Home
last modified time | relevance | path

Searched refs:metal (Results 1 – 18 of 18) sorted by relevance

/linux/tools/testing/selftests/rcutorture/bin/
H A Dkvm-test-1-run.sh171 # Give bare-metal advice
175 touch $resdir/bare-metal
176 echo To run this scenario on bare metal: >> $resdir/bare-metal
177 echo >> $resdir/bare-metal
178 echo " 1." Set your bare-metal build tree to the state shown in this file: >> $resdir/bare-metal
179 echo " " $testid_txt >> $resdir/bare-metal
180 echo " 2." Update your bare-metal build tree"'"s .config based on this file: >> $resdir/bare-metal
[all...]
/linux/Documentation/virt/kvm/x86/
H A Drunning-nested-guests.rst31 - L0 – level-0; the bare metal host, running KVM
43 hypervisor running on bare metal, adding another layer and
45 metal, running the LPAR hypervisor), L1 (host hypervisor), L2
88 1. On the bare metal host (L0), list the kernel modules and ensure that
128 metal host (L0). Parameters for Intel hosts::
147 Once your bare metal host (L0) is configured for nesting, you should be
188 bare metal host, works as of Linux kernel 5.3 and QEMU 4.2.0 for
206 metal host.
209 bare metal host.
211 - Migrating a nested guest (L2) to a bare metal host.
H A Derrata.rst9 behavioral differences between virtual machines and bare metal systems.
H A Dtimekeeping.rst499 solving many of these problems on bare metal.
/linux/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-rf-tuner.rst18 inside a metal box, while newer ones are highly integrated chips
19 without a metal box "silicon tuners". These controls are mostly
/linux/Documentation/virt/acrn/
H A Dintroduction.rst6 The ACRN Hypervisor is a Type 1 hypervisor, running directly on bare-metal
/linux/Documentation/admin-guide/media/
H A Dfrontend-cardlist.rst14 the demodulator and tuner/PLL chip are inside a metal box for
15 shielding, and the whole metal box has its own part number.
H A Dbttv.rst555 #) These cards have a number printed on the PCB just above the tuner metal box:
/linux/kernel/configs/
H A Ddebug.config4 # seek regressions on linux-next builds on different bare-metal and virtual
/linux/Documentation/admin-guide/hw-vuln/
H A Dl1tf.rst409 on both hypervisor and bare metal.
557 the bare metal hypervisor, the nested hypervisor and the nested virtual
559 guest will always be processed by the bare metal hypervisor. If KVM is the
560 bare metal hypervisor it will:
568 cache avoids that the bare metal hypervisor's secrets are exposed to the
/linux/Documentation/arch/powerpc/
H A Ddawr-power9.rst51 For GDB watchpoints (ie 'watch' command) on POWER9 bare metal , GDB
/linux/drivers/net/wireless/ti/wl18xx/
H A Dmain.c1394 s8 rom = 0, metal = 0, pg_ver = 0, rdl_ver = 0, package_type = 0; in wl18xx_get_pg_ver() local
1415 metal = (fuse & WL18XX_METAL_VER_MASK) >> in wl18xx_get_pg_ver()
1418 metal = (fuse & WL18XX_NEW_METAL_VER_MASK) >> in wl18xx_get_pg_ver()
1428 wl18xx_rdl_name(rdl_ver), pg_ver, metal, rom); in wl18xx_get_pg_ver()
/linux/Documentation/virt/hyperv/
H A Dvpci.rst13 would when running on bare metal, so no changes are required
50 metal system. Once those data structures are set up, the
53 were running in Linux on bare-metal. Because vPCI devices are
/linux/drivers/cxl/
H A DKconfig226 bare metal x86. However, for testing purposes toggling this option
/linux/arch/arm64/boot/dts/arm/
H A Djuno-base.dtsi663 /* The SMMU is only really of interest to bare-metal hypervisors */
/linux/Documentation/security/keys/
H A Dcore.rst298 00000892 I--QU- 1 perm 1f000000 0 0 user metal:copper: 0
299 00000893 I--Q-N 1 35s 1f3f0000 0 0 user metal:silver: 0
300 00000894 I--Q-- 1 10h 003f0000 0 0 user metal:gold: 0
/linux/Documentation/networking/device_drivers/can/ctu/
H A Dctucanfd-driver.rst273 either on bare metal or in a user-space application. Another advantage
/linux/Documentation/RCU/Design/Requirements/
H A DRequirements.rst1003 hypervisor), but can also happen in bare-metal environments due to