WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-devel] Re: VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3

from [Christian Tramnitz] [Permanent Link][Original]
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1
From: Christian Tramnitz <chris.ace@xxxxxxx>
Date: Mon, 28 Sep 2009 12:38:19 +0200
Delivery-date: Mon, 28 Sep 2009 03:39:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <715D42877B251141A38726ABF5CABF2C05507CF699@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <e8f0b580909270835x684b0a25q5386477f8100784@xxxxxxxxxxxxxx> <C6E55FAC.15D49%keir.fraser@xxxxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C05507CF699@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (Windows/20090812) 
Han, Weidong wrote:

Yes, the other people should not succeed on the same motherboard with the same 
BIOS, unless they used an old xen version without this check. USB controllers 
and integrated graphics card will use RMRR. I suspect it can work with this 
broken BIOS even you remove the check and don't disable VT-d.

Regards,
Weidong
I'm the one with working VT-d on this board (using the same BIOS version than Michael). I was using an older 3.4.0-pre but now switched to the latest 3.5-unstable and its still working. I haven't tried to actually pass-through a device for some time but it was already working in the past. 

Attached my xm dmesg.
I also agree with Sander's comment in this thread, that we should mark "unwilling" vendors in the VT-d section of the Wiki. I'll add notes to all Asus boards (basically this one and the P6T Deluxe that I also own and had problems with). 


