Searched refs:launch (Results 1 – 17 of 17) sorted by relevance
| /Linux-v4.19/arch/mips/mti-malta/ |
| D | malta-amon.c | 21 struct cpulaunch *launch = (struct cpulaunch *)CKSEG0ADDR(CPULAUNCH); in amon_cpu_avail() local
28 launch += cpu; in amon_cpu_avail()
29 if (!(launch->flags & LAUNCH_FREADY)) { in amon_cpu_avail()
33 if (launch->flags & (LAUNCH_FGO|LAUNCH_FGONE)) { in amon_cpu_avail()
45 volatile struct cpulaunch *launch = in amon_cpu_start() local
54 launch += cpu; in amon_cpu_start()
58 launch->pc = pc; in amon_cpu_start()
59 launch->gp = gp; in amon_cpu_start()
60 launch->sp = sp; in amon_cpu_start()
61 launch->a0 = a0; in amon_cpu_start()
[all …]
|
| /Linux-v4.19/arch/powerpc/platforms/powernv/ |
| D | npu-dma.c | 461 unsigned long launch, unsigned long va) in mmio_launch_invalidate() argument
468 __raw_writeq_be(launch, npu->mmio_atsd_regs[reg]); in mmio_launch_invalidate()
475 unsigned long launch; in mmio_invalidate_pid() local
482 launch = PPC_BIT(12); in mmio_invalidate_pid()
485 launch |= PPC_BIT(13); in mmio_invalidate_pid()
488 launch |= (u64) in mmio_invalidate_pid()
492 launch |= pid << PPC_BITLSHIFT(38); in mmio_invalidate_pid()
495 launch |= !flush << PPC_BITLSHIFT(39); in mmio_invalidate_pid()
498 mmio_launch_invalidate(&mmio_atsd_reg[i], launch, 0); in mmio_invalidate_pid()
506 unsigned long launch; in mmio_invalidate_va() local
[all …]
|
| /Linux-v4.19/Documentation/ |
| D | intel_txt.txt | 47 uses Intel TXT to perform a measured and verified launch of an OS
83 pre-launch components can be removed from the trust chain, DMA
105 incorrect), it will directly launch the kernel with no changes
126 - Tboot then applies an (optional) user-defined launch policy to
140 - As part of its launch, tboot DMA protects all of RAM (using the
160 launch, TXT must first be exited. This is to prevent attacks that
|
| /Linux-v4.19/Documentation/devicetree/bindings/pci/ |
| D | fsl,imx6q-pcie.txt | 25 - fsl,tx-swing-low: TX launch amplitude swing_low value. Default: 127
|
| /Linux-v4.19/Documentation/virtual/kvm/ |
| D | amd-memory-encryption.rst | 142 After completion of the launch flow, the KVM_SEV_LAUNCH_FINISH command can be
|
| /Linux-v4.19/security/ |
| D | Kconfig | 105 Intel(R) Trusted Execution Technology to perform a measured launch
|
| /Linux-v4.19/Documentation/networking/ |
| D | 6pack.txt | 116 - Do a spattach as you would launch kissattach when starting a KISS port.
|
| /Linux-v4.19/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 69 *not* clear the RAM. It will then launch the bootloader, as
|
| D | hvcs.txt | 234 used to launch the interactive I/O application. If one is using xterm and
|
| /Linux-v4.19/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 303 PartitionDesktop.msi, you will be able to launch a console for your guest
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | blkio-controller.txt | 46 launch two dd threads in different cgroup to read those files.
|
| /Linux-v4.19/scripts/ |
| D | spelling.txt | 730 lauch||launch
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | hugetlbpage.rst | 239 other node at any time after launch and the resulting node will be
|
| /Linux-v4.19/drivers/scsi/ |
| D | ncr53c8xx.c | 1341 struct launch { struct
1528 struct launch start;
1536 struct launch restart;
|
| /Linux-v4.19/Documentation/scsi/ |
| D | ChangeLog.ncr53c8xx | 459 Use a simple CALL to a launch script in the CCB.
|
| /Linux-v4.19/arch/x86/kvm/ |
| D | vmx.c | 8533 static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch);
12696 static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch) in nested_vmx_run() argument
12742 if (vmcs12->launch_state == launch) { in nested_vmx_run()
12744 launch ? VMXERR_VMLAUNCH_NONCLEAR_VMCS in nested_vmx_run()
|
| /Linux-v4.19/Documentation/s390/ |
| D | Debugging390.txt | 1847 to launch gdb (my victim app. ) now be bad & do the following from another
|
