Lines Matching refs:user
18 switched over to kernel memory. The user-level state is saved
21 - user mode:
23 user memory. The user-level state is contained in the
28 interruption-handlers start execution in. The user-level
36 - CPU registers may contain a mixture of user-level and kernel-level
39 user-level)
46 in fsys-mode (they point to the user-level stacks, which may
49 In summary, fsys-mode is much more similar to running in user-mode
69 to by "regs" was executing in user mode (privilege level 3).
71 executing on the user-level stack(s). Finally, fsys_mode() returns
93 - r11 = saved ar.pfs (a user-level value)
97 - b6 = return address (a user-level value)
98 - ar.pfs = previous frame-state (a user-level value)
100 - all other registers may contain values passed in from user-mode
134 it is not safe to assume that user-level called a handler with the
143 information back to user-level. In particular, before returning to
144 user-level, care needs to be taken to clear any scratch registers
149 o Fsyscall-handlers MUST NOT access user-memory without first
188 words, user-level code must not rely on PSR.be being preserved
204 PSR.db Unchanged. The kernel prevents user-level from setting a hardware
205 breakpoint that triggers at any privilege level other than 3 (user-mode).
214 the fsys-mode handler will return directly to user-level. This