c4pt4inkrunch@gmail.com
2010-Apr-24 20:08 UTC
[Xen-devel] trying to get vt-d working with xen 4.0.0 stable + 2.6.32.10 pvops kernel with .config file from the
here is my xm dmesg i was wondering if anyone knew about these DMAR listings in the vt-d section of the dmesg (with iommu=verbose at boot) __ __ _ _ ___ ___ \ \/ /___ _ __ | || | / _ \ / _ \ \ // _ \ ''_ \ | || |_| | | | | | | / \ __/ | | | |__ _| |_| | |_| | /_/\_\___|_| |_| |_|(_)___(_)___/ (XEN) Xen version 4.0.0 (root@) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) Sat Apr 24 15:16:24 EDT 2010 (XEN) Latest ChangeSet: unavailable (XEN) Command line: dom0_mem=1024M iommu=verbose (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 3 MBR signatures (XEN) Found 3 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009e000 (usable) (XEN) 000000000009e000 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007ecce000 (usable) (XEN) 000000007ecce000 - 000000007ed48000 (ACPI NVS) (XEN) 000000007ed48000 - 000000007fdb2000 (usable) (XEN) 000000007fdb2000 - 000000007fdb4000 (reserved) (XEN) 000000007fdb4000 - 000000007fe6d000 (usable) (XEN) 000000007fe6d000 - 000000007fe78000 (ACPI NVS) (XEN) 000000007fe78000 - 000000007fe7d000 (ACPI data) (XEN) 000000007fe7d000 - 000000007fee5000 (ACPI NVS) (XEN) 000000007fee5000 - 000000007fef2000 (ACPI data) (XEN) 000000007fef2000 - 000000007fef3000 (usable) (XEN) 000000007fef3000 - 000000007feff000 (ACPI data) (XEN) 000000007feff000 - 000000007ff00000 (usable) (XEN) 000000007ff00000 - 0000000080000000 (reserved) (XEN) 00000000f0000000 - 00000000f8000000 (reserved) (XEN) 00000000ffe00000 - 0000000100000000 (reserved) (XEN) System RAM: 1878MB (1924000kB) (XEN) ACPI: RSDP 000FE020, 0014 (r0 INTEL ) (XEN) ACPI: RSDT 7FEFD038, 0084 (r1 INTEL D5400XS 549 1000013) (XEN) ACPI: FACP 7FEFC000, 0074 (r1 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: DSDT 7FEF8000, 3C26 (r1 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: FACS 7FE7D000, 0040 (XEN) ACPI: APIC 7FEF7000, 00D4 (r1 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: WDDT 7FEF6000, 0040 (r1 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: MCFG 7FEF5000, 003C (r1 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: ASF! 7FEF4000, 00A7 (r32 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: HPET 7FEF3000, 0038 (r1 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: DMAR 7FEF1000, 00C8 (r1 INTEL D5400XS 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEF0000, 03CC (r1 INTEL CpuPm 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEEF000, 0175 (r1 INTEL Cpu0Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEEE000, 0175 (r1 INTEL Cpu1Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEED000, 0175 (r1 INTEL Cpu2Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEEC000, 0175 (r1 INTEL Cpu3Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEEB000, 0175 (r1 INTEL Cpu4Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEEA000, 0175 (r1 INTEL Cpu5Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEE9000, 0175 (r1 INTEL Cpu6Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEE8000, 0175 (r1 INTEL Cpu7Ist 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEE7000, 00DD (r1 INTEL Cpu0Cst 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEE6000, 00DD (r1 INTEL Cpu1Cst 549 MSFT 1000013) (XEN) ACPI: SSDT 7FEE5000, 00DD (r1 INTEL Cpu2Cst 549 MSFT 1000013) (XEN) ACPI: SSDT 7FE7C000, 00DD (r1 INTEL Cpu3Cst 549 MSFT 1000013) (XEN) ACPI: SSDT 7FE7B000, 00DD (r1 INTEL Cpu4Cst 549 MSFT 1000013) (XEN) ACPI: SSDT 7FE7A000, 00DD (r1 INTEL Cpu5Cst 549 MSFT 1000013) (XEN) ACPI: SSDT 7FE79000, 00DD (r1 INTEL Cpu6Cst 549 MSFT 1000013) (XEN) ACPI: SSDT 7FE78000, 00DD (r1 INTEL Cpu7Cst 549 MSFT 1000013) (XEN) Xen heap: 8MB (8856kB) (XEN) Domain heap initialised (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #4 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) Processor #5 7:7 APIC version 20 (XEN) Processor #2 7:7 APIC version 20 (XEN) Processor #6 7:7 APIC version 20 (XEN) Processor #3 7:7 APIC version 20 (XEN) Processor #7 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) IOAPIC[1]: apic_id 9, version 255, address 0xfec88000, GSI 24-279 (XEN) IOAPIC[2]: apic_id 10, version 255, address 0xfec90000, GSI 48-303 (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs (XEN) [VT-D]dmar.c:679: Host address width 40 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe710000 (XEN) [VT-D]dmar.c:320: bridge: 0:1.0 start = 0 sec = 1 sub = 4 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe714000 (XEN) [VT-D]dmar.c:320: bridge: 0:5.0 start = 0 sec = 5 sub = 8 (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe718000 (XEN) [VT-D]dmar.c:411: flags: INCLUDE_ALL (XEN) [VT-D]dmar.c:694: found ACPI_DMAR_DRHD: (XEN) [VT-D]dmar.c:398: dmaru->address = fe71a000 (XEN) [VT-D]dmar.c:334: endpoint: 0:f.0 (XEN) [VT-D]dmar.c:699: found ACPI_DMAR_RMRR: (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.0 (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.1 (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.2 (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.3 (XEN) [VT-D]dmar.c:334: endpoint: 0:1d.7 (XEN) [VT-D]dmar.c:571: RMRR region: base_addr e0000 end_address effff (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2327.572 MHz processor. (XEN) Initing memory sharing. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs disabled. (XEN) HVM: VMX enabled (XEN) [VT-D]iommu.c:1078: drhd->address = fe71a000 iommu->reg = fff17000 (XEN) [VT-D]iommu.c:1080: cap = ffffffffffffffff ecap = ffffffffffffffff (XEN) [VT-D]iommu.c:1086: IOMMU: unsupported (XEN) ---- print_iommu_regs ---- (XEN) drhd->address = fe71a000 (XEN) VER = ffffffff (XEN) CAP = ffffffffffffffff (XEN) n_fault_reg = 100 (XEN) fault_recording_offset = 3ff0 (XEN) ECAP = ffffffffffffffff (XEN) GCMD = ffffffff (XEN) GSTS = ffffffff (XEN) RTADDR = ffffffffffffffff (XEN) CCMD = ffffffffffffffff (XEN) FSTS = ffffffff (XEN) FECTL = ffffffff (XEN) FEDATA = ffffffff (XEN) FEADDR = ffffffff (XEN) FEUADDR = ffffffff (XEN) I/O virtualisation disabled (XEN) Total of 8 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 8 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 16 KiB. (XEN) Brought up 8 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 32-bit, PAE, lsb (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0x400000 -> 0xac5000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000020000000->0000000030000000 (196608 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0400000->c0ac5000 (XEN) Init. ramdisk: c0ac5000->c9d52e00 (XEN) Phys-Mach map: c9d53000->c9e53000 (XEN) Start info: c9e53000->c9e5347c (XEN) Page tables: c9e54000->c9ea9000 (XEN) Boot stack: c9ea9000->c9eaa000 (XEN) TOTAL: c0000000->ca000000 (XEN) ENTRY ADDRESS: c088e000 (XEN) Dom0 has maximum 8 VCPUs (XEN) Scrubbing Free RAM: ..........done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 136kB init memory. root@Phoenix:~# _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-May-04 14:49 UTC
Re: [Xen-devel] trying to get vt-d working with xen 4.0.0 stable + 2.6.32.10 pvops kernel with .config file from the
On Sat, Apr 24, 2010 at 08:08:56PM +0000, c4pt4inkrunch@gmail.com wrote:> here is my xm dmesg i was wondering if anyone knew about these DMAR.. snip..> (XEN) [VT-D]iommu.c:1078: drhd->address = fe71a000 iommu->reg = fff17000 > (XEN) [VT-D]iommu.c:1080: cap = ffffffffffffffff ecap = ffffffffffffffff > (XEN) [VT-D]iommu.c:1086: IOMMU: unsupportedLine 1086. 1083 if ( cap_fault_reg_offset(iommu->cap) + 1084 cap_num_fault_regs(iommu->cap) * PRIMARY_FAULT_REG_LEN >PAGE_SIZE || 1085 ecap_iotlb_offset(iommu->ecap) >= PAGE_SIZE ) 1086 { The iommu->cap and iommu->ecap are used. And as you can see below the values are all 0xfffffffffffffffff which are pretty bogus.> (XEN) ---- print_iommu_regs ---- > (XEN) drhd->address = fe71a000 > (XEN) VER = ffffffff > (XEN) CAP = ffffffffffffffff > (XEN) n_fault_reg = 100 > (XEN) fault_recording_offset = 3ff0 > (XEN) ECAP = ffffffffffffffff > (XEN) GCMD = ffffffff > (XEN) GSTS = ffffffff > (XEN) RTADDR = ffffffffffffffff > (XEN) CCMD = ffffffffffffffff > (XEN) FSTS = ffffffff > (XEN) FECTL = ffffffff > (XEN) FEDATA = ffffffff > (XEN) FEADDR = ffffffff > (XEN) FEUADDR = ffffffff > (XEN) I/O virtualisation disabled > (XEN) Total of 8 processors activated.Looks to me that your hardware isn''t working right. So to fix this, please follow this link: "Intel developers also want to know about broken IOMMU/VT-d BIOS implementations, see this email: +http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00841.html, so let them know all the details about your hardware and +software if you have broken BIOS. " _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel