| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | os.S | 58 | or supervisor application space. The examples below use simple "move"
59 | instructions for supervisor mode applications and call _copyin()/_copyout()
76 | Writes to data memory while in supervisor mode.
79 | a0 - supervisor source address
82 | 0x4(%a6),bit5 - 1 = supervisor mode, 0 = user mode
89 btst #0x5,0x4(%a6) | check for supervisor state
107 | Reads from data/instruction memory while in supervisor mode.
111 | a1 - supervisor destination address
113 | 0x4(%a6),bit5 - 1 = supervisor mode, 0 = user mode
122 btst #0x5,0x4(%a6) | check for supervisor state
[all …]
|
| D | iskeleton.S | 72 btst #0x5,%sp@ | supervisor bit set in saved SR?
192 | d0 = `xxxxxxff -> supervisor; `xxxxxx00 -> user
258 | d0 = `xxxxxxff -> supervisor; `xxxxxx00 -> user
|
| D | CHANGES | 91 bit 18:16 = x10 (TM; x = 1 for supervisor mode)
113 bit 18:16 = x01 (TM; x = 1 for supervisor mode)
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | skeleton.S | 393 | a0 - supervisor source address
397 | The supervisor source address is guaranteed to point into the supervisor
404 | If the EXC_SR shows that the exception was from supervisor space,
439 | a1 - supervisor destination address
442 | Like mem_write, mem_read always reads with a supervisor
443 | destination address on the supervisor stack. Also like mem_write,
445 | from supervisor space is indicated.
449 btstb #5,EXC_SR(%a6) |check for supervisor state
|
| D | x_store.S | 167 exg %a0,%a1 |a0=supervisor source, a1=user dest
251 exg %a0,%a1 |a0=supervisor source, a1=user dest
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | hypercalls.txt | 67 shared page that contains parts of supervisor visible register state.
68 The guest can map this shared page to access its supervisor register through
|
| D | ppc-pv.txt | 67 page that contains parts of supervisor visible register state. The guest can
|
| D | api.txt | 3414 It also sets the guest privilege level to "supervisor" mode. Usually the guest
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/disp/ |
| D | nv50.h | 17 struct work_struct supervisor; member
|
| D | nv50.c | 152 INIT_WORK(&disp->supervisor, func->super); in nv50_disp_new_()
733 container_of(work, struct nv50_disp, supervisor); in nv50_disp_intr_supervisor()
810 schedule_work(&disp->supervisor); in nv50_disp_intr()
|
| D | gf119.c | 366 container_of(work, struct nv50_disp, supervisor); in gf119_disp_intr_supervisor()
477 schedule_work(&disp->supervisor); in gf119_disp_intr()
|
| /linux-4.4.14/drivers/misc/eeprom/ |
| D | Kconfig | 53 tristate "Maxim MAX6874/5 power supply supervisor"
58 sequencer/supervisor.
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/core/ |
| D | ioctl.c | 417 nvkm_ioctl(struct nvkm_client *client, bool supervisor, in nvkm_ioctl() argument
426 client->super = supervisor; in nvkm_ioctl()
|
| /linux-4.4.14/arch/frv/kernel/ |
| D | break.S | 317 # exceptions must've been enabled and we must've been in supervisor mode
352 # exceptions must've been enabled and we must've been in supervisor mode
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 1560 # it here. if it was used from supervisor mode, then we have to handle this
1580 # is the ea mode pre-decrement of the stack pointer from supervisor mode?
1882 btst &0x5,EXC_SR(%a6) # user or supervisor?
1883 bne.w fu_in_exit_s_p # supervisor
1900 # the exception occurred in supervisor mode. check to see if the
1979 btst &0x5,EXC_SR(%a6) # user or supervisor?
1980 bne.w fu_in_exc_exit_s_p # supervisor
2113 btst &0x5,EXC_SR(%a6) # user or supervisor?
2114 bne.b fu_out_exit_s_p # supervisor
2131 # the exception occurred in supervisor mode. check to see if the
[all …]
|
| D | isp.S | 482 btst &0x5,EXC_ISR(%a6) # supervisor mode?
504 btst &0x5,EXC_ISR(%a6) # supervisor mode?
506 # here, a7 has been incremented by 4 bytes in supervisor mode. we still
579 # changed. we don't have to update a7 for supervisor mose because that case
|
| D | fpsp.S | 1561 # it here. if it was used from supervisor mode, then we have to handle this
1581 # is the ea mode pre-decrement of the stack pointer from supervisor mode?
1883 btst &0x5,EXC_SR(%a6) # user or supervisor?
1884 bne.w fu_in_exit_s_p # supervisor
1901 # the exception occurred in supervisor mode. check to see if the
1980 btst &0x5,EXC_SR(%a6) # user or supervisor?
1981 bne.w fu_in_exc_exit_s_p # supervisor
2114 btst &0x5,EXC_SR(%a6) # user or supervisor?
2115 bne.b fu_out_exit_s_p # supervisor
2132 # the exception occurred in supervisor mode. check to see if the
[all …]
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | README.FPE | 56 RFC/WFC are fully implemented. RFC/WFC are supervisor only instructions, and
58 from supervisor mode.
|
| D | TODO | 52 supervisor only instructions. If anyone has any ideas or comments I
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | max6875 | 17 The Maxim MAX6875 is an EEPROM-programmable power-supply sequencer/supervisor.
|
| /linux-4.4.14/Documentation/mn10300/ |
| D | ABI.txt | 91 All other non-supervisor-only registers are clobberable (such as MDR, MCRL,
|
| /linux-4.4.14/arch/powerpc/kvm/ |
| D | Kconfig | 90 using supervisor and user modes. However, this also means
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.cpu | 374 bool "Use write-through caching for 68060 supervisor accesses"
380 here will force supervisor (kernel) accesses to use writethrough
|
| /linux-4.4.14/arch/cris/arch-v32/kernel/ |
| D | head.S | 42 ;; supervisor mode.
|
| /linux-4.4.14/Documentation/frv/ |
| D | kernel-ABI.txt | 10 supervisor stack pointer, and most of them do not have any scratch
|
| /linux-4.4.14/arch/powerpc/boot/dts/ |
| D | xpedite5301.dts | 223 cpu-supervisor@51 {
|
| D | xpedite5370.dts | 221 cpu-supervisor@51 {
|
| D | xpedite5330.dts | 259 cpu-supervisor@51 {
|
| D | xcalibur1501.dts | 230 cpu-supervisor@51 {
|
| /linux-4.4.14/arch/cris/arch-v10/kernel/ |
| D | head.S | 30 ;; This is the entry point of the kernel. We are in supervisor mode.
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | entry.S | 530 # PER event in supervisor state, must be kprobes
|