Home
last modified time | relevance | path

Searched refs:RIP (Results 1 – 12 of 12) sorted by relevance

/linux-3.4.99/arch/x86/ia32/
Dia32entry.S152 orl $TS_COMPAT,TI_status+THREAD_INFO(%rsp,RIP-ARGOFFSET)
153 testl $_TIF_WORK_SYSCALL_ENTRY,TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
165 testl $_TIF_ALLWORK_MASK,TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
168 andl $~TS_COMPAT,TI_status+THREAD_INFO(%rsp,RIP-ARGOFFSET)
171 movl RIP-R11(%rsp),%edx /* User %eip */
205 testl $(_TIF_ALLWORK_MASK & ~_TIF_SYSCALL_AUDIT),TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
220 testl %edi,TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
238 testl $(_TIF_WORK_SYSCALL_ENTRY & ~_TIF_SYSCALL_AUDIT),TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
292 movq %rcx,RIP-ARGOFFSET(%rsp)
293 CFI_REL_OFFSET rip,RIP-ARGOFFSET
[all …]
/linux-3.4.99/arch/x86/kernel/
Dentry_64.S256 EMPTY_FRAME \start, SS+8+\offset-RIP
258 CFI_REL_OFFSET rsp, RSP+\offset-RIP
261 CFI_REL_OFFSET rip, RIP+\offset-RIP
269 INTR_FRAME \start, RIP+\offset-ORIG_RAX
479 movq %rcx,RIP-ARGOFFSET(%rsp)
480 CFI_REL_OFFSET rip,RIP-ARGOFFSET
481 testl $_TIF_WORK_SYSCALL_ENTRY,TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
505 movl TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET),%edx
513 movq RIP-ARGOFFSET(%rsp),%rcx
588 testl $(_TIF_WORK_SYSCALL_ENTRY & ~_TIF_SYSCALL_AUDIT),TI_flags+THREAD_INFO(%rsp,RIP-ARGOFFSET)
[all …]
/linux-3.4.99/arch/x86/um/
Dptrace_64.c31 [RIP >> 3] = HOST_IP,
71 case RIP: in putreg()
148 case RIP: in getreg()
Duser-offsets.c82 DEFINE_LONGS(HOST_IP, RIP); in foo()
/linux-3.4.99/arch/x86/include/asm/
Dptrace-abi.h47 #define RIP 128 macro
Dcalling.h79 #define RIP (128) macro
/linux-3.4.99/net/ipx/
DKconfig55 disabled. This might break existing applications, especially RIP/SAP
56 daemons. A RIP/SAP daemon that works well with the full internal net
/linux-3.4.99/arch/x86/um/os-Linux/
Dmcontext.c25 COPY(RIP); in get_regs_from_mc()
/linux-3.4.99/Documentation/
Dkmemcheck.txt242 RIP: 0010:[<ffffffff8104ede8>] [<ffffffff8104ede8>] __dequeue_signal+0xc8/0x190
260 The single most valuable information in this report is the RIP (or EIP on 32-
353 RIP value, they actually point to the _next_ instruction (they are return
493 that, we'll need the RIP address again:
495 RIP: 0010:[<ffffffff8104ede8>] [<ffffffff8104ede8>] __dequeue_signal+0xc8/0x190
Dkernel-parameters.txt2903 targets for exploits that can control RIP.
/linux-3.4.99/drivers/staging/telephony/
Dixj.h564 BYTE RIP:1; /* cr0[1:1] */ member
/linux-3.4.99/Documentation/trace/
Dftrace.txt1287 [57848.106019] RIP: 0010:[<ffffffffa0000006>] [<ffffffffa0000006>] open+0x6/0x14 [oops]