|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 1/4] x86/dom0: prevent access to MMCFG areas for PVH Dom0
On Thu, Aug 31, 2017 at 03:32:42PM +0800, Chao Gao wrote: > On Tue, Aug 29, 2017 at 08:33:25AM +0100, Roger Pau Monne wrote: > >On Mon, Aug 28, 2017 at 06:18:13AM +0000, Tian, Kevin wrote: > >> > From: Roger Pau Monne [mailto:roger.pau@xxxxxxxxxx] > >> > Sent: Friday, August 25, 2017 9:59 PM > >> > > >> > On Fri, Aug 25, 2017 at 06:25:36AM -0600, Jan Beulich wrote: > >> > > >>> On 25.08.17 at 14:15, <roger.pau@xxxxxxxxxx> wrote: > >> > > > On Wed, Aug 23, 2017 at 02:16:38AM -0600, Jan Beulich wrote: > >> > > >> >>> On 22.08.17 at 15:54, <roger.pau@xxxxxxxxxx> wrote: > >> > > >> > On Tue, Aug 22, 2017 at 06:26:23AM -0600, Jan Beulich wrote: > >> > > >> >> >>> On 11.08.17 at 18:43, <roger.pau@xxxxxxxxxx> wrote: > >> > > >> >> > --- a/xen/arch/x86/dom0_build.c > >> > > >> >> > +++ b/xen/arch/x86/dom0_build.c > >> > > >> >> > @@ -440,6 +440,10 @@ int __init > >> > dom0_setup_permissions(struct domain *d) > >> > > >> >> > rc |= rangeset_add_singleton(mmio_ro_ranges, mfn); > >> > > >> >> > } > >> > > >> >> > > >> > > >> >> > + /* For PVH prevent access to the MMCFG areas. */ > >> > > >> >> > + if ( dom0_pvh ) > >> > > >> >> > + rc |= pci_mmcfg_set_domain_permissions(d); > >> > > >> >> > >> > > >> >> What about ones reported by Dom0 later on? Which then raises the > >> > > >> >> question whether ... > >> > > >> > > >> > > >> > This should be dealt with in the PHYSDEVOP_pci_mmcfg_reserved > >> > handler. > >> > > >> > But since you propose to do white listing, I guess it doesn't > >> > > >> > matter > >> > > >> > that much anymore. > >> > > >> > >> > > >> Well, a fundamental question is whether white listing would work in > >> > > >> the first place. I could see room for severe problems e.g. with ACPI > >> > > >> methods wanting to access MMIO that's not described by any PCI > >> > > >> devices' BARs. Typically that would be regions in the chipset which > >> > > >> firmware is responsible for configuring/managing, the addresses of > >> > > >> which can be found/set in custom config space registers. > >> > > > > >> > > > The question would also be what would Xen allow in such > >> > > > white-listing. > >> > > > Obviously you can get to map the same using both white-list and > >> > > > black-listing (see below). > >> > > > >> > > Not really - what you've said there regarding MMCFG regions is > >> > > a clear indication that we should _not_ map reserved regions, i.e. > >> > > it would need to be full white listing with perhaps just the PCI > >> > > device BARs being handled automatically. > >> > > >> > I've tried just mapping the BARs and that sadly doesn't work, the box > >> > hangs after the IOMMU is enabled: > >> > > >> > [...] > >> > (XEN) [VT-D]d0:PCI: map 0000:3f:13.5 > >> > (XEN) [VT-D]d0:PCI: map 0000:3f:13.6 > >> > (XEN) [VT-D]iommu_enable_translation: iommu->reg = ffff82c00021b000 > >> > > >> > I will park this ATM and leave it for the Intel guys to diagnose. > >> > > >> > For the reference, the specific box I'm testing ATM has a Xeon(R) CPU > >> > E5-1607 0 @ 3.00GHz and a C600/X79 chipset. > >> > > >> > >> +Chao who can help check whether we have such a box at hand. > >> > >> btw please also give your BIOS version. > > > >It's a Precision T3600 BIOS A14. > > Hi, Roger. > > I found a Ivy bridge box with E5-2697 v2 and tested with "dom0=pvh", and > the bug didn't occur on this box. The log is below: > XEN) [ 7.509588] [VT-D]d0:PCIe: map 0000:ff:1e.2 > (XEN) [ 7.511047] [VT-D]d0:PCIe: map 0000:ff:1e.3 > (XEN) [ 7.512463] [VT-D]d0:PCIe: map 0000:ff:1e.4 > (XEN) [ 7.513927] [VT-D]d0:PCIe: map 0000:ff:1e.5 > (XEN) [ 7.515342] [VT-D]d0:PCIe: map 0000:ff:1e.6 > (XEN) [ 7.516808] [VT-D]d0:PCIe: map 0000:ff:1e.7 > (XEN) [ 7.519449] [VT-D]iommu_enable_translation: iommu->reg = > ffff82c00021b000 > (XEN) [ 7.522295] [VT-D]iommu_enable_translation: iommu->reg = > ffff82c00021d000 > (XEN) [ 8.675096] OS: linux version: 2.6 loader: generic bitness: > 64-bit > (XEN) [ 8.726763] > (XEN) [ 8.730171] **************************************** > (XEN) [ 8.737491] Panic on CPU 0: > (XEN) [ 8.742376] Building a PVHv2 Dom0 is not yet supported. > (XEN) [ 8.750148] **************************************** > (XEN) [ 8.757457] > (XEN) [ 8.760877] Reboot in five seconds... > (XEN) [ 13.769050] Resetting with ACPI MEMORY or I/O RESET_REG > > I agree with you that there may be some bugs in firmware and VT-d. > I did trials on a haswell box with iommu_inclusive_mapping=false. I did > see DMA traslation fault. The address to be translated is reserved in > e820 but isn't included in RMRR. Even that, the box booted up > successfully. > > But if the bug exists in pvh dom0, it also exists in pv dom0. Could you > try to boot with pv dom0 and set iommu_inclusive_mapping=false? > Theoretically, the system would halt exactly like what you met in > pvh dom0. Is that right? or I miss some difference between pvh dom0 and > pv dom0. Yes, the same happens with iommu_incluse_mapping=false on PV, the issue is not PVH specific. Here is the full dmesg: Xen 4.10-unstable (XEN) Xen version 4.10-unstable (root@) (FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)) debug=y Thu Aug 31 09:47:55 BST 2017 (XEN) Latest ChangeSet: (XEN) Console output is synchronous. (XEN) Bootloader: FreeBSD Loader (XEN) Command line: dom0_mem=4096M com1=115200,8n1 console=com1,vga guest_loglvl=all loglvl=all iommu=debug,verbose sync_console watchdog iommu_inclusive_mapping=false (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 2 MBR signatures (XEN) Found 2 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000008dc00 (usable) (XEN) 000000000008dc00 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 0000000018ebb000 (usable) (XEN) 0000000018ebb000 - 0000000018fe8000 (ACPI NVS) (XEN) 0000000018fe8000 - 0000000018fe9000 (usable) (XEN) 0000000018fe9000 - 0000000019000000 (ACPI NVS) (XEN) 0000000019000000 - 000000001dffd000 (usable) (XEN) 000000001dffd000 - 000000001e000000 (ACPI data) (XEN) 000000001e000000 - 00000000ac784000 (usable) (XEN) 00000000ac784000 - 00000000ac818000 (reserved) (XEN) 00000000ac818000 - 00000000ad800000 (usable) (XEN) 00000000b0000000 - 00000000b4000000 (reserved) (XEN) 00000000fed20000 - 00000000fed40000 (reserved) (XEN) 00000000fed50000 - 00000000fed90000 (reserved) (XEN) 00000000ffa00000 - 00000000ffa40000 (reserved) (XEN) 0000000100000000 - 0000000250000000 (usable) (XEN) New Xen image base address: 0xad200000 (XEN) ACPI: RSDP 000FE300, 0024 (r2 DELL ) (XEN) ACPI: XSDT 1DFFEE18, 0074 (r1 DELL CBX3 6222004 MSFT 10013) (XEN) ACPI: FACP 18FEFD98, 00F4 (r4 DELL CBX3 6222004 MSFT 10013) (XEN) ACPI: DSDT 18FA9018, 6373 (r1 DELL CBX3 0 INTL 20091112) (XEN) ACPI: FACS 18FF1F40, 0040 (XEN) ACPI: APIC 1DFFDC18, 0158 (r2 DELL CBX3 6222004 MSFT 10013) (XEN) ACPI: MCFG 18FFED18, 003C (r1 A M I OEMMCFG. 6222004 MSFT 97) (XEN) ACPI: TCPA 18FFEC98, 0032 (r2 0 0) (XEN) ACPI: SSDT 18FF0A98, 0306 (r1 DELLTP TPM 3000 INTL 20091112) (XEN) ACPI: HPET 18FFEC18, 0038 (r1 A M I PCHHPET 6222004 AMI. 3) (XEN) ACPI: BOOT 18FFEB98, 0028 (r1 DELL CBX3 6222004 AMI 10013) (XEN) ACPI: SSDT 18FB0018, 36FFE (r2 INTEL CpuPm 4000 INTL 20091112) (XEN) ACPI: SLIC 18FEEC18, 0176 (r3 DELL CBX3 6222004 MSFT 10013) (XEN) ACPI: DMAR 18FF1B18, 0094 (r1 A M I OEMDMAR 1 INTL 1) (XEN) System RAM: 8149MB (8345288kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-0000000250000000 (XEN) Domain heap initialised (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 45 (0x2d), Stepping 7 (raw 000206d7) (XEN) found SMP MP-table at 000f1db0 (XEN) DMI 2.6 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x408 (32 bits) (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:404,1:0], pm1x_evt[1:400,1:0] (XEN) ACPI: 32/64X FACS address mismatch in FADT - 18ffdf40/0000000018ff1f40, using 32 (XEN) ACPI: wakeup_vec[18ffdf4c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled) (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled) (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled) (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled) (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled) (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled) (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x10] disabled) (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x11] disabled) (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x12] disabled) (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x13] disabled) (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x14] disabled) (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x15] disabled) (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x16] disabled) (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x17] disabled) (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x18] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x19] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1a] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x1b] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x1c] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x1d] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x1e] disabled) (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x1f] disabled) (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x02] address[0xfec3f000] gsi_base[24]) (XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec3f000, GSI 24-47 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) [VT-D]Host address width 46 (XEN) [VT-D]found ACPI_DMAR_DRHD: (XEN) [VT-D] dmaru->address = fbffe000 (XEN) [VT-D]drhd->address = fbffe000 iommu->reg = ffff82c00021b000 (XEN) [VT-D]cap = d2078c106f0462 ecap = f020fa (XEN) [VT-D] IOAPIC: 0000:00:1f.7 (XEN) [VT-D] IOAPIC: 0000:00:05.4 (XEN) [VT-D] MSI HPET: 0000:f0:0f.0 (XEN) [VT-D] flags: INCLUDE_ALL (XEN) [VT-D]found ACPI_DMAR_RMRR: (XEN) [VT-D] endpoint: 0000:00:1d.0 (XEN) [VT-D] endpoint: 0000:00:1a.0 (XEN) [VT-D]dmar.c:638: RMRR region: base_addr ac7cf000 end_addr ac7defff (XEN) [VT-D]found ACPI_DMAR_RHSA: (XEN) [VT-D] rhsau->address: fbffe000 rhsau->proximity_domain: 0 (XEN) ERST table was not found (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 32 CPUs (28 hotplug CPUs) (XEN) IRQ limits: 48 GSI, 736 MSI/MSI-X (XEN) Switched to APIC driver x2apic_cluster. (XEN) xstate: size: 0x340 and states: 0x7 (XEN) mce_intel.c:763: MCA Capability: firstbank 0, extended MCE MSR 0, BCAST, SER, CMCI (XEN) CPU0: Intel machine check reporting enabled (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2992.801 MHz processor. (XEN) Initing memory sharing. (XEN) alt table ffff82d0804262c0 -> ffff82d080426a34 (XEN) PCI: MCFG configuration 0: base b0000000 segment 0000 buses 00 - 3f (XEN) PCI: MCFG area at b0000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-3f (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping enabled (XEN) nr_sockets: 9 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) TSC deadline timer enabled (XEN) Allocated console ring of 32 KiB. (XEN) mwait-idle: MWAIT substates: 0x21120 (XEN) mwait-idle: v0.4.1 model 0x2d (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) Brought up 4 CPUs (XEN) Testing NMI watchdog on all CPUs: ok (XEN) Running stub recovery selftests... (XEN) traps.c:1530: GPF (0000): ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d08034b0fa (XEN) traps.c:738: Trap 12: ffff82d0bffff040 [ffff82d0bffff040] -> ffff82d08034b0fa (XEN) traps.c:1068: Trap 3: ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d08034b0fa (XEN) ACPI sleep modes: S3 (XEN) VPMU: disabled (XEN) mcheck_poll: Machine check polling timer started. (XEN) Dom0 has maximum 624 PIRQs (XEN) NX (Execute Disable) protection active (XEN) *** LOADING DOMAIN 0 *** (XEN) ELF: phdr: paddr=0x200000 memsz=0x14d0dc8 (XEN) ELF: phdr: paddr=0x18d1000 memsz=0x6b05a8 (XEN) ELF: memory: 0x200000 -> 0x1f815a8 (XEN) ELF: note: GUEST_OS = "FreeBSD" (XEN) ELF: note: GUEST_VERSION = "0x124f9d" (XEN) ELF: note: XEN_VERSION = "xen-3.0" (XEN) ELF: note: VIRT_BASE = 0xffffffff80000000 (XEN) ELF: note: PADDR_OFFSET = 0 (XEN) ELF: note: ENTRY = 0xffffffff80eba000 (XEN) ELF: note: HYPERCALL_PAGE = 0xffffffff80eb9000 (XEN) ELF: note: HV_START_LOW = 0xffff800000000000 (XEN) ELF: note: FEATURES = "writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel|hvm_callback_vector" (XEN) ELF: note: PAE_MODE = "yes" (XEN) ELF: note: unknown (0xd) (XEN) ELF: note: LOADER = "generic" (XEN) ELF: note: SUSPEND_CANCEL = 0 (XEN) ELF: note: BSD_SYMTAB = "yes" (XEN) ELF: note: PHYS32_ENTRY = 0xeba030 (XEN) ELF: using notes from SHT_NOTE section (XEN) ELF: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff80200000 (XEN) virt_kend = 0xffffffff82272768 (XEN) virt_entry = 0xffffffff80eba000 (XEN) p2m_base = 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x200000 -> 0x1f815a8 (XEN) Dom0 symbol map 0x1f815a8 -> 0x2272768 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000244000000->0000000248000000 (1031217 pages to be allocated) (XEN) Init. ramdisk: 000000024fc31000->0000000250000000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff82272768 (XEN) Init. ramdisk: ffffffff82273000->ffffffff82642000 (XEN) Phys-Mach map: ffffffff82642000->ffffffff82e42000 (XEN) Start info: ffffffff82e42000->ffffffff82e424b4 (XEN) Page tables: ffffffff82e43000->ffffffff82e5e000 (XEN) Boot stack: ffffffff82e5e000->ffffffff82e5f000 (XEN) TOTAL: ffffffff80000000->ffffffff83000000 (XEN) ENTRY ADDRESS: ffffffff80eba000 (XEN) Dom0 has maximum 4 VCPUs (XEN) ELF: phdr 2 at 0xffffffff80200000 -> 0xffffffff816d0dc8 (XEN) ELF: phdr 3 at 0xffffffff818d1000 -> 0xffffffff81a1a7b8 (XEN) [VT-D]d0:Hostbridge: skip 0000:00:00.0 map (XEN) Masked UR signaling on 0000:00:00.0 (XEN) Masked UR signaling on 0000:00:01.0 (XEN) Masked UR signaling on 0000:00:01.1 (XEN) Masked UR signaling on 0000:00:02.0 (XEN) Masked UR signaling on 0000:00:03.0 (XEN) [VT-D]d0:PCIe: map 0000:00:05.0 (XEN) Masked VT-d error signaling on 0000:00:05.0 (XEN) [VT-D]d0:PCIe: map 0000:00:05.2 (XEN) [VT-D]d0:PCI: map 0000:00:05.4 (XEN) [VT-D]d0:PCI: map 0000:00:16.0 (XEN) [VT-D]d0:PCI: map 0000:00:19.0 (XEN) [VT-D]d0:PCI: map 0000:00:1a.0 (XEN) [VT-D]d0:PCIe: map 0000:00:1b.0 (XEN) [VT-D]d0:PCI: map 0000:00:1d.0 (XEN) [VT-D]d0:PCI: map 0000:00:1f.0 (XEN) [VT-D]d0:PCI: map 0000:00:1f.2 (XEN) [VT-D]d0:PCI: map 0000:00:1f.3 (XEN) [VT-D]d0:PCIe: map 0000:03:00.0 (XEN) [VT-D]d0:PCIe: map 0000:03:00.1 (XEN) [VT-D]d0:PCIe: map 0000:05:00.0 (XEN) [VT-D]d0:PCIe: map 0000:05:00.3 (XEN) [VT-D]d0:PCIe: map 0000:07:00.0 (XEN) [VT-D]d0:PCI: map 0000:3f:08.0 (XEN) [VT-D]d0:PCIe: map 0000:3f:08.3 (XEN) [VT-D]d0:PCIe: map 0000:3f:08.4 (XEN) [VT-D]d0:PCI: map 0000:3f:09.0 (XEN) [VT-D]d0:PCIe: map 0000:3f:09.3 (XEN) [VT-D]d0:PCIe: map 0000:3f:09.4 (XEN) [VT-D]d0:PCI: map 0000:3f:0a.0 (XEN) [VT-D]d0:PCI: map 0000:3f:0a.1 (XEN) [VT-D]d0:PCI: map 0000:3f:0a.2 (XEN) [VT-D]d0:PCI: map 0000:3f:0a.3 (XEN) [VT-D]d0:PCI: map 0000:3f:0b.0 (XEN) [VT-D]d0:PCI: map 0000:3f:0b.3 (XEN) [VT-D]d0:PCI: map 0000:3f:0c.0 (XEN) [VT-D]d0:PCI: map 0000:3f:0c.1 (XEN) [VT-D]d0:PCI: map 0000:3f:0c.6 (XEN) [VT-D]d0:PCI: map 0000:3f:0c.7 (XEN) [VT-D]d0:PCI: map 0000:3f:0d.0 (XEN) [VT-D]d0:PCI: map 0000:3f:0d.1 (XEN) [VT-D]d0:PCI: map 0000:3f:0d.6 (XEN) [VT-D]d0:PCI: map 0000:3f:0e.0 (XEN) [VT-D]d0:PCI: map 0000:3f:0e.1 (XEN) [VT-D]d0:PCIe: map 0000:3f:0f.0 (XEN) [VT-D]d0:PCIe: map 0000:3f:0f.1 (XEN) [VT-D]d0:PCIe: map 0000:3f:0f.2 (XEN) [VT-D]d0:PCIe: map 0000:3f:0f.3 (XEN) [VT-D]d0:PCIe: map 0000:3f:0f.4 (XEN) [VT-D]d0:PCIe: map 0000:3f:0f.5 (XEN) [VT-D]d0:PCI: map 0000:3f:0f.6 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.0 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.1 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.2 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.3 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.4 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.5 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.6 (XEN) [VT-D]d0:PCIe: map 0000:3f:10.7 (XEN) [VT-D]d0:PCI: map 0000:3f:11.0 (XEN) [VT-D]d0:PCI: map 0000:3f:13.0 (XEN) [VT-D]d0:PCI: map 0000:3f:13.1 (XEN) [VT-D]d0:PCI: map 0000:3f:13.4 (XEN) [VT-D]d0:PCI: map 0000:3f:13.5 (XEN) [VT-D]d0:PCI: map 0000:3f:13.6 (XEN) [VT-D]iommu_enable_translation: iommu->reg = ffff82c00021b000 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |