Searched refs:Device (Results 1 – 25 of 40) sorted by relevance
12
| /xen/tools/libacpi/ |
| A D | dsdt.asl | 25 Device(MEM0)
40 Device (PCI0)
48 Device (VGA)
177 Device(HPET) {
200 Device (ISA)
213 Device (SYSR)
244 Device (PIC)
255 Device (DMA0)
271 Device (TMR)
281 Device (RTC)
[all …]
|
| A D | ssdt_tpm2.asl | 12 Device (TPM)
14 Name (_HID, "MSFT0101" /* TPM 2.0 Security Device */) // _HID: Hardware ID
|
| A D | ssdt_tpm.asl | 12 Device (TPM) {
|
| A D | ssdt_laptop_slate.asl | 16 Device (CONV) {
|
| A D | ssdt_pm.asl | 282 Device (AC)
328 Device (BAT0)
373 Device (BAT1)
|
| /xen/docs/ |
| A D | INDEX | 25 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 D | vtd.txt | 114 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 D | hvm-emulated-unplug.pandoc | 72 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
|
| A D | efi.pandoc | 201 The way to specify the domU domains is by Device Tree as specified in the
202 [dom0less](dom0less.html) documentation page under the "Device Tree
265 Device tree:
317 Device tree:
377 Device tree:
404 Device tree:
|
| /xen/xen/drivers/ |
| A D | Kconfig | 1 menu "Device Drivers"
|
| /xen/tools/flask/policy/modules/ |
| A D | nic_dev.te | 3 # Device delegation
|
| A D | domU.te | 19 # Device model for domU_t. You can define distinct types for device models for
|
| /xen/docs/misc/arm/device-tree/ |
| A D | passthrough.txt | 1 Device passthrough
|
| /xen/automation/eclair_analysis/ |
| A D | xen_arm_config | 105 # Device Drivers
120 # end of Device Drivers
|
| A D | xen_x86_config | 99 # Device Drivers
120 # end of Device Drivers
|
| /xen/docs/features/ |
| A D | dom0less.pandoc | 9 Booting Multiple Domains from Device Tree
14 hypervisor via Device Tree. Specifically, the existing Device Tree based
20 domains, but the system can start also without dom0 if the Device Tree
58 ### Device Tree configuration ###
|
| /xen/xen/arch/arm/configs/ |
| A D | tiny64_defconfig | 22 # Device Drivers
|
| /xen/docs/misc/arm/ |
| A D | passthrough.txt | 1 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 D | passthrough-noiommu.txt | 1 Request Device Assignment without IOMMU support
|
| A D | booting.txt | 15 Xen does not support the ATAG list and requires Device
|
| /xen/docs/designs/launch/ |
| A D | hyperlaunch.rst | 46 - The Device Tree specification for Hyperlaunch metadata
548 Device Tree as defined in the Hyperlaunch Device Tree design document. With the
549 LCM implemented in Device Tree, it has a magic number that enables the
552 compliant Hyperlaunch Device Tree. The Hyperlaunch Device Tree nodes are
560 Arm Device Tree
564 the Device Tree ecosystem, and in particular in parallel with dom0less Device
674 * For dom0less, guest Device Trees are dynamically constructed by the
682 ACPI and Device Tree methods.
853 in Device Tree binary format) is provided to the hypervisor
913 Device Tree
[all …]
|
| /xen/xen/ |
| A D | Kconfig.debug | 85 bool "Device tree debug messages"
88 Device tree parsing and DOM0 device tree building messages are
|
| /xen/xen/common/ |
| A D | README.source | 34 This directory was originally imported from the Device Tree
|
| /xen/xen/arch/x86/boot/ |
| A D | edd.S | 64 movb $0x48, %ah # 0x48 Get Device Parameters
|
| /xen/ |
| A D | SUPPORT.md | 725 See the appropriate "Device Passthrough" section
728 ### Device Model Stub Domains
736 ### Device Model Deprivileging
837 ### x86/PCI Device Passthrough
891 ### ARM: Guest Device Tree support
895 ### Device Tree Overlays
969 Status, Device Model Stub Domains: Supported, with caveats
974 trusted driver domains (see Device Model Stub Domains).
|
Completed in 43 milliseconds
12