| /xen-4.10.0-shim-comet/tools/blktap2/control/ |
| A D | tap-ctl-major.c | 37 FILE *devices; in tap_ctl_blk_major() local
40 devices = fopen("/proc/devices", "r"); in tap_ctl_blk_major()
41 if (!devices) { in tap_ctl_blk_major()
50 s = fgets(buf, sizeof(buf), devices); in tap_ctl_blk_major()
65 if (devices) in tap_ctl_blk_major()
66 fclose(devices); in tap_ctl_blk_major()
|
| /xen-4.10.0-shim-comet/tools/blktap2/lvm/ |
| A D | lvm-util.c | 170 lvm_parse_lv_devices(struct vg *vg, struct lv_segment *seg, char *devices) in lvm_parse_lv_devices() argument
175 for (i = 0; i < strlen(devices); i++) in lvm_parse_lv_devices()
176 if (strchr(",()", devices[i])) in lvm_parse_lv_devices()
177 devices[i] = ' '; in lvm_parse_lv_devices()
179 if (sscanf(devices, _NAME" %"SCNu64, seg->device, &start) != 2) in lvm_parse_lv_devices()
221 char type[32], name[256], dev[256], devices[1024]; in lvm_scan_lvs() local
236 &seg.pe_size, devices) != 7) in lvm_scan_lvs()
247 if (lvm_parse_lv_devices(vg, &seg, devices)) in lvm_scan_lvs()
|
| /xen-4.10.0-shim-comet/docs/misc/ |
| A D | vtd.txt | 32 ls -l /sys/bus/pci/devices/0000:01:00.0/driver
42 13) add "pci" line in /etc/xen/hvm.conf for to assigned devices
80 12) add "pci" line in /etc/xen/hvm.conf for to assigned devices
86 Enable MSI/MSI-x for assigned devices
91 MSI-INTx translation for passthrough devices in HVM
117 There are some devices the BIOS controls, for e.g. USB devices to perform
142 VT-d spec specifies that all conventional PCI devices behind a
145 PCIe devices do not have this restriction.
214 Assigning devices to HVM domains
236 Such devices assigned to HVM domain currently do not work.
[all …]
|
| A D | hvm-emulated-unplug.markdown | 5 * Disconnecting emulated devices.
34 6. The drivers write a two-byte bitmask of devices to unplug to IO
43 The relevant emulated devices then disappear from the relevant
82 unplug of all NIC, IDE and SCSI devices. This was used in all SUSE
90 devices, or either NIC or storage. To control all devices the value 0x1
92 Device. This was supposed to unplug NIC, IDE and SCSI devices. If VMDP
93 was configured to control just NIC devices it would write the value 0x2
94 to offset 0x8. If VMDP was configured to control just storage devices it
|
| A D | pvh.markdown | 73 Description of paravirtualized devices will come from XenStore, just as it's
78 ### Interrupts from physical devices ###
80 Interrupts from physical devices are delivered using native methods, this is
83 devices will also have the necessary interrupt controllers in order to manage
84 the delivery of interrupts from those devices, using the same interfaces that
87 ### Interrupts from paravirtualized devices ###
89 Interrupts from paravirtualized devices are delivered using event channels, see
|
| A D | xsm-flask.txt | 9 interactions between domains, devices, and the hypervisor are permitted.
13 - Control which domains can use device passthrough (and which devices)
280 FLASK is capable of labeling devices and enforcing policies associated with
281 them. There are two methods to label devices: dynamic labeling using
286 the domain performing the labeling be trusted to label all the devices in the
289 IRQs, PCI devices, I/O memory and x86 IO ports can all have labels defined.
295 The "lspci -vvn" command can be used to output all the devices and identifiers
320 The AVC denials for IRQs, memory, ports, and PCI devices will normally contain
323 source/destination is printed to the log, so labeling devices using this method
|
| A D | vtd-pi.txt | 37 assigned devices (such as, NIC), external interrupt handling for the assigned
38 devices always needs VMM intervention.
51 virtual machines with assigned devices, migrating a vCPU across pCPUs
55 of an external interrupt from assigned devices is stored in the IRTE (i.e.
60 Here is what Xen currently does for external interrupts from assigned devices:
230 assigned devices issue interrupts. We need add a new global vector to
267 scheduling of the vCPU. When external interrupts from assigned devices occur,
317 from assigned devices is stored in IRTE, this makes the following
|
| A D | qemu-xen-security | 15 supported. All devices of one the above classes, which are not explicitly
|
| /xen-4.10.0-shim-comet/docs/misc/arm/device-tree/ |
| A D | passthrough.txt | 7 It is highly recommended to set this property on devices which are passed
8 through since many devices will not cope with being accessed by dom0 and
|
| /xen-4.10.0-shim-comet/docs/man/ |
| A D | xen-vbd-interface.markdown.7 | 4 A Xen guest can be provided with block devices. These are always
17 underlying devices as the corresponding Xen VBD (ie, multipath).
45 Non-whole disk devices cannot be passed through to HVM guests via
114 So for Linux PV guests, users are recommended to supply xvd* devices
115 only. Modern PV drivers will map these to identically-named devices
119 supply as few hd* devices as possible, and for the rest of the disks,
120 to use pure xvd* devices starting at xvde. Modern PV-on-HVM drivers
121 will map provided hd* devices to the corresponding /dev/xvd* (for
129 workaround is not to supply problematic combinations of devices.
|
| A D | xen-pci-device-reservations.pod.7 | 8 paravirtualisation features such as disk and network devices etc.
11 that can bind to virtual devices[1]. This may be done using the Xen PCI
78 devices. See hvm-emulated-unplug.markdown for details of the IO ports
|
| A D | xl.conf.pod.5 | 94 Configures the default hotplug script used by virtual network devices.
102 Configures the default bridge to set for virtual network devices.
110 Configures the default backend to set for virtual network devices.
116 Configures the default gateway device to set for virtual network devices.
|
| /xen-4.10.0-shim-comet/tools/examples/ |
| A D | README | 14 block-enbd - binds/unbinds network block devices
15 block-nbd - binds/unbinds network block devices
17 external-device-migrate - called by xend for migrating external devices
26 devices
|
| A D | xlexample.pvhlinux | 34 # Network devices
|
| A D | xlexample.pvlinux | 36 # Network devices
|
| A D | xlexample.hvm | 35 # Network devices
|
| /xen-4.10.0-shim-comet/xen/drivers/passthrough/vtd/ |
| A D | dmar.c | 89 xfree(scope->devices); in scope_devices_free()
90 scope->devices = NULL; in scope_devices_free()
335 scope->devices = xzalloc_array(u16, cnt); in acpi_parse_dev_scope()
336 if ( !scope->devices ) in acpi_parse_dev_scope()
533 b = PCI_BUS(dmaru->scope.devices[i]); in acpi_parse_one_drhd()
534 d = PCI_SLOT(dmaru->scope.devices[i]); in acpi_parse_one_drhd()
535 f = PCI_FUNC(dmaru->scope.devices[i]); in acpi_parse_one_drhd()
594 u8 b = PCI_BUS(rmrru->scope.devices[i]); in register_one_rmrr()
595 u8 d = PCI_SLOT(rmrru->scope.devices[i]); in register_one_rmrr()
596 u8 f = PCI_FUNC(rmrru->scope.devices[i]); in register_one_rmrr()
[all …]
|
| A D | dmar.h | 56 u16 *devices; /* devices owned by this unit */ member
99 for (idx = 0; (bdf = rmrr->scope.devices[idx]) && \
|
| /xen-4.10.0-shim-comet/tools/flask/policy/modules/ |
| A D | xen.te | 22 # devices that have not yet been labeled
46 # devices and use that label for allow rules
83 # The object role (object_r) is used for devices, resources, and event channels;
|
| A D | nic_dev.te | 6 # use flask-label-pci to dynamically label devices on each boot or define the
|
| /xen-4.10.0-shim-comet/tools/firmware/rombios/ |
| A D | rombios.c | 695 ata_device_t devices[BX_MAX_ATA_DEVICES];
2498 write_byte(ebda_seg,&EbdaData->ata.devices[device].removable,0);
2499 write_byte(ebda_seg,&EbdaData->ata.devices[device].lock,0);
2501 write_word(ebda_seg,&EbdaData->ata.devices[device].blksize,0);
2503 write_word(ebda_seg,&EbdaData->ata.devices[device].lchs.heads,0);
2505 write_word(ebda_seg,&EbdaData->ata.devices[device].lchs.spt,0);
2506 write_word(ebda_seg,&EbdaData->ata.devices[device].pchs.heads,0);
2508 write_word(ebda_seg,&EbdaData->ata.devices[device].pchs.spt,0);
2668 type=read_byte(ebda_seg,&EbdaData->ata.devices[device].type);
2921 type=read_byte(ebda_seg,&EbdaData->ata.devices[device].type);
[all …]
|
| /xen-4.10.0-shim-comet/tools/blktap2/ |
| A D | README | 15 virtual block devices presented to VMs to be implemented in userspace
32 and related tools) may be trivially applied to block devices.
47 implement individual block devices where desired. The userspace
117 devices and stop blktap2 drivers. This can be used to implement a
154 Previous versions of blktap mounted devices in dom0 by using blkfront
209 any number of tap devices. 0 is more common, meaning that you will
218 devices in this array and pad with "&null_disk," as necessary.
|
| /xen-4.10.0-shim-comet/tools/flask/policy/policy/ |
| A D | device_contexts | 3 # Label devices for delegation
|
| /xen-4.10.0-shim-comet/tools/console/testsuite/ |
| A D | README | 25 xmexample1 has no devices and no root set (this is what triggers /linuxrc).
|
| /xen-4.10.0-shim-comet/xen/common/ |
| A D | Kconfig | 99 devices.
149 domain 0 that manages devices without needing access to other
191 cores, targeted for avionics, drones, and medical devices.
|