Home
last modified time | relevance | path

Searched refs:Device (Results 1 – 25 of 34) sorted by relevance

12

/xen/tools/libacpi/
A Ddsdt.asl34 Device(MEM0)
49 Device (PCI0)
57 Device (VGA)
186 Device(HPET) {
209 Device (ISA)
222 Device (SYSR)
253 Device (PIC)
264 Device (DMA0)
280 Device (TMR)
290 Device (RTC)
[all …]
A Dssdt_tpm.asl21 Device (TPM) {
A Dssdt_laptop_slate.asl25 Device (CONV) {
A Dssdt_pm.asl291 Device (AC)
337 Device (BAT0)
382 Device (BAT1)
/xen/docs/
A DINDEX25 misc/arm/passthrough Passthrough a device described in the Device Tree to a guest
26 misc/arm/device-tree/booting Device tree bindings to boot Xen
27 misc/arm/device-tree/passthrough Device tree binding to passthrough a device
/xen/docs/misc/
A Dvtd.txt114 RDM, 'reserved device memory', for PCI Device Passthrough
139 Caveat on Conventional PCI Device Passthrough
223 * Device has an internal resource, such as private memory, which is
261 VF offset: 128, stride: 2, Device ID: 10ca
274 01:10.0 Ethernet controller: Intel Corporation Device 10ca (rev 01)
275 01:10.2 Ethernet controller: Intel Corporation Device 10ca (rev 01)
276 01:10.4 Ethernet controller: Intel Corporation Device 10ca (rev 01)
277 01:10.6 Ethernet controller: Intel Corporation Device 10ca (rev 01)
278 01:11.0 Ethernet controller: Intel Corporation Device 10ca (rev 01)
279 01:11.2 Ethernet controller: Intel Corporation Device 10ca (rev 01)
[all …]
A Dhvm-emulated-unplug.pandoc72 as part of the Xen Platform PCI Device, so if that device is not
80 0x4 in the memory region of the Xen Platform PCI Device. This was done
92 Device. This was supposed to unplug NIC, IDE and SCSI devices. If VMDP
/xen/xen/drivers/
A DKconfig1 menu "Device Drivers"
/xen/tools/flask/policy/modules/
A Dnic_dev.te3 # Device delegation
A DdomU.te16 # Device model for domU_t. You can define distinct types for device models for
A Dxen.if168 # Device types and delegation (PCI passthrough)
/xen/docs/misc/arm/device-tree/
A Dpassthrough.txt1 Device passthrough
A Dbooting.txt242 Device Assignment
245 Device Assignment (Passthrough) is supported by adding another module,
/xen/docs/features/
A Ddom0less.pandoc9 Booting Multiple Domains from Device Tree
14 hypervisor via Device Tree. Specifically, the existing Device Tree based
57 ### Device Tree configuration ###
/xen/xen/arch/arm/configs/
A Dtiny64_defconfig22 # Device Drivers
/xen/docs/misc/arm/
A Dpassthrough.txt1 Passthrough a device described in the Device Tree to a guest
58 3) Compile the partial guest device with dtc (Device Tree Compiler).
84 Dom0-less Device Passthrough
102 The memory will be mapped as device memory in the guest (Device-nGnRE).
A Dbooting.txt15 Xen does not support the ATAG list and requires Device
/xen/xen/
A DKconfig.debug93 bool "Device tree debug messages"
96 Device tree parsing and DOM0 device tree building messages are
/xen/xen/common/
A DREADME.source34 This directory was originally imported from the Device Tree
/xen/
A DSUPPORT.md558 See the appropriate "Device Passthrough" section
561 ### Device Model Stub Domains
569 ### Device Model Deprivileging
662 ### x86/PCI Device Passthrough
703 ### ARM: Guest Device Tree support
775 Status, Device Model Stub Domains: Supported, with caveats
780 trusted driver domains (see Device Model Stub Domains).
/xen/xen/arch/x86/boot/
A Dedd.S64 movb $0x48, %ah # 0x48 Get Device Parameters
/xen/tools/ocaml/libs/xl/
A Dxenlight.mli.in35 | POLLHUP (* Device has been disconnected (revents only) *)
A Dxenlight.ml.in33 | POLLHUP (* Device has been disconnected (revents only) *)
/xen/xen/include/efi/
A Defidevp.h81 UINT8 Device; member
/xen/xen/common/efi/
A Dboot.c56 IN const EFI_DEVICE_PATH *Device,
64 IN const EFI_DEVICE_PATH *Device,
72 IN const EFI_DEVICE_PATH *Device,

Completed in 23 milliseconds

12