Searched refs:downcall (Results 1 - 16 of 16) sorted by relevance
/linux-4.4.14/arch/tile/kernel/ |
H A D | messaging.c | 36 /* Make sure downcall interrupts will be enabled. */ init_messaging() 103 * We shouldn't have gotten a message downcall with no hv_message_intr() 107 panic("Message downcall invoked with no messages!"); hv_message_intr()
|
H A D | intvec_64.S | 359 * any path that turns into a downcall to one of our TLB handlers. 363 * The advantage of getting a downcall is we can panic in Linux. 782 * Redispatch a downcall.
|
H A D | intvec_32.S | 165 * any path that turns into a downcall to one of our TLB handlers. 747 * Redispatch a downcall.
|
/linux-4.4.14/arch/tile/include/hv/ |
H A D | drv_pcie_rc_intf.h | 34 int intr; /**< interrupt number used for downcall */
|
H A D | hypervisor.h | 1193 /** Dispatch the next interrupt from the client downcall mechanism. 1200 * be delivered through the downcall mechanism. 1202 * A downcall is initially delivered to the client as an INTCTRL_CL 1206 * the client's actual downcall-handling interrupt vectors to be entered. 1214 * of entering one of the client's actual downcall-handling interrupt 1226 * will set this register to cause a downcall to happen, and will clear 1229 * When a downcall vector is entered, the INTCTRL_CL interrupt will be 1230 * masked. When the client is done processing a downcall, and is ready 1234 * downcall: 1247 * to allow setting MPLs for related SPRs) for our downcall vectors. 1249 /** Message receive downcall interrupt vector */ 1251 /** DMA TLB miss downcall interrupt vector */ 1255 /** DMA TLB access violation downcall interrupt vector */ 1257 /** Device interrupt downcall interrupt vector */ 1259 /** NMI downcall interrupt vector */ 1262 #define HV_NMI_FLAG_FORCE 0x1 /**< Force an NMI downcall regardless of 1567 * interrupt vector to be invoked through the interrupt downcall mechanism 1571 * Another message-available downcall will not occur until a call to 1573 * subsequently arrives. Note that such a downcall could occur while 1755 * downcall (intctrl1) method, depending on what the tile is doing 1811 /** Force an NMI downcall regardless of the ICS bit of the client. */ 1872 * The completion interrupt message could come directly, or via the downcall 1918 * The completion interrupt message could come directly, or via the downcall
|
/linux-4.4.14/include/linux/sunrpc/ |
H A D | rpc_pipe_fs.h | 38 ssize_t (*downcall)(struct file *, const char __user *, size_t); member in struct:rpc_pipe_ops
|
/linux-4.4.14/fs/coda/ |
H A D | psdev.c | 123 pr_warn("downcall opc %d, uniq %d, too much!", coda_psdev_write() 134 /* what downcall errors does Venus handle ? */ coda_psdev_write()
|
H A D | dir.c | 505 * cache manager Venus issues a downcall to the kernel when this
|
/linux-4.4.14/fs/nfs/blocklayout/ |
H A D | rpc_pipefs.c | 141 .downcall = bl_pipe_downcall,
|
/linux-4.4.14/net/sunrpc/ |
H A D | rpc_pipe.c | 338 res = RPC_I(inode)->pipe->ops->downcall(filp, buf, len); rpc_pipe_write() 813 * responses to upcalls. They will result in calls to @msg->downcall. 828 if (pipe->ops->downcall == NULL) rpc_mkpipe_dentry() 1276 .downcall = dummy_downcall,
|
/linux-4.4.14/drivers/infiniband/core/ |
H A D | iwcm.c | 289 /* Wait if we're currently in a connect or accept downcall */ iw_cm_disconnect() 355 * Wait if we're currently in a connect or accept downcall. A destroy_cm_id() 914 * the iwcm_wq thread to allow callback functions to downcall into
|
/linux-4.4.14/fs/nfsd/ |
H A D | nfs4recover.c | 674 * wake_up_process in the downcall from racing with schedule. __cld_pipe_upcall() 761 /* errno >= 0 means we got a downcall */ cld_pipe_destroy_msg() 770 .downcall = cld_pipe_downcall,
|
/linux-4.4.14/fs/nfs/ |
H A D | nfs4idmap.c | 394 .downcall = idmap_pipe_downcall,
|
/linux-4.4.14/net/sunrpc/auth_gss/ |
H A D | gss_krb5_mech.c | 292 /* The downcall format was designed before we completely understood gss_import_v1_context()
|
H A D | auth_gss.c | 2017 .downcall = gss_pipe_downcall, 2025 .downcall = gss_pipe_downcall,
|
/linux-4.4.14/arch/tile/mm/ |
H A D | fault.c | 198 * itself during the downcall from hypervisor to Linux. We just check
|
Completed in 630 milliseconds