Searched refs:metal (Results 1 – 25 of 26) sorted by relevance
12
| /Linux-v6.1/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 174 touch $resdir/bare-metal
175 echo To run this scenario on bare metal: >> $resdir/bare-metal
176 echo >> $resdir/bare-metal
177 echo " 1." Set your bare-metal build tree to the state shown in this file: >> $resdir/bare-metal
178 echo " " $testid_txt >> $resdir/bare-metal
179 echo " 2." Update your bare-metal build tree"'"s .config based on this file: >> $resdir/bare-metal
180 echo " " $resdir/ConfigFragment >> $resdir/bare-metal
181 echo " 3." Make the bare-metal kernel"'"s build system aware of your .config updates: >> $resdir/ba…
182 echo " " $ 'yes "" | make oldconfig' >> $resdir/bare-metal
183 echo " 4." Build your bare-metal kernel. >> $resdir/bare-metal
[all …]
|
| /Linux-v6.1/Documentation/virt/kvm/x86/ |
| D | running-nested-guests.rst | 31 - 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.
|
| D | errata.rst | 9 behavioral differences between virtual machines and bare metal systems.
|
| D | timekeeping.rst | 499 solving many of these problems on bare metal.
|
| /Linux-v6.1/Documentation/devicetree/bindings/arm/amlogic/ |
| D | analog-top.txt | 5 "metal revision" (which encodes the "minor version") of the SoC.
|
| /Linux-v6.1/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-rf-tuner.rst | 17 inside a metal box, while newer ones are highly integrated chips
18 without a metal box "silicon tuners". These controls are mostly
|
| /Linux-v6.1/Documentation/virt/acrn/ |
| D | introduction.rst | 6 The ACRN Hypervisor is a Type 1 hypervisor, running directly on bare-metal
|
| /Linux-v6.1/Documentation/admin-guide/media/ |
| D | frontend-cardlist.rst | 14 the demodulator and tuner/PLL chip are inside a metal box for
15 shielding, and the whole metal box has its own part number.
|
| D | bttv.rst | 555 #) These cards have a number printed on the PCB just above the tuner metal box:
|
| /Linux-v6.1/kernel/configs/ |
| D | debug.config | 2 # seek regressions on linux-next builds on different bare-metal and virtual
|
| /Linux-v6.1/arch/powerpc/platforms/cell/ |
| D | Kconfig | 61 bool "RAS features for bare metal Cell BE"
|
| /Linux-v6.1/drivers/net/wireless/ti/wl18xx/ |
| D | main.c | 1345 s8 rom = 0, metal = 0, pg_ver = 0, rdl_ver = 0, package_type = 0; in wl18xx_get_pg_ver() local
1366 metal = (fuse & WL18XX_METAL_VER_MASK) >> in wl18xx_get_pg_ver()
1369 metal = (fuse & WL18XX_NEW_METAL_VER_MASK) >> in wl18xx_get_pg_ver()
1379 wl18xx_rdl_name(rdl_ver), pg_ver, metal, rom); in wl18xx_get_pg_ver()
|
| /Linux-v6.1/Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 409 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-v6.1/Documentation/powerpc/ |
| D | dawr-power9.rst | 51 For GDB watchpoints (ie 'watch' command) on POWER9 bare metal , GDB
|
| /Linux-v6.1/Documentation/x86/ |
| D | tdx.rst | 25 TDX guests behave differently from bare-metal and traditional VMX guests.
73 these MSRs appear to function just as they would on bare metal.
|
| /Linux-v6.1/Documentation/virt/hyperv/ |
| D | clocks.rst | 11 driver, just as they would on bare metal. Linux vDSO support for the
|
| D | overview.rst | 7 consists primarily of a bare-metal hypervisor plus a virtual machine
|
| /Linux-v6.1/arch/arm64/boot/dts/arm/ |
| D | juno-base.dtsi | 664 /* The SMMU is only really of interest to bare-metal hypervisors */
|
| /Linux-v6.1/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 39 nested pagetables but almost always also on bare metal without
|
| D | memory-hotplug.rst | 466 environments that require it (e.g., bare metal
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | vfio.rst | 19 bare-metal device drivers [3]_.
|
| /Linux-v6.1/Documentation/security/keys/ |
| D | core.rst | 298 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-v6.1/Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 274 either on bare metal or in a user-space application. Another advantage
|
| /Linux-v6.1/arch/powerpc/ |
| D | Kconfig | 919 values. Useful for bare metal only. If unsure say Y here.
|
| /Linux-v6.1/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 1003 hypervisor), but can also happen in bare-metal environments due to
|
12
