| /linux/arch/mips/mti-malta/ |
| A D | malta-amon.c | 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()
64 launch->flags |= LAUNCH_FGO; in amon_cpu_start()
[all …]
|
| /linux/Documentation/hwmon/ |
| A D | isl68137.rst | 25 Publicly available (after August 2020 launch) at the Renesas website
35 Publicly available (after August 2020 launch) at the Renesas website
45 Publicly available (after August 2020 launch) at the Renesas website
55 Publicly available (after August 2020 launch) at the Renesas website
65 Publicly available (after August 2020 launch) at the Renesas website
75 Publicly available (after August 2020 launch) at the Renesas website
85 Publicly available (after August 2020 launch) at the Renesas website
95 Publicly available (after August 2020 launch) at the Renesas website
105 Publicly available (after August 2020 launch) at the Renesas website
115 Publicly available (after August 2020 launch) at the Renesas website
[all …]
|
| /linux/arch/mips/sgi-ip30/ |
| A D | ip30-smp.c | 37 void *launch; member
123 mpc->launch = smp_bootstrap; in ip30_smp_boot_secondary()
|
| /linux/Documentation/x86/ |
| A D | intel_txt.rst | 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
|
| A D | sgx.rst | 155 SGX provides a launch control mechanism. After all enclave pages have been
166 kernel on launch control policy. Before calling EINIT function, the driver sets
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-devices-platform-stratix10-rsu | 114 and the operating system launch was
|
| /linux/Documentation/devicetree/bindings/pci/ |
| A D | fsl,imx6q-pcie.yaml | 117 description: TX launch amplitude swing_low value (optional required).
|
| /linux/Documentation/admin-guide/media/ |
| A D | imx7.rst | 178 …gst-launch-1.0 -v v4l2src device=/dev/video1 ! video/x-raw,format=UYVY,width=640,height=480 ! v4l2…
|
| A D | imx.rst | 632 gst-launch-1.0 v4l2src device=/dev/video0 ! kmssink
680 gst-launch-1.0 v4l2src device=/dev/video1 ! kmssink
|
| /linux/Documentation/driver-api/ |
| A D | reset.rst | 41 In more complicated reset controls, a single trigger action can launch a
|
| /linux/Documentation/networking/ |
| A D | 6pack.rst | 131 - Do a spattach as you would launch kissattach when starting a KISS port.
|
| /linux/security/ |
| A D | Kconfig | 105 Intel(R) Trusted Execution Technology to perform a measured launch
|
| /linux/Documentation/userspace-api/ |
| A D | landlock.rst | 274 life of a thread, especially for applications able to launch other applications
|
| /linux/arch/x86/kvm/vmx/ |
| A D | nested.c | 3492 static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch) in nested_vmx_run() argument
3503 evmptrld_status = nested_vmx_handle_enlightened_vmptrld(vcpu, launch); in nested_vmx_run()
3529 vmcs12->launch_state = !launch; in nested_vmx_run()
3547 if (CC(vmcs12->launch_state == launch)) in nested_vmx_run()
3549 launch ? VMXERR_VMLAUNCH_NONCLEAR_VMCS in nested_vmx_run()
|
| /linux/Documentation/virt/kvm/ |
| A D | amd-memory-encryption.rst | 170 After completion of the launch flow, the KVM_SEV_LAUNCH_FINISH command can be
|
| /linux/drivers/staging/unisys/Documentation/ |
| A D | overview.txt | 303 PartitionDesktop.msi, you will be able to launch a console for your guest
|
| /linux/Documentation/powerpc/ |
| A D | firmware-assisted-dump.rst | 70 *not* clear the RAM. It will then launch the bootloader, as
|
| A D | hvcs.rst | 237 used to launch the interactive I/O application. If one is using xterm and
|
| /linux/drivers/scsi/ |
| A D | ncr53c8xx.c | 1332 struct launch { struct
1514 struct launch start;
1522 struct launch restart;
|
| /linux/scripts/ |
| A D | spelling.txt | 882 lauch||launch
|
| /linux/Documentation/scsi/ |
| A D | ChangeLog.ncr53c8xx | 459 Use a simple CALL to a launch script in the CCB.
|
| /linux/Documentation/admin-guide/mm/ |
| A D | hugetlbpage.rst | 332 other node at any time after launch and the resulting node will be
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| A D | spectre.rst | 192 target buffer (BTB) before issuing syscall to launch an attack.
|
| /linux/mm/ |
| A D | Kconfig | 842 to make ioctl calls that can launch kernel-based unit tests for
|