Home
last modified time | relevance | path

Searched refs:CALL (Results 1 – 25 of 33) sorted by relevance

12

/Linux-v6.6/tools/testing/selftests/bpf/
Duprobe_multi.c13 #define CALL(name, idx) NAME(name, idx)(); macro
49 F10000(CALL, uprobe_multi_func_, 0) in bench()
50 F10000(CALL, uprobe_multi_func_, 1) in bench()
51 F10000(CALL, uprobe_multi_func_, 2) in bench()
52 F10000(CALL, uprobe_multi_func_, 3) in bench()
53 F10000(CALL, uprobe_multi_func_, 4) in bench()
/Linux-v6.6/drivers/scsi/
D53c700.scr244 CALL SendMessage
283 CALL ProcessReceiveMessage
308 CALL ProcessReceiveMessage
314 CALL SGScriptStartAddress
327 CALL SGScriptStartAddress
338 CALL ProcessReceiveMessage
373 CALL ProcessReceiveMessage
400 CALL ProcessReceiveMessage
D53c700_d.h_shipped409 CALL SendMessage
517 CALL ProcessReceiveMessage
584 CALL ProcessReceiveMessage
602 CALL SGScriptStartAddress
639 CALL SGScriptStartAddress
674 CALL ProcessReceiveMessage
763 CALL ProcessReceiveMessage
835 CALL ProcessReceiveMessage
/Linux-v6.6/arch/x86/kernel/
Dstatic_call.c8 CALL = 0, /* site call */ enumerator
65 case CALL: in __static_call_transform()
Dftrace_64.S301 CALL .Ldo_rebalance
/Linux-v6.6/Documentation/admin-guide/hw-vuln/
Dsrso.rst15 CALL instruction (i.e., an instruction predicted to be a CALL but is
16 not actually a CALL) can create an entry in the RAP which may be used
21 non-architectural CALL instructions in kernel space and use this to
Dcross-thread-rsb.rst61 An attack can be mounted on affected processors by performing a series of CALL
70 targets by performing a sequence of CALL instructions.
/Linux-v6.6/drivers/gpu/drm/nouveau/include/nvif/
Dpush206e.h9 PUSH_DATA__((p), NVDEF(NV206E, DMA, OPCODE2, CALL) | \
/Linux-v6.6/drivers/media/v4l2-core/
Dvideobuf-core.c50 #define CALL(q, f, arg...) \ macro
127 return CALL(q, iolock, q, vb, fbuf); in videobuf_iolock()
724 CALL(q, sync, q, buf); in videobuf_dqbuf()
816 CALL(q, sync, q, q->read_buf); in videobuf_read_zerocopy()
930 CALL(q, sync, q, q->read_buf); in videobuf_read_one()
1190 rc = CALL(q, mmap_mapper, q, buf, vma); in videobuf_mmap_mapper()
/Linux-v6.6/arch/x86/include/asm/
Dtext-patching.h83 __CASE(CALL); in text_opcode_size()
Dperf_event_p4.h723 P4_GEN_ESCR_EMASK(P4_EVENT_RETIRED_MISPRED_BRANCH_TYPE, CALL, 2),
728 P4_GEN_ESCR_EMASK(P4_EVENT_RETIRED_BRANCH_TYPE, CALL, 2),
/Linux-v6.6/
DKbuild39 quiet_cmd_syscalls = CALL $<
/Linux-v6.6/arch/m68k/ifpsp060/
Diskeleton.S43 | (1) EXAMPLE CALL-OUTS #
309 | (3) EXAMPLE CALL-OUT SECTION #
Dfskeleton.S40 | (1) EXAMPLE CALL-OUTS #
300 | (3) EXAMPLE CALL-OUT SECTION #
Dos.S38 | EXAMPLE CALL-OUTS #
/Linux-v6.6/Documentation/arch/x86/
Dshstk.rst16 applications. When executing a CALL instruction, the processor pushes the
20 control-protection fault. IBT verifies indirect CALL/JMP targets are intended
/Linux-v6.6/arch/x86/events/intel/
Dp4.c350 P4_ESCR_EMASK_BIT(P4_EVENT_RETIRED_MISPRED_BRANCH_TYPE, CALL) |
360 P4_ESCR_EMASK_BIT(P4_EVENT_RETIRED_BRANCH_TYPE, CALL) |
688 P4_ESCR_EMASK_BIT(P4_EVENT_RETIRED_BRANCH_TYPE, CALL) |
/Linux-v6.6/scripts/gcc-plugins/
Dstackleak_plugin.c302 if (GET_CODE(body) != CALL) in remove_stack_tracking_gcall()
/Linux-v6.6/arch/sparc/net/
Dbpf_jit_comp_32.c85 #define CALL F1(1) macro
243 *prog++ = CALL | (((_off) >> 2) & 0x3fffffff); \
Dbpf_jit_comp_64.c161 #define CALL F1(1) macro
251 ctx->image[ctx->idx] = CALL | ((off >> 2) & 0x3fffffff); in emit_call()
/Linux-v6.6/tools/perf/util/
Dperf_event_attr_fprintf.c56 bit_name(CALL), bit_name(NO_FLAGS), bit_name(NO_CYCLES), in __p_branch_sample_type()
Ddlfilter.c369 CHECK_FLAG(CALL); in dlfilter__init()
/Linux-v6.6/include/linux/ceph/
Drados.h314 f(CALL, __CEPH_OSD_OP(RD, EXEC, 1), "call") \
/Linux-v6.6/Documentation/translations/ko_KR/
Dmemory-barriers.txt2366 CALL wakeup
2407 CALL wakeup
/Linux-v6.6/arch/x86/lib/
Dx86-opcode-map.txt293 # in "near" jumps and calls is 16-bit. For CALL,
296 e8: CALL Jz (f64)
475 # Note: "forced64" is Intel CPU behavior (see comment about CALL insn).
1034 # Note: "forced64" is Intel CPU behavior (see comment about CALL insn).

12