Home
last modified time | relevance | path

Searched full:virtualized (Results 1 – 25 of 121) sorted by relevance

12345

/linux/sound/xen/
H A DKconfig5 tristate "Xen para-virtualized sound frontend driver"
11 Choose this option if you want to enable a para-virtualized
/linux/drivers/gpu/drm/xen/
H A DKconfig6 tristate "Para-virtualized frontend driver for Xen guest OS"
14 Choose this option if you want to enable a para-virtualized
/linux/drivers/cpuidle/
H A DKconfig37 bool "Haltpoll governor (for virtualized systems)"
45 Some virtualized workloads benefit from using it.
/linux/Documentation/ABI/testing/
H A Dsysfs-hypervisor-xen8 "HVM": fully virtualized guest (x86)
10 "PVH": fully virtualized guest without legacy emulation (x86)
/linux/Documentation/gpu/
H A Dxen-front.rst2 drm/xen-front Xen para-virtualized frontend driver
5 This frontend driver implements Xen para-virtualized display
/linux/drivers/net/ethernet/qlogic/
H A DKconfig44 This allows for virtual function acceleration in virtualized
96 This allows for virtual function acceleration in virtualized
/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dmsi-pic.txt37 This property may be used in virtualized environments where the hypervisor
87 In a virtualized environment, the hypervisor may need to create an IOMMU
/linux/arch/x86/include/asm/xen/
H A Dcpuid.h108 #define XEN_HVM_CPUID_APIC_ACCESS_VIRT (1u << 0) /* Virtualized APIC registers */
109 #define XEN_HVM_CPUID_X2APIC_VIRT (1u << 1) /* Virtualized x2APIC accesses */
/linux/include/xen/interface/
H A Dsched.h81 * in interpreting shutdown requests and reasons for fully-virtualized
82 * domains. A para-virtualized domain may use SCHEDOP_shutdown directly.
/linux/arch/powerpc/platforms/powernv/
H A DKconfig4 bool "IBM PowerNV (Non-Virtualized) platform support"
/linux/Documentation/devicetree/bindings/iommu/
H A Dxen,grant-dma.yaml7 title: Xen specific IOMMU for virtualized devices (e.g. virtio)
/linux/Documentation/virt/kvm/x86/
H A Dtimekeeping.rst321 timer device would require additional support to be virtualized properly and is
547 Since CPUID may actually be virtualized by a trap and emulate mechanism, this
624 Precise timing and delays may not be possible in a virtualized system. This
627 in general for a virtualized system; hardware control software can't be
628 adequately virtualized without a full real-time operating system, which would
639 guest about the host in anything but a perfect implementation of virtualized
/linux/drivers/net/ethernet/sfc/siena/
H A DKconfig36 virtualized environments.
/linux/drivers/dma/qcom/
H A DKconfig42 start managing the channels. In a virtualized environment,
/linux/Documentation/security/
H A Dsnp-tdx-threat-model.rst12 Kernel developers working on confidential computing for virtualized
32 that are targeting virtualized environments and allow running Virtual
35 virtualized environments (VE)'.
/linux/drivers/gpu/drm/xe/
H A Dxe_sriov_types.h27 * @XE_SRIOV_MODE_NONE: bare-metal mode (non-virtualized)
/linux/arch/arm64/kvm/
H A DKconfig42 Support hosting virtualized guest machines.
/linux/Documentation/admin-guide/hw-vuln/
H A Dmultihit.rst8 or cache type. A malicious guest running on a virtualized system can
63 guests in a virtualized system.
H A Dtsx_async_abort.rst248 disabled. The same applies to virtualized environments with trusted guests.
259 are prevented in a virtualized environment as well, even if the VMs do not
/linux/tools/testing/selftests/net/tcp_ao/lib/
H A Dsetup.c287 * It is not virtualized in v6.7, so it has to written outside test
293 * it is per-namespace, keeping logic for non-virtualized optmem_max
/linux/drivers/net/ethernet/sfc/
H A DKconfig58 virtualized environments.
/linux/net/openvswitch/
H A DKconfig22 Open vSwitch is a multilayer Ethernet switch targeted at virtualized
/linux/include/xen/interface/io/
H A Dsndif.h192 * Every virtualized sound frontend has a set of PCM devices and streams, each
363 * the virtualized device. If this is possible at the moment of error,
365 * new connection with backend. If the virtualized device is still in use and
367 * until either the virtualized device removed or backend initiates a new
368 * connection. On the virtualized device removal frontend goes into the
373 * and thus cannot provide functionality of the virtualized device anymore.
374 * After backend is back to normal the virtualized device may still hold some
378 * frontend will make sure no new clients of the virtualized device are
381 * Once all the clients are gone frontend can reinitialize the virtualized
389 * client of the virtualized device has gone and the device can be removed
[all …]
H A Ddisplif.h295 * the virtualized device. If this is possible at the moment of error,
297 * new connection with backend. If the virtualized device is still in use and
299 * until either the virtualized device is removed or backend initiates a new
300 * connection. On the virtualized device removal frontend goes into the
305 * and thus cannot provide functionality of the virtualized device anymore.
306 * After backend is back to normal the virtualized device may still hold some
310 * frontend will make sure no new clients of the virtualized device are
313 * Once all the clients are gone frontend can reinitialize the virtualized
321 * client of the virtualized device has gone and the device can be removed
324 * the virtualized device.
/linux/include/video/
H A Dudlfb.h41 bool virtualized; /* true when physical usb device not present */ member

12345