Home
last modified time | relevance | path

Searched refs:supervisor (Results 1 – 25 of 32) sorted by relevance

12

/Linux-v4.19/arch/m68k/ifpsp060/
Dos.S58 | 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 …]
Diskeleton.S72 btst #0x5,%sp@ | supervisor bit set in saved SR?
192 | d0 = `xxxxxxff -> supervisor; `xxxxxx00 -> user
258 | d0 = `xxxxxxff -> supervisor; `xxxxxx00 -> user
DCHANGES91 bit 18:16 = x10 (TM; x = 1 for supervisor mode)
113 bit 18:16 = x01 (TM; x = 1 for supervisor mode)
/Linux-v4.19/Documentation/devicetree/bindings/interrupt-controller/
Driscv,cpu-intc.txt10 The RISC-V supervisor ISA manual specifies three interrupt sources that are
18 All RISC-V systems that conform to the supervisor ISA specification are
29 RISC-V supervisor ISA manual, with only the following three interrupts being
30 defined for supervisor mode:
31 - Source 1 is the supervisor software interrupt, which can be sent by an SBI
33 - Source 5 is the supervisor timer interrupt, which can be configured by
35 - Source 9 is the supervisor external interrupt, which chains to all other
Dsifive,plic-1.0.0.txt11 privilege modes per hart; machine mode and supervisor mode.
/Linux-v4.19/arch/m68k/fpsp040/
Dskeleton.S393 | 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
Dx_store.S167 exg %a0,%a1 |a0=supervisor source, a1=user dest
251 exg %a0,%a1 |a0=supervisor source, a1=user dest
/Linux-v4.19/drivers/gpu/drm/nouveau/nvkm/engine/disp/
Dgf119.c37 container_of(work, struct nv50_disp, supervisor); in gf119_disp_super()
145 queue_work(disp->wq, &disp->supervisor); in gf119_disp_intr()
Dnv50.h13 struct work_struct supervisor; member
Dgv100.c43 container_of(work, struct nv50_disp, supervisor); in gv100_disp_super()
133 queue_work(disp->wq, &disp->supervisor); in gv100_disp_intr_ctrl_disp()
Dnv50.c176 INIT_WORK(&disp->supervisor, func->super); in nv50_disp_new_()
548 container_of(work, struct nv50_disp, supervisor); in nv50_disp_super()
676 queue_work(disp->wq, &disp->supervisor); in nv50_disp_intr()
/Linux-v4.19/drivers/misc/eeprom/
DKconfig56 tristate "Maxim MAX6874/5 power supply supervisor"
61 sequencer/supervisor.
/Linux-v4.19/Documentation/virtual/kvm/
Dhypercalls.txt72 shared page that contains parts of supervisor visible register state.
73 The guest can map this shared page to access its supervisor register through
Dppc-pv.txt67 page that contains parts of supervisor visible register state. The guest can
/Linux-v4.19/drivers/gpu/drm/nouveau/nvkm/core/
Dioctl.c429 nvkm_ioctl(struct nvkm_client *client, bool supervisor, in nvkm_ioctl() argument
438 client->super = supervisor; in nvkm_ioctl()
/Linux-v4.19/arch/m68k/ifpsp060/src/
Dpfpsp.S1560 # 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 …]
Disp.S482 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
/Linux-v4.19/Documentation/arm/nwfpe/
DREADME.FPE56 RFC/WFC are fully implemented. RFC/WFC are supervisor only instructions, and
58 from supervisor mode.
DTODO52 supervisor only instructions. If anyone has any ideas or comments I
/Linux-v4.19/Documentation/core-api/
Derrseq.rst78 struct supervisor {
83 struct supervisor su;
/Linux-v4.19/Documentation/misc-devices/
Dmax687517 The Maxim MAX6875 is an EEPROM-programmable power-supply sequencer/supervisor.
/Linux-v4.19/arch/powerpc/kvm/
DKconfig96 using supervisor and user modes. However, this also means
/Linux-v4.19/arch/m68k/
DKconfig.cpu386 bool "Use write-through caching for 68060 supervisor accesses"
392 here will force supervisor (kernel) accesses to use writethrough
/Linux-v4.19/Documentation/
DDMA-attributes.txt154 accesses to DMA buffers in both privileged "supervisor" and unprivileged
/Linux-v4.19/arch/arm/boot/dts/
Dam437x-idk-evm.dts525 * Supply voltage supervisor on board will not allow opp50 so

12