Best regards,
  Christian

 __  __            _____  ____                     _        _     _      
 \ \/ /___ _ __   |___ / | ___|    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ \047_ \    |_ \ |___ \ __| | | | \047_ \/ __| __/ _` | \047_ \| |/ 
_ \
  /  \  __/ | | |  ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                         
(XEN) Xen version 3.5-unstable (root@xxxxxxxxxxxxx) (gcc version 4.1.2 (Gentoo 
4.1.2 p1.0.2)) Sat Sep 12 11:57:50 CEST 2009
(XEN) Latest ChangeSet: Tue Sep 22 14:19:38 2009 +0100 20247:8b1567102cf3
(XEN) Command line: iommu=1 iommu_inclusive_mapping=1
(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 0 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cf550000 (usable)
(XEN)  00000000cf550000 - 00000000cf55e000 (ACPI data)
(XEN)  00000000cf55e000 - 00000000cf5e0000 (ACPI NVS)
(XEN)  00000000cf5e0000 - 00000000cf600000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffc00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000022c000000 (usable)
(XEN) ACPI: RSDP 000F9A80, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT CF550100, 0064 (r1 A_M_I_ OEMXSDT   3000831 MSFT       97)
(XEN) ACPI: FACP CF550290, 00F4 (r3 A_M_I_ OEMFACP   3000831 MSFT       97)
(XEN) ACPI: DSDT CF5505C0, 843B (r1  A0869 A0869001        1 INTL 20060113)
(XEN) ACPI: FACS CF55E000, 0040
(XEN) ACPI: APIC CF550390, 006C (r1 A_M_I_ OEMAPIC   3000831 MSFT       97)
(XEN) ACPI: MCFG CF550400, 003C (r1 A_M_I_ OEMMCFG   3000831 MSFT       97)
(XEN) ACPI: OEMB CF55E040, 0081 (r1 A_M_I_ AMI_OEM   3000831 MSFT       97)
(XEN) ACPI: HPET CF558A00, 0038 (r1 A_M_I_ OEMHPET   3000831 MSFT       97)
(XEN) ACPI: GSCI CF55E0D0, 2024 (r1 A_M_I_ GMCHSCI   3000831 MSFT       97)
(XEN) ACPI: iEIT CF560100, 00B0 (r1 A_M_I_ EITTABLE  3000831 MSFT       97)
(XEN) ACPI: DMAR CF5601B0, 0140 (r1    AMI  OEMDMAR        1 MSFT       97)
(XEN) System RAM: 8105MB (8299984kB)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-000000022c000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000ff780
(XEN) DMI 2.4 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
(XEN) ACPI:                  wakeup_vec[cf55e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 6:15 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(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 1 I/O APICs
(XEN) ACPI: HPET id: 0xffffffff base: 0xfed00000
(XEN) [VT-D]dmar.c:537: Host address width 36
(XEN) [VT-D]dmar.c:546: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:373: dmaru->address = fed91000
(XEN) [VT-D]dmar.c:325: endpoint: 0:2.0
(XEN) [VT-D]dmar.c:546: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:373: dmaru->address = fed92000
(XEN) [VT-D]dmar.c:325: endpoint: 0:3.0
(XEN) [VT-D]dmar.c:546: found ACPI_DMAR_DRHD
(XEN) [VT-D]dmar.c:373: dmaru->address = fed93000
(XEN) [VT-D]dmar.c:385: found INCLUDE_ALL
(XEN) [VT-D]dmar.c:550: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:550: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:428: RMRR address range not in reserved memory base = 
cf600000 end = cfffffff; iommu_inclusive_mapping=1 parameter may be needed.
(XEN) [VT-D]dmar.c:325: endpoint: 0:2.0
(XEN) [VT-D]dmar.c:550: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:325: endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:325: endpoint: 0:1a.7
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: Not using MMCONFIG.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 3000.062 MHz processor.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 4096K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU0 has no CMCI support
(XEN) [VT-D]iommu.c:943: drhd->address = fed92000
(XEN) [VT-D]iommu.c:944: iommu->reg = ffff82c3fff57000
(XEN) [VT-D]iommu.c:943: drhd->address = fed91000
(XEN) [VT-D]iommu.c:944: iommu->reg = ffff82c3fff56000
(XEN) [VT-D]iommu.c:943: drhd->address = fed93000
(XEN) [VT-D]iommu.c:944: iommu->reg = ffff82c3fff55000
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation not supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz stepping 0b
(XEN) Booting processor 1/1 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 4096K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU: Processor Core ID: 1
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM2)
(XEN) CMCI: CPU1 has no CMCI support
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz stepping 0b
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:0.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:3.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:19.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1f.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1f.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1f.3
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1f.6
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.1
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.3
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.4
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.5
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.6
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 1:1.7
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.1
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1d.7
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.0
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.1
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.2
(XEN) [VT-D]iommu.c:1182:d32767 domain_context_mapping:PCI: bdf = 0:1a.7
(XEN) [VT-D]iommu.c:632: iommu_enable_translation: iommu->reg = ffff82c3fff57000
(XEN) [VT-D]iommu.c:632: iommu_enable_translation: iommu->reg = ffff82c3fff56000
(XEN) [VT-D]iommu.c:716: iommu_page_fault: iommu->reg = ffff82c3fff56000
(XEN) [VT-D]iommu.c:685: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:688: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:670: iommu_fault:DMA Write: 0:2.0 addr 400000000 REASON 5 
iommu->reg = ffff82c3fff56000
(XEN) print_vtd_entries: iommu = ffff8302263f30d0 bdf = 0:2:0 gmfn = 400000
(XEN)     root_entry = ffff8302263f0000
(XEN)     root_entry[0] = 225255001
(XEN)     context = ffff830225255000
(XEN)     context[10] = 101_2263c0001
(XEN)     l3 = ffff8302263c0000
(XEN)     l3_index = 10
(XEN)     l3[10] = 0
(XEN)     l3[10] not present
(XEN) [VT-D]iommu.c:632: iommu_enable_translation: iommu->reg = ffff82c3fff55000
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x200000 memsz=0x403000
(XEN) elf_parse_binary: phdr: paddr=0x603000 memsz=0x6ca40
(XEN) elf_parse_binary: phdr: paddr=0x670000 memsz=0x888
(XEN) elf_parse_binary: phdr: paddr=0x672000 memsz=0x1b92d4
(XEN) elf_parse_binary: memory: 0x200000 -> 0x82b2d4
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80207000
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: INIT_P2M = 0xffffe20000000000
(XEN) elf_xen_parse_note: FEATURES = 
"writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0x0
(XEN)     virt_offset      = 0xffffffff80000000
(XEN)     virt_kstart      = 0xffffffff80200000
(XEN)     virt_kend        = 0xffffffff8082b2d4
(XEN)     virt_entry       = 0xffffffff80200000
(XEN)     p2m_base         = 0xffffe20000000000
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x82b2d4
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000224000000->0000000225000000 (2012285 pages to be 
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff80200000->ffffffff8082b2d4
(XEN)  Init. ramdisk: ffffffff8082c000->ffffffff8082c000
(XEN)  Phys-Mach map: ffffe20000000000->ffffe20000f623e8
(XEN)  Start info:    ffffffff8082c000->ffffffff8082c4b4
(XEN)  Page tables:   ffffffff8082d000->ffffffff80836000
(XEN)  Boot stack:    ffffffff80836000->ffffffff80837000
(XEN)  TOTAL:         ffffffff80000000->ffffffff80c00000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff80603000
(XEN) elf_load_binary: phdr 1 at 0xffffffff80603000 -> 0xffffffff8066fa40
(XEN) elf_load_binary: phdr 2 at 0xffffffff80670000 -> 0xffffffff80670888
(XEN) elf_load_binary: phdr 3 at 0xffffffff80672000 -> 0xffffffff806baa20
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input 
to Xen)
(XEN) Freed 152kB init memory.
(XEN) io_apic.c:2208: 
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=00000900
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:02.0
(XEN) PCI add device 00:03.0
(XEN) PCI add device 00:19.0
(XEN) PCI add device 00:1a.0
(XEN) PCI add device 00:1a.1
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1a.7
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) PCI add device 00:1d.2
(XEN) PCI add device 00:1d.7
(XEN) PCI add device 00:1e.0
(XEN) PCI add device 00:1f.0
(XEN) PCI add device 00:1f.2
(XEN) PCI add device 00:1f.3
(XEN) PCI add device 00:1f.6
(XEN) PCI add device 01:01.0
(XEN) Set CPU acpi_id(1) cpuid(0) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=64, 
bit_offset=0, reserved=0, address=409
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=16, 
bit_offset=0, reserved=0, address=408
(XEN)   _PSS: state_count=2
(XEN)   State0: 2997MHz 88000mW 10us 10us 0x928 0x928
(XEN)   State1: 1998MHz 52800mW 10us 10us 0x618 0x618
(XEN)   _PSD: num_entries=5 rev=0 domain=0 coord_type=254 num_processors=2
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 0 initialization completed
(XEN) Set CPU acpi_id(2) cpuid(1) Px State info:
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=64, 
bit_offset=0, reserved=0, address=409
(XEN)   _PCT: descriptor=130, length=12, space_id=127, bit_width=16, 
bit_offset=0, reserved=0, address=408
(XEN)   _PSS: state_count=2
(XEN)   State0: 2997MHz 88000mW 10us 10us 0x928 0x928
(XEN)   State1: 1998MHz 52800mW 10us 10us 0x618 0x618
(XEN)   _PSD: num_entries=5 rev=0 domain=0 coord_type=254 num_processors=2
(XEN)   _PPC: 0
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 1 initialization completed
(XEN) no cpu_id for acpi_id 3
(XEN) no cpu_id for acpi_id 4
(XEN) PCI add device 00:00.0
(XEN) PCI add device 00:19.0
(XEN) allocated vector for irq:20
(XEN) allocated vector for irq:17
(XEN) PCI add device 00:1f.2
(XEN) allocated vector for irq:22
(XEN) PCI add device 00:1a.7
(XEN) allocated vector for irq:18
(XEN) PCI add device 00:1d.7
(XEN) allocated vector for irq:23
(XEN) PCI add device 00:1a.0
(XEN) allocated vector for irq:16
(XEN) PCI add device 00:1a.1
(XEN) allocated vector for irq:21
(XEN) PCI add device 00:1a.2
(XEN) PCI add device 00:1d.0
(XEN) PCI add device 00:1d.1
(XEN) allocated vector for irq:19
(XEN) PCI add device 00:1d.2

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] [PATCH] Support Integrated graphics passthrough, Han, Weidong
Next by Date:  Re: [Xen-devel] Re: VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1, Keir Fraser
Previous by Thread:  RE: [Xen-devel] VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1, Han, Weidong
Next by Thread:  Re: [Xen-devel] Re: VT-D On An Asus P5E-VM DO Motherboard Not Working, Xen 3.4.1, Keir Fraser
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy