Home
last modified time | relevance | path

Searched refs:launch (Results 1 – 15 of 15) sorted by relevance

/linux-4.4.14/arch/mips/mti-malta/
Dmalta-amon.c21 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-4.4.14/Documentation/
Dintel_txt.txt40 uses Intel TXT to perform a measured and verified launch of an OS
76 pre-launch components can be removed from the trust chain, DMA
97 incorrect), it will directly launch the kernel with no changes
115 o Tboot then applies an (optional) user-defined launch policy to
127 o As part of its launch, tboot DMA protects all of RAM (using the
145 launch, TXT must first be exited. This is to prevent attacks that
/linux-4.4.14/drivers/staging/unisys/Documentation/
Dproc-entries.txt80 next reboot will launch the installation and recovery tool. If set to
Doverview.txt322 PartitionDesktop.msi, you will be able to launch a console for your guest
/linux-4.4.14/security/
DKconfig80 Intel(R) Trusted Execution Technology to perform a measured launch
/linux-4.4.14/Documentation/networking/
D6pack.txt116 - Do a spattach as you would launch kissattach when starting a KISS port.
/linux-4.4.14/Documentation/powerpc/
Dfirmware-assisted-dump.txt65 *not* clear the RAM. It will then launch the bootloader, as
Dhvcs.txt234 used to launch the interactive I/O application. If one is using xterm and
/linux-4.4.14/scripts/
Dspelling.txt579 lauch||launch
/linux-4.4.14/Documentation/vm/
Dhugetlbpage.txt212 other node at any time after launch and the resulting node will be
/linux-4.4.14/Documentation/cgroups/
Dblkio-controller.txt46 launch two dd threads in different cgroup to read those files.
/linux-4.4.14/drivers/scsi/
Dncr53c8xx.c1341 struct launch { struct
1528 struct launch start;
1536 struct launch restart;
/linux-4.4.14/Documentation/scsi/
DChangeLog.ncr53c8xx459 Use a simple CALL to a launch script in the CCB.
/linux-4.4.14/arch/x86/kvm/
Dvmx.c6943 static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch);
9796 static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch) in nested_vmx_run() argument
9825 if (vmcs12->launch_state == launch) { in nested_vmx_run()
9827 launch ? VMXERR_VMLAUNCH_NONCLEAR_VMCS in nested_vmx_run()
/linux-4.4.14/Documentation/s390/
DDebugging390.txt1847 to launch gdb (my victim app. ) now be bad & do the following from another