* pv-ops domU not working with MSI interrupts on Nehalem
@ 2010-09-27 15:52 Bruce Edge
2010-09-27 17:24 ` Konrad Rzeszutek Wilk
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
0 siblings, 2 replies; 42+ messages in thread
From: Bruce Edge @ 2010-09-27 15:52 UTC (permalink / raw)
To: xen-devel
One of our developers who is working on a tachyon driver is
complaining that the pvops domU kernel is not working for these MSI
interrupts.
This is using the current head of xen/2.6.32.x on both a single
Nahelam 920 and a dual E5540. This behavior is consistent with Xen
4.0.1, 4.0.2.rc1-pre and 4.1.
Here are his comments:
- the driver has no problem to enable msi interrupt and request the
interrupt through kernel functions pci_enable_msi & request_irq
- the interrupt does happen. But the interrupt service routine of
tachyon driver doesn't detect any interrupt status related to this
interrupt, which inhibits the tachyon chip from coming on-line. And
there are high count of tachyon interrupt in /proc/interrupts
kaan-18-dpm:~# cat /proc/interrupts | grep TACH
124: 760415 0 0 0 0 0
0 0 0 0 0 0
0 0 xen-pirq-pcifront-msi HW_TACHYON
125: 762234 0 0 0 0 0
0 0 0 0 0 0
0 0 xen-pirq-pcifront-msi HW_TACHYON
126: 764180 0 0 0 0 0
0 0 0 0 0 0
0 0 xen-pirq-pcifront-msi HW_TACHYON
127: 764164 0 0 0 0 0
0 0 0 0 0 0
0 0 xen-pirq-pcifront-msi HW_TACHYON
-Bruce
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-27 15:52 pv-ops domU not working with MSI interrupts on Nehalem Bruce Edge
@ 2010-09-27 17:24 ` Konrad Rzeszutek Wilk
2010-09-27 19:16 ` Bruce Edge
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
1 sibling, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-09-27 17:24 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel
On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> One of our developers who is working on a tachyon driver is
> complaining that the pvops domU kernel is not working for these MSI
> interrupts.
> This is using the current head of xen/2.6.32.x on both a single
> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> 4.0.1, 4.0.2.rc1-pre and 4.1.
>
> Here are his comments:
>
> - the driver has no problem to enable msi interrupt and request the
> interrupt through kernel functions pci_enable_msi & request_irq
What shows up in the Xen console when you send the 'q' key? Does it
show that the vector is assigned to the appropiate guest?
> - the interrupt does happen. But the interrupt service routine of
> tachyon driver doesn't detect any interrupt status related to this
> interrupt, which inhibits the tachyon chip from coming on-line. And
> there are high count of tachyon interrupt in /proc/interrupts
Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
in the MMIO BAR?
>
> kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> 124: 760415 0 0 0 0 0
> 0 0 0 0 0 0
> 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 125: 762234 0 0 0 0 0
> 0 0 0 0 0 0
> 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 126: 764180 0 0 0 0 0
> 0 0 0 0 0 0
> 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 127: 764164 0 0 0 0 0
> 0 0 0 0 0 0
> 0 0 xen-pirq-pcifront-msi HW_TACHYON
Can you provide the full dmesg output?
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-27 17:24 ` Konrad Rzeszutek Wilk
@ 2010-09-27 19:16 ` Bruce Edge
2010-09-27 19:54 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-09-27 19:16 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, xen-devel
[-- Attachment #1: Type: text/plain, Size: 20681 bytes --]
On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
>
> On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> > One of our developers who is working on a tachyon driver is
> > complaining that the pvops domU kernel is not working for these MSI
> > interrupts.
> > This is using the current head of xen/2.6.32.x on both a single
> > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> > 4.0.1, 4.0.2.rc1-pre and 4.1.
> >
> > Here are his comments:
> >
> > - the driver has no problem to enable msi interrupt and request the
> > interrupt through kernel functions pci_enable_msi & request_irq
>
> What shows up in the Xen console when you send the 'q' key? Does it
> show that the vector is assigned to the appropiate guest?
The Xen console q key shows that the domU is assigned:
(XEN) Interrupts { 32, 41-42, 47 }
but the domU thinks it has:
124/125/126/127
Is there some mapping that's taking place, or is this plain wrong?
>
> > - the interrupt does happen. But the interrupt service routine of
> > tachyon driver doesn't detect any interrupt status related to this
> > interrupt, which inhibits the tachyon chip from coming on-line. And
> > there are high count of tachyon interrupt in /proc/interrupts
>
> Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
> in the MMIO BAR?
>
The driver would check the appropriate register (tachyon registers) in
the MMIO to determine the source of interrupts.
> >
> > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> > 124: 760415 0 0 0 0 0
> > 0 0 0 0 0 0
> > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > 125: 762234 0 0 0 0 0
> > 0 0 0 0 0 0
> > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > 126: 764180 0 0 0 0 0
> > 0 0 0 0 0 0
> > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > 127: 764164 0 0 0 0 0
> > 0 0 0 0 0 0
> > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>
> Can you provide the full dmesg output?
Attached.
Some possibly related messages on dom0 console:
[ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
[ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
[ 1882.269834] xen: --> irq=32
[ 1882.269841] Already setup the GSI :32
[ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
[ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
read-only configuration space field at offset 0x62, size 2. This may
be harmless, but if you have problems with your device:
[ 1882.270465] 1) see permissive attribute in sysfs
[ 1882.270467] 2) report problems to the xen-devel mailing list along
with details of your device obtained from lspci.
[ 1882.270615] alloc irq_desc for 478 on node 0
[ 1882.270625] alloc kstat_irqs on node 0
[ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
[ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
[ 1882.348445] xen: --> irq=42
[ 1882.348472] Already setup the GSI :42
[ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
[ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
read-only configuration space field at offset 0x62, size 2. This may
be harmless, but if you have problems with your device:
[ 1882.349066] 1) see permissive attribute in sysfs
[ 1882.349067] 2) report problems to the xen-devel mailing list along
with details of your device obtained from lspci.
[ 1882.349205] alloc irq_desc for 477 on node 0
[ 1882.349215] alloc kstat_irqs on node 0
[ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
[ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
[ 1882.402916] xen: --> irq=47
[ 1882.402921] Already setup the GSI :47
[ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
[ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
read-only configuration space field at offset 0x62, size 2. This may
be harmless, but if you have problems with your device:
[ 1882.403282] 1) see permissive attribute in sysfs
[ 1882.403282] 2) report problems to the xen-devel mailing list along
with details of your device obtained from lspci.
[ 1882.403380] alloc irq_desc for 476 on node 0
[ 1882.403386] alloc kstat_irqs on node 0
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr e6f80000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 3
(XEN) l3[3] = 702b6003
(XEN) l2 = ffff8300702b6000
(XEN) l2_index = 137
(XEN) l2[137] = 0
(XEN) l2[137] not present
(XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
(XEN) l2[6] not present
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc00
-Bruce
[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 74930 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32.21-xenoprof-1 (root@kaan) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #1 SMP Wed Sep 22 16:02:23 PDT 2010
[ 0.000000] Command line: dummy=dummy root=/dev/mapper/system-dom0_0 ro earlyprintk=xen loglevel=10 debug acpi=force console=hvc0,115200n8
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] released 0 pages of unused memory
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 000000000009f400 (usable)
[ 0.000000] Xen: 000000000009f400 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000020000000 (usable)
[ 0.000000] Xen: 00000000df62f000 - 00000000df63c000 (ACPI data)
[ 0.000000] Xen: 00000000df63d000 - 00000000e4000000 (reserved)
[ 0.000000] Xen: 00000000fec00000 - 00000000fee10000 (reserved)
[ 0.000000] Xen: 00000000ff800000 - 0000000100000000 (reserved)
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] DMI 2.6 present.
[ 0.000000] last_pfn = 0x20000 max_arch_pfn = 0x400000000
[ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] init_memory_mapping: 0000000000000000-0000000020000000
[ 0.000000] 0000000000 - 0020000000 page 4k
[ 0.000000] kernel direct mapping tables up to 20000000 @ 100000-202000
[ 0.000000] RAMDISK: 02861000 - 0c05ac00
[ 0.000000] ACPI: RSDP 00000000000f4f00 00024 (v02 HP )
[ 0.000000] ACPI: XSDT 00000000df630040 000BC (v01 HP ProLiant 00000002 Ò? 0000162E)
[ 0.000000] ACPI: FACP 00000000df630140 000F4 (v03 HP ProLiant 00000002 Ò? 0000162E)
[ 0.000000] ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20090903/tbfadt-607)
[ 0.000000] ACPI Warning: Invalid length for Pm2ControlBlock: 32, using default 8 (20090903/tbfadt-607)
[ 0.000000] ACPI: DSDT 00000000df630240 02005 (v01 HP DSDT 00000001 INTL 20030228)
[ 0.000000] ACPI: FACS 00000000df62f100 00040
[ 0.000000] ACPI: SPCR 00000000df62f140 00050 (v01 HP SPCRRBSU 00000001 Ò? 0000162E)
[ 0.000000] ACPI: MCFG 00000000df62f1c0 0003C (v01 HP ProLiant 00000001 00000000)
[ 0.000000] ACPI: HPET 00000000df62f200 00038 (v01 HP ProLiant 00000002 Ò? 0000162E)
[ 0.000000] ACPI: FFFF 00000000df62f240 00064 (v02 HP ProLiant 00000002 Ò? 0000162E)
[ 0.000000] ACPI: SPMI 00000000df62f2c0 00040 (v05 HP ProLiant 00000001 Ò? 0000162E)
[ 0.000000] ACPI: ERST 00000000df62f300 001D0 (v01 HP ProLiant 00000001 Ò? 0000162E)
[ 0.000000] ACPI: APIC 00000000df62f500 0015E (v01 HP ProLiant 00000002 00000000)
[ 0.000000] ACPI: SRAT 00000000df62f680 00570 (v01 HP Proliant 00000001 Ò? 0000162E)
[ 0.000000] ACPI: FFFF 00000000df62fc00 00176 (v01 HP ProLiant 00000001 Ò? 0000162E)
[ 0.000000] ACPI: BERT 00000000df62fd80 00030 (v01 HP ProLiant 00000001 Ò? 0000162E)
[ 0.000000] ACPI: HEST 00000000df62fdc0 000BC (v01 HP ProLiant 00000001 Ò? 0000162E)
[ 0.000000] ACPI: XMAR 00000000df62fe80 00154 (v01 HP ProLiant 00000001 Ò? 0000162E)
[ 0.000000] ACPI: SSDT 00000000df632280 00125 (v03 HP CRSPCI0 00000002 HP 00000001)
[ 0.000000] ACPI: SSDT 00000000df6323c0 00255 (v03 HP riser1a 00000002 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000df632640 0025D (v03 HP riser2a 00000002 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000df6328c0 003BB (v01 HP pcc 00000001 INTL 20090625)
[ 0.000000] ACPI: SSDT 00000000df632c80 00377 (v01 HP pmab 00000001 INTL 20090625)
[ 0.000000] ACPI: SSDT 00000000df633000 022E4 (v01 INTEL PPM RCM 00000001 INTL 20061109)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] SRAT: PXM 0 -> APIC 0 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 1 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 2 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 3 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 4 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 5 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 6 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 7 -> Node 0
[ 0.000000] SRAT: PXM 1 -> APIC 16 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 17 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 18 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 19 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 20 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 21 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 22 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 23 -> Node 1
[ 0.000000] SRAT: Node 0 PXM 0 0-e0000000
[ 0.000000] SRAT: Node 0 PXM 0 100000000-1a0000000
[ 0.000000] SRAT: Node 1 PXM 1 1a0000000-320000000
[ 0.000000] NUMA: Using 29 for the hash shift.
[ 0.000000] Bootmem setup node 0 0000000000000000-0000000020000000
[ 0.000000] NODE_DATA [0000000000001000 - 0000000000004fff]
[ 0.000000] bootmap [0000000000008000 - 000000000000bfff] pages 4
[ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 0020000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [000c15c000 - 000c1c1000] XEN PAGETABLES ==> [000c15c000 - 000c1c1000]
[ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
[ 0.000000] #3 [0001000000 - 0002737520] TEXT DATA BSS ==> [0001000000 - 0002737520]
[ 0.000000] #4 [0002861000 - 000c05ac00] RAMDISK ==> [0002861000 - 000c05ac00]
[ 0.000000] #5 [000c05b000 - 000c15c000] XEN START INFO ==> [000c05b000 - 000c15c000]
[ 0.000000] #6 [0002738000 - 0002742180] BRK ==> [0002738000 - 0002742180]
[ 0.000000] #7 [0000100000 - 000019a000] PGTABLE ==> [0000100000 - 000019a000]
[ 0.000000] found SMP MP-table at [ffff8800000f4f80] f4f80
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00100000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x00020000
[ 0.000000] On node 0 totalpages: 130975
[ 0.000000] DMA zone: 104 pages used for memmap
[ 0.000000] DMA zone: 157 pages reserved
[ 0.000000] DMA zone: 3738 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 3224 pages used for memmap
[ 0.000000] DMA32 zone: 123752 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x908
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x24] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x14] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x34] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x22] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x12] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x32] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x26] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x16] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x36] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x11] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x31] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x25] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x15] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x35] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x23] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x13] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x33] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x27] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x17] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x37] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-0
[ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec80000] gsi_base[24])
[ 0.000000] IOAPIC[1]: apic_id 0, version 0, address 0xfec80000, GSI 24-24
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 280
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 20000000 (gap: 20000000:bf62f000)
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.0.2-rc1-pre (preserve-AD) (dom0)
[ 0.000000] NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:1 nr_node_ids:2
[ 0.000000] PERCPU: Embedded 478 pages/cpu @ffff88000c267000 s1927064 r8192 d22632 u1957888
[ 0.000000] pcpu-alloc: s1927064 r8192 d22632 u1957888 alloc=478*4096
[ 0.000000] pcpu-alloc: [0] 0
[ 4.168278] trying to map vcpu_info 0 at ffff88000c272020, mfn 18c272, offset 32
[ 4.168284] cpu 0 using vcpu_info at ffff88000c272020
[ 4.168286] Xen: using vcpu_info placement
[ 4.168292] Built 1 zonelists in Node order, mobility grouping on. Total pages: 127490
[ 4.168295] Policy zone: DMA32
[ 4.168306] Kernel command line: dummy=dummy root=/dev/mapper/system-dom0_0 ro earlyprintk=xen loglevel=10 debug acpi=force console=hvc0,115200n8
[ 4.168358] PID hash table entries: 2048 (order: 2, 16384 bytes)
[ 4.168725] Initializing CPU#0
[ 4.178099] DMA: Placing 64MB software IO TLB between ffff88000d1ad000 - ffff8800111ad000
[ 4.178108] DMA: software IO TLB at phys 0xd1ad000 - 0x111ad000
[ 4.178111] xen_swiotlb_fixup: buf=ffff88000d1ad000 size=67108864
[ 4.198055] xen_swiotlb_fixup: buf=ffff88001120d000 size=32768
[ 4.252465] Memory: 260456k/524288k available (6123k kernel code, 388k absent, 263444k reserved, 3749k data, 2620k init)
[ 4.252527] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=2
[ 4.252634] Hierarchical RCU implementation.
[ 4.252668] NR_IRQS:4352 nr_irqs:512
[ 4.252781] xen: --> irq=0
[ 4.252790] xen: --> irq=1
[ 4.252796] xen: --> irq=2
[ 4.252802] xen: --> irq=3
[ 4.252809] xen: --> irq=4
[ 4.252815] xen: --> irq=5
[ 4.252821] xen: --> irq=6
[ 4.252827] xen: --> irq=7
[ 4.252833] xen: --> irq=8
[ 4.252840] xen: --> irq=9
[ 4.252846] xen: --> irq=10
[ 4.252852] xen: --> irq=11
[ 4.252858] xen: --> irq=12
[ 4.252865] xen: --> irq=13
[ 4.252871] xen: --> irq=14
[ 4.252877] xen: --> irq=15
[ 4.252892] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[ 4.252895] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 4.252899] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1
[ 4.252902] xen: registering gsi 9 triggering 0 polarity 0
[ 4.252906] xen_allocate_pirq: returning irq 9 for gsi 9
[ 4.252909] xen: --> irq=9
[ 4.252916] xen: acpi sci 9
[ 4.256365] Console: colour VGA+ 80x25
[ 4.256384] console [hvc0] enabled, bootconsole disabled
[ 4.256401] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[ 4.256405] ... MAX_LOCKDEP_SUBCLASSES: 8
[ 4.256408] ... MAX_LOCK_DEPTH: 48
[ 4.256411] ... MAX_LOCKDEP_KEYS: 8191
[ 4.256415] ... CLASSHASH_SIZE: 4096
[ 4.256418] ... MAX_LOCKDEP_ENTRIES: 16384
[ 4.256421] ... MAX_LOCKDEP_CHAINS: 32768
[ 4.256424] ... CHAINHASH_SIZE: 16384
[ 4.256428] memory used by lock dependency info: 6367 kB
[ 4.256431] per task-struct memory footprint: 2688 bytes
[ 4.257347] allocated 5242880 bytes of page_cgroup
[ 4.257352] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 4.257848] ODEBUG: 9 of 9 active objects replaced
[ 4.257929] Xen: using vcpuop timer interface
[ 4.257934] installing Xen timer for CPU 0
[ 4.257975] alloc irq_desc for 511 on node 0
[ 4.257981] alloc kstat_irqs on node 0
[ 4.258030] Detected 2533.496 MHz processor.
[ 4.258059] Calibrating delay loop (skipped), value calculated using timer frequency.. 5066.99 BogoMIPS (lpj=25334960)
[ 4.258140] Security Framework initialized
[ 4.258150] SELinux: Disabled at boot.
[ 4.258346] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 4.258492] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 4.258552] Mount-cache hash table entries: 256
[ 4.259653] Initializing cgroup subsys ns
[ 4.259659] Initializing cgroup subsys cpuacct
[ 4.259673] Initializing cgroup subsys memory
[ 4.259769] Initializing cgroup subsys devices
[ 4.259775] Initializing cgroup subsys freezer
[ 4.259779] Initializing cgroup subsys net_cls
[ 4.259885] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 4.259890] CPU: L2 cache: 256K
[ 4.259893] CPU: L3 cache: 8192K
[ 4.259898] CPU 0/0x0 -> Node 0
[ 4.259902] CPU: Unsupported number of siblings 16
[ 4.259907] mce: CPU supports 9 MCE banks
[ 4.259936] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only.
[ 4.259951] SMP alternatives: switching to UP code
[ 4.292632] Freeing SMP alternatives: 39k freed
[ 4.292655] ACPI: Core revision 20090903
[ 4.317850] ftrace: converting mcount calls to 0f 1f 44 00 00
[ 4.317858] ftrace: allocating 24198 entries in 95 pages
[ 4.324178] alloc irq_desc for 510 on node 0
[ 4.324185] alloc kstat_irqs on node 0
[ 4.324202] alloc irq_desc for 509 on node 0
[ 4.324208] alloc kstat_irqs on node 0
[ 4.324222] alloc irq_desc for 508 on node 0
[ 4.324228] alloc kstat_irqs on node 0
[ 4.324255] alloc irq_desc for 507 on node 0
[ 4.324261] alloc kstat_irqs on node 0
[ 4.324779] Brought up 1 CPUs
[ 4.324837] CPU0 attaching NULL sched-domain.
[ 4.325428] devtmpfs: initialized
[ 4.327692] Grant table initialized
[ 4.327698] regulator: core version 0.5
[ 4.327756] Time: 17:59:31 Date: 09/27/10
[ 4.328026] NET: Registered protocol family 16
[ 4.328418] alloc irq_desc for 506 on node 0
[ 4.328425] alloc kstat_irqs on node 0
[ 4.329652] ACPI: bus type pci registered
[ 4.329934] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 63
[ 4.329940] PCI: MCFG area at e0000000 reserved in E820
[ 4.339401] PCI: Using MMCONFIG at e0000000 - e3ffffff
[ 4.339406] PCI: Using configuration type 1 for base access
[ 4.339412] PCI: HP ProLiant DL380 detected, enabling pci=bfsort.
[ 4.347966] bio: create slab <bio-0> at 0
[ 4.353020] ERROR: Unable to locate IOAPIC for GSI 9
[ 4.353093] ACPI: EC: Look up EC in DSDT
[ 4.357690] ACPI Error: Field [CDW3] at 96 exceeds Buffer [NULL] size 64 (bits) (20090903/dsopcode-596)
[ 4.357711] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_._OSC] (Node ffff88001fd171a0), AE_AML_BUFFER_LIMIT
[ 4.370868] ACPI: Interpreter enabled
[ 4.370873] ACPI: (supports S0 S4 S5)
[ 4.370989] ACPI: Using IOAPIC for interrupt routing
[ 4.403670] ACPI: No dock devices found.
[ 4.403754] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 4.404169] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 4.404180] pci 0000:00:00.0: PME# disabled
[ 4.404423] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 4.404433] pci 0000:00:01.0: PME# disabled
[ 4.404668] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
[ 4.404678] pci 0000:00:02.0: PME# disabled
[ 4.404918] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 4.404928] pci 0000:00:03.0: PME# disabled
[ 4.405163] pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
[ 4.405172] pci 0000:00:04.0: PME# disabled
[ 4.405426] pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
[ 4.405436] pci 0000:00:05.0: PME# disabled
[ 4.405689] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
[ 4.405700] pci 0000:00:06.0: PME# disabled
[ 4.405933] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[ 4.405943] pci 0000:00:07.0: PME# disabled
[ 4.406185] pci 0000:00:08.0: PME# supported from D0 D3hot D3cold
[ 4.406196] pci 0000:00:08.0: PME# disabled
[ 4.406429] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
[ 4.406439] pci 0000:00:09.0: PME# disabled
[ 4.406690] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
[ 4.406701] pci 0000:00:0a.0: PME# disabled
[ 4.409722] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 4.409733] pci 0000:00:1c.0: PME# disabled
[ 4.409940] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 4.409951] pci 0000:00:1c.2: PME# disabled
[ 4.410152] pci 0000:00:1d.0: reg 20 io port: [0x1000-0x101f]
[ 4.410400] pci 0000:00:1d.1: reg 20 io port: [0x1020-0x103f]
[ 4.410666] pci 0000:00:1d.2: reg 20 io port: [0x1040-0x105f]
[ 4.410913] pci 0000:00:1d.3: reg 20 io port: [0x1060-0x107f]
[ 4.411144] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf1df0000-0xf1df03ff]
[ 4.411298] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 4.411309] pci 0000:00:1d.7: PME# disabled
[ 4.411876] pci 0000:04:00.0: reg 10 64bit mmio: [0xfb400000-0xfb7fffff]
[ 4.411904] pci 0000:04:00.0: reg 18 64bit mmio: [0xfb3f0000-0xfb3f0fff]
[ 4.411921] pci 0000:04:00.0: reg 20 io port: [0x4000-0x40ff]
[ 4.411949] pci 0000:04:00.0: reg 30 32bit mmio pref: [0x000000-0x07ffff]
[ 4.412023] pci 0000:04:00.0: supports D1
[ 4.412027] pci 0000:04:00.0: PME# supported from D0
[ 4.412036] pci 0000:04:00.0: PME# disabled
[ 4.427758] pci 0000:00:01.0: bridge io port: [0x4000-0x4fff]
[ 4.427769] pci 0000:00:01.0: bridge 32bit mmio: [0xfb300000-0xfb7fffff]
[ 4.428637] pci 0000:0d:00.0: reg 10 io port: [0x7000-0x70ff]
[ 4.428666] pci 0000:0d:00.0: reg 14 64bit mmio: [0xfbff0000-0xfbff3fff]
[ 4.428694] pci 0000:0d:00.0: reg 1c 64bit mmio: [0xfbe00000-0xfbefffff]
[ 4.428722] pci 0000:0d:00.0: reg 30 32bit mmio pref: [0x000000-0x03ffff]
[ 4.428907] pci 0000:0d:00.1: reg 10 io port: [0x7400-0x74ff]
[ 4.428935] pci 0000:0d:00.1: reg 14 64bit mmio: [0xfbdf0000-0xfbdf3fff]
[ 4.428963] pci 0000:0d:00.1: reg 1c 64bit mmio: [0xfbc00000-0xfbcfffff]
[ 4.428991] pci 0000:0d:00.1: reg 30 32bit mmio pref: [0x000000-0x03ffff]
[ 4.447719] pci 0000:00:07.0: bridge io port: [0x7000-0x7fff]
[ 4.447729] pci 0000:00:07.0: bridge 32bit mmio: [0xfbc00000-0xfbffffff]
[ 4.448042] pci 0000:07:00.0: reg 18 io port: [0x5000-0x50ff]
[ 4.448058] pci 0000:07:00.0: reg 1c io port: [0x5400-0x54ff]
[ 4.448086] pci 0000:07:00.0: reg 20 64bit mmio: [0xfbbf0000-0xfbbf7fff]
[ 4.448311] pci 0000:07:00.1: reg 18 io port: [0x5800-0x58ff]
[ 4.448328] pci 0000:07:00.1: reg 1c io port: [0x5c00-0x5cff]
[ 4.448356] pci 0000:07:00.1: reg 20 64bit mmio: [0xfbbe0000-0xfbbe7fff]
[ 4.448580] pci 0000:07:00.2: reg 18 io port: [0x6000-0x60ff]
[ 4.448596] pci 0000:07:00.2: reg 1c io port: [0x6400-0x64ff]
[ 4.448624] pci 0000:07:00.2: reg 20 64bit mmio: [0xfbbd0000-0xfbbd7fff]
[ 4.448868] pci 0000:07:00.3: reg 18 io port: [0x6800-0x68ff]
[ 4.448885] pci 0000:07:00.3: reg 1c io port: [0x6c00-0x6cff]
[ 4.448913] pci 0000:07:00.3: reg 20 64bit mmio: [0xfbbc0000-0xfbbc7fff]
[ 4.467804] pci 0000:00:09.0: bridge io port: [0x5000-0x6fff]
[ 4.467815] pci 0000:00:09.0: bridge 32bit mmio: [0xfbb00000-0xfbbfffff]
[ 4.468132] pci 0000:02:00.0: reg 10 64bit mmio: [0xf4000000-0xf5ffffff]
[ 4.468228] pci 0000:02:00.0: reg 30 32bit mmio pref: [0x000000-0x00ffff]
[ 4.468336] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
[ 4.468347] pci 0000:02:00.0: PME# disabled
[ 4.468533] pci 0000:02:00.1: reg 10 64bit mmio: [0xf2000000-0xf3ffffff]
[ 4.468607] pci 0000:02:00.1: reg 30 32bit mmio pref: [0x000000-0x00ffff]
[ 4.468715] pci 0000:02:00.1: PME# supported from D0 D3hot D3cold
[ 4.468727] pci 0000:02:00.1: PME# disabled
[ 4.469361] pci 0000:00:1c.0: bridge 32bit mmio: [0xf2000000-0xf5ffffff]
[ 4.469534] pci 0000:03:00.0: reg 10 64bit mmio: [0xf8000000-0xf9ffffff]
[ 4.469608] pci 0000:03:00.0: reg 30 32bit mmio pref: [0x000000-0x00ffff]
[ 4.469716] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 4.469727] pci 0000:03:00.0: PME# disabled
[ 4.469922] pci 0000:03:00.1: reg 10 64bit mmio: [0xf6000000-0xf7ffffff]
[ 4.469997] pci 0000:03:00.1: reg 30 32bit mmio pref: [0x000000-0x00ffff]
[ 4.470105] pci 0000:03:00.1: PME# supported from D0 D3hot D3cold
[ 4.470116] pci 0000:03:00.1: PME# disabled
[ 4.470750] pci 0000:00:1c.2: bridge 32bit mmio: [0xf6000000-0xf9ffffff]
[ 4.470878] pci 0000:01:03.0: reg 10 32bit mmio pref: [0xe8000000-0xefffffff]
[ 4.470896] pci 0000:01:03.0: reg 14 io port: [0x3000-0x30ff]
[ 4.470914] pci 0000:01:03.0: reg 18 32bit mmio: [0xf1ff0000-0xf1ffffff]
[ 4.470972] pci 0000:01:03.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
[ 4.471025] pci 0000:01:03.0: supports D1 D2
[ 4.471137] pci 0000:01:04.0: reg 10 io port: [0x2800-0x28ff]
[ 4.471155] pci 0000:01:04.0: reg 14 32bit mmio: [0xf1fe0000-0xf1fe01ff]
[ 4.471274] pci 0000:01:04.0: PME# supported from D0 D3hot D3cold
[ 4.471285] pci 0000:01:04.0: PME# disabled
[ 4.471390] pci 0000:01:04.2: reg 10 io port: [0x3400-0x34ff]
[ 4.471408] pci 0000:01:04.2: reg 14 32bit mmio: [0xf1fd0000-0xf1fd07ff]
[ 4.471427] pci 0000:01:04.2: reg 18 32bit mmio: [0xf1fc0000-0xf1fc3fff]
[ 4.471445] pci 0000:01:04.2: reg 1c 32bit mmio: [0xf1f00000-0xf1f7ffff]
[ 4.471492] pci 0000:01:04.2: reg 30 32bit mmio pref: [0x000000-0x00ffff]
[ 4.471547] pci 0000:01:04.2: PME# supported from D0 D3hot D3cold
[ 4.471558] pci 0000:01:04.2: PME# disabled
[ 4.471749] pci 0000:01:04.4: reg 20 io port: [0x3800-0x381f]
[ 4.471832] pci 0000:01:04.4: PME# supported from D0 D3hot D3cold
[ 4.471843] pci 0000:01:04.4: PME# disabled
[ 4.471954] pci 0000:01:04.6: reg 10 32bit mmio: [0xf1ef0000-0xf1ef00ff]
[ 4.472087] pci 0000:01:04.6: PME# supported from D0 D3hot D3cold
[ 4.472098] pci 0000:01:04.6: PME# disabled
[ 4.472241] pci 0000:00:1e.0: transparent bridge
[ 4.472251] pci 0000:00:1e.0: bridge io port: [0x2000-0x3fff]
[ 4.472261] pci 0000:00:1e.0: bridge 32bit mmio: [0xf1e00000-0xf1ffffff]
[ 4.472278] pci 0000:00:1e.0: bridge 64bit mmio pref: [0xe8000000-0xefffffff]
[ 4.472445] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 4.473952] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IP2P._PRT]
[ 4.474375] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IPT1._PRT]
[ 4.474670] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IPT3._PRT]
[ 4.474964] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT01._PRT]
[ 4.475213] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT03._PRT]
[ 4.475998] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT04._PRT]
[ 4.476448] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT05._PRT]
[ 4.477247] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT06._PRT]
[ 4.477978] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT07._PRT]
[ 4.478730] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT08._PRT]
[ 4.479601] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT09._PRT]
[ 4.480425] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT0A._PRT]
[ 4.540342] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 7 10 *11)
[ 4.540653] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7 *10 11)
[ 4.540947] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 *7 10 11)
[ 4.541236] ACPI: PCI Interrupt Link [LNKD] (IRQs *5 7 10 11)
[ 4.541533] ACPI: PCI Interrupt Link [LNKE] (IRQs 5 7 10 11) *3
[ 4.541836] ACPI: PCI Interrupt Link [LNKF] (IRQs 5 7 10 *11)
[ 4.542140] ACPI: PCI Interrupt Link [LNKG] (IRQs 5 *7 10 11)
[ 4.542422] ACPI: PCI Interrupt Link [LNKH] (IRQs *5 7 10 11)
[ 4.542779] sync cpu 0 get result 1 max_id f
[ 4.542840] sync cpu 1 get result 1 max_id f
[ 4.542887] sync cpu 2 get result 1 max_id f
[ 4.542933] sync cpu 3 get result 1 max_id f
[ 4.543001] sync cpu 4 get result 1 max_id f
[ 4.543047] sync cpu 5 get result 1 max_id f
[ 4.543093] sync cpu 6 get result 1 max_id f
[ 4.543144] sync cpu 7 get result 1 max_id f
[ 4.543211] sync cpu 8 get result 1 max_id f
[ 4.543257] sync cpu 9 get result 1 max_id f
[ 4.543303] sync cpu a get result 1 max_id f
[ 4.543349] sync cpu b get result 1 max_id f
[ 4.543395] sync cpu c get result 1 max_id f
[ 4.543442] sync cpu d get result 1 max_id f
[ 4.543493] sync cpu e get result 1 max_id f
[ 4.543540] sync cpu f get result 1 max_id f
[ 4.543548] alloc irq_desc for 505 on node 0
[ 4.543554] alloc kstat_irqs on node 0
[ 4.543737] xen_balloon: Initialising balloon driver with page order 0.
[ 4.544453] vgaarb: device added: PCI:0000:01:03.0,decodes=io+mem,owns=io+mem,locks=none
[ 4.544482] vgaarb: loaded
[ 4.544912] SCSI subsystem initialized
[ 4.545097] libata version 3.00 loaded.
[ 4.545481] usbcore: registered new interface driver usbfs
[ 4.545560] usbcore: registered new interface driver hub
[ 4.545691] usbcore: registered new device driver usb
[ 4.546042] PCI: Using ACPI for IRQ routing
[ 4.549491] PCI: Discovered peer bus 3e
[ 4.554952] PCI: Discovered peer bus 3f
[ 4.576198] NetLabel: Initializing
[ 4.576202] NetLabel: domain hash size = 128
[ 4.576206] NetLabel: protocols = UNLABELED CIPSOv4
[ 4.576350] NetLabel: unlabeled traffic allowed by default
[ 4.577294] Switching to clocksource xen
[ 4.577638] kstop/0 used greatest stack depth: 6504 bytes left
[ 4.634928] pnp: PnP ACPI init
[ 4.634984] ACPI: bus type pnp registered
[ 4.639449] xen: registering gsi 1 triggering 1 polarity 0
[ 4.639455] xen_allocate_pirq: returning irq 1 for gsi 1
[ 4.639459] xen: --> irq=1
[ 4.639852] xen: registering gsi 12 triggering 1 polarity 0
[ 4.639858] xen_allocate_pirq: returning irq 12 for gsi 12
[ 4.639861] xen: --> irq=12
[ 4.642670] pnp: PnP ACPI: found 10 devices
[ 4.642675] ACPI: ACPI bus type pnp unregistered
[ 4.642713] system 00:01: ioport range 0x408-0x40f has been reserved
[ 4.642720] system 00:01: ioport range 0x4d0-0x4d1 has been reserved
[ 4.642726] system 00:01: ioport range 0x700-0x71f has been reserved
[ 4.642732] system 00:01: ioport range 0x880-0x8ff has been reserved
[ 4.642739] system 00:01: ioport range 0x900-0x97f has been reserved
[ 4.642745] system 00:01: ioport range 0xc80-0xc83 has been reserved
[ 4.642751] system 00:01: ioport range 0xcd4-0xcd7 has been reserved
[ 4.642757] system 00:01: ioport range 0xf50-0xf58 has been reserved
[ 4.642764] system 00:01: ioport range 0xca0-0xca1 has been reserved
[ 4.642770] system 00:01: ioport range 0xca4-0xca5 has been reserved
[ 4.642781] system 00:01: ioport range 0x3f8-0x3ff has been reserved
[ 4.642788] system 00:01: iomem range 0xe0000000-0xe3ffffff has been reserved
[ 4.642795] system 00:01: iomem range 0xfe000000-0xfebfffff has been reserved
[ 4.642801] system 00:01: iomem range 0xe7ffe000-0xe7ffffff has been reserved
[ 4.647754] PM-Timer failed consistency check (0x0xffffff) - aborting.
[ 4.648476] pci 0000:00:01.0: PCI bridge, secondary bus 0000:04
[ 4.648484] pci 0000:00:01.0: IO window: 0x4000-0x4fff
[ 4.648497] pci 0000:00:01.0: MEM window: 0xfb300000-0xfb7fffff
[ 4.648507] pci 0000:00:01.0: PREFETCH window: 0x20000000-0x200fffff
[ 4.648523] pci 0000:00:02.0: PCI bridge, secondary bus 0000:05
[ 4.648526] pci 0000:00:02.0: IO window: disabled
[ 4.648538] pci 0000:00:02.0: MEM window: disabled
[ 4.648549] pci 0000:00:02.0: PREFETCH window: disabled
[ 4.648564] pci 0000:00:03.0: PCI bridge, secondary bus 0000:10
[ 4.648568] pci 0000:00:03.0: IO window: disabled
[ 4.648580] pci 0000:00:03.0: MEM window: disabled
[ 4.648589] pci 0000:00:03.0: PREFETCH window: disabled
[ 4.648604] pci 0000:00:04.0: PCI bridge, secondary bus 0000:13
[ 4.648608] pci 0000:00:04.0: IO window: disabled
[ 4.648638] pci 0000:00:04.0: MEM window: disabled
[ 4.648647] pci 0000:00:04.0: PREFETCH window: disabled
[ 4.648663] pci 0000:00:05.0: PCI bridge, secondary bus 0000:14
[ 4.648667] pci 0000:00:05.0: IO window: disabled
[ 4.648678] pci 0000:00:05.0: MEM window: disabled
[ 4.648688] pci 0000:00:05.0: PREFETCH window: disabled
[ 4.648703] pci 0000:00:06.0: PCI bridge, secondary bus 0000:17
[ 4.648707] pci 0000:00:06.0: IO window: disabled
[ 4.648718] pci 0000:00:06.0: MEM window: disabled
[ 4.648728] pci 0000:00:06.0: PREFETCH window: disabled
[ 4.648749] pci 0000:00:07.0: PCI bridge, secondary bus 0000:0d
[ 4.648757] pci 0000:00:07.0: IO window: 0x7000-0x7fff
[ 4.648769] pci 0000:00:07.0: MEM window: 0xfbc00000-0xfbffffff
[ 4.648779] pci 0000:00:07.0: PREFETCH window: 0x20100000-0x201fffff
[ 4.648795] pci 0000:00:08.0: PCI bridge, secondary bus 0000:0a
[ 4.648799] pci 0000:00:08.0: IO window: disabled
[ 4.648810] pci 0000:00:08.0: MEM window: disabled
[ 4.648820] pci 0000:00:08.0: PREFETCH window: disabled
[ 4.648835] pci 0000:00:09.0: PCI bridge, secondary bus 0000:07
[ 4.648842] pci 0000:00:09.0: IO window: 0x5000-0x6fff
[ 4.648855] pci 0000:00:09.0: MEM window: 0xfbb00000-0xfbbfffff
[ 4.648864] pci 0000:00:09.0: PREFETCH window: disabled
[ 4.648880] pci 0000:00:0a.0: PCI bridge, secondary bus 0000:06
[ 4.648883] pci 0000:00:0a.0: IO window: disabled
[ 4.648895] pci 0000:00:0a.0: MEM window: disabled
[ 4.648905] pci 0000:00:0a.0: PREFETCH window: disabled
[ 4.648926] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
[ 4.648930] pci 0000:00:1c.0: IO window: disabled
[ 4.648943] pci 0000:00:1c.0: MEM window: 0xf2000000-0xf5ffffff
[ 4.648953] pci 0000:00:1c.0: PREFETCH window: 0x20200000-0x202fffff
[ 4.648976] pci 0000:00:1c.2: PCI bridge, secondary bus 0000:03
[ 4.648979] pci 0000:00:1c.2: IO window: disabled
[ 4.648992] pci 0000:00:1c.2: MEM window: 0xf6000000-0xf9ffffff
[ 4.649003] pci 0000:00:1c.2: PREFETCH window: 0x20300000-0x203fffff
[ 4.649027] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:01
[ 4.649035] pci 0000:00:1e.0: IO window: 0x2000-0x3fff
[ 4.649047] pci 0000:00:1e.0: MEM window: 0xf1e00000-0xf1ffffff
[ 4.649058] pci 0000:00:1e.0: PREFETCH window: 0x000000e8000000-0x000000efffffff
[ 4.649098] pci 0000:00:01.0: setting latency timer to 64
[ 4.649126] pci 0000:00:02.0: setting latency timer to 64
[ 4.649153] pci 0000:00:03.0: setting latency timer to 64
[ 4.649180] pci 0000:00:04.0: setting latency timer to 64
[ 4.649207] pci 0000:00:05.0: setting latency timer to 64
[ 4.649234] pci 0000:00:06.0: setting latency timer to 64
[ 4.649262] pci 0000:00:07.0: setting latency timer to 64
[ 4.649289] pci 0000:00:08.0: setting latency timer to 64
[ 4.649316] pci 0000:00:09.0: setting latency timer to 64
[ 4.649343] pci 0000:00:0a.0: setting latency timer to 64
[ 4.649368] xen: registering gsi 16 triggering 0 polarity 1
[ 4.649378] alloc irq_desc for 16 on node 0
[ 4.649384] alloc kstat_irqs on node 0
[ 4.649393] xen: --> irq=16
[ 4.649399] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 4.649410] pci 0000:00:1c.0: setting latency timer to 64
[ 4.649434] xen: registering gsi 16 triggering 0 polarity 1
[ 4.649438] xen_allocate_pirq: returning irq 16 for gsi 16
[ 4.649442] xen: --> irq=16
[ 4.649444] Already setup the GSI :16
[ 4.649448] pci 0000:00:1c.2: PCI INT C -> GSI 16 (level, low) -> IRQ 16
[ 4.649458] pci 0000:00:1c.2: setting latency timer to 64
[ 4.649498] pci 0000:00:1e.0: setting latency timer to 64
[ 4.649508] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 4.649512] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
[ 4.649516] pci_bus 0000:04: resource 0 io: [0x4000-0x4fff]
[ 4.649521] pci_bus 0000:04: resource 1 mem: [0xfb300000-0xfb7fffff]
[ 4.649525] pci_bus 0000:04: resource 2 pref mem [0x20000000-0x200fffff]
[ 4.649530] pci_bus 0000:0d: resource 0 io: [0x7000-0x7fff]
[ 4.649534] pci_bus 0000:0d: resource 1 mem: [0xfbc00000-0xfbffffff]
[ 4.649538] pci_bus 0000:0d: resource 2 pref mem [0x20100000-0x201fffff]
[ 4.649543] pci_bus 0000:07: resource 0 io: [0x5000-0x6fff]
[ 4.649547] pci_bus 0000:07: resource 1 mem: [0xfbb00000-0xfbbfffff]
[ 4.649552] pci_bus 0000:02: resource 1 mem: [0xf2000000-0xf5ffffff]
[ 4.649556] pci_bus 0000:02: resource 2 pref mem [0x20200000-0x202fffff]
[ 4.649561] pci_bus 0000:03: resource 1 mem: [0xf6000000-0xf9ffffff]
[ 4.649565] pci_bus 0000:03: resource 2 pref mem [0x20300000-0x203fffff]
[ 4.649569] pci_bus 0000:01: resource 0 io: [0x2000-0x3fff]
[ 4.649573] pci_bus 0000:01: resource 1 mem: [0xf1e00000-0xf1ffffff]
[ 4.649577] pci_bus 0000:01: resource 2 pref mem [0xe8000000-0xefffffff]
[ 4.649582] pci_bus 0000:01: resource 3 io: [0x00-0xffff]
[ 4.649586] pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffffffffffff]
[ 4.649590] pci_bus 0000:3e: resource 0 io: [0x00-0xffff]
[ 4.649594] pci_bus 0000:3e: resource 1 mem: [0x000000-0xffffffffffffffff]
[ 4.649599] pci_bus 0000:3f: resource 0 io: [0x00-0xffff]
[ 4.649603] pci_bus 0000:3f: resource 1 mem: [0x000000-0xffffffffffffffff]
[ 4.649738] NET: Registered protocol family 2
[ 4.650155] IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 4.651649] TCP established hash table entries: 16384 (order: 6, 262144 bytes)
[ 4.651998] TCP bind hash table entries: 16384 (order: 8, 1179648 bytes)
[ 4.654132] TCP: Hash tables configured (established 16384 bind 16384)
[ 4.654150] TCP reno registered
[ 4.654458] NET: Registered protocol family 1
[ 4.655034] RPC: Registered udp transport module.
[ 4.655040] RPC: Registered tcp transport module.
[ 4.655044] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 4.667662] pci 0000:01:03.0: Boot video device
[ 4.669048] Trying to unpack rootfs image as initramfs...
[ 4.897339] Freeing initrd memory: 155623k freed
[ 5.003262] DMA-API: preallocated 32768 debug entries
[ 5.003269] DMA-API: debugging enabled by kernel config
[ 5.003275] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 5.003280] DMA: Placing 64MB software IO TLB between ffff88000d1ad000 - ffff8800111ad000
[ 5.003285] DMA: software IO TLB at phys 0xd1ad000 - 0x111ad000
[ 5.005161] audit: initializing netlink socket (disabled)
[ 5.005225] type=2000 audit(1285610371.957:1): initialized
[ 5.014623] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 5.029930] VFS: Disk quotas dquot_6.5.2
[ 5.030249] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 5.034634] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 5.036260] fuse init (API version 7.13)
[ 5.036684] msgmni has been set to 812
[ 5.037695] cryptomgr_test used greatest stack depth: 5896 bytes left
[ 5.037873] cryptomgr_test used greatest stack depth: 5592 bytes left
[ 5.038322] alg: No test for stdrng (krng)
[ 5.038575] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 5.038593] io scheduler noop registered
[ 5.038598] io scheduler anticipatory registered
[ 5.038603] io scheduler deadline registered
[ 5.038943] io scheduler cfq registered (default)
[ 5.040875] alloc irq_desc for 504 on node 0
[ 5.040882] alloc kstat_irqs on node 0
[ 5.040930] pcieport 0000:00:01.0: setting latency timer to 64
[ 5.041391] alloc irq_desc for 503 on node 0
[ 5.041397] alloc kstat_irqs on node 0
[ 5.041435] pcieport 0000:00:02.0: setting latency timer to 64
[ 5.041876] alloc irq_desc for 502 on node 0
[ 5.041900] alloc kstat_irqs on node 0
[ 5.041939] pcieport 0000:00:03.0: setting latency timer to 64
[ 5.042365] alloc irq_desc for 501 on node 0
[ 5.042371] alloc kstat_irqs on node 0
[ 5.042409] pcieport 0000:00:04.0: setting latency timer to 64
[ 5.042844] alloc irq_desc for 500 on node 0
[ 5.042868] alloc kstat_irqs on node 0
[ 5.042906] pcieport 0000:00:05.0: setting latency timer to 64
[ 5.043332] alloc irq_desc for 499 on node 0
[ 5.043338] alloc kstat_irqs on node 0
[ 5.043375] pcieport 0000:00:06.0: setting latency timer to 64
[ 5.043814] alloc irq_desc for 498 on node 0
[ 5.043820] alloc kstat_irqs on node 0
[ 5.043858] pcieport 0000:00:07.0: setting latency timer to 64
[ 5.044302] alloc irq_desc for 497 on node 0
[ 5.044308] alloc kstat_irqs on node 0
[ 5.044346] pcieport 0000:00:08.0: setting latency timer to 64
[ 5.044802] alloc irq_desc for 496 on node 0
[ 5.044808] alloc kstat_irqs on node 0
[ 5.044846] pcieport 0000:00:09.0: setting latency timer to 64
[ 5.045279] alloc irq_desc for 495 on node 0
[ 5.045285] alloc kstat_irqs on node 0
[ 5.045323] pcieport 0000:00:0a.0: setting latency timer to 64
[ 5.045777] alloc irq_desc for 494 on node 0
[ 5.045784] alloc kstat_irqs on node 0
[ 5.045846] pcieport 0000:00:1c.0: setting latency timer to 64
[ 5.046235] alloc irq_desc for 493 on node 0
[ 5.046241] alloc kstat_irqs on node 0
[ 5.046284] pcieport 0000:00:1c.2: setting latency timer to 64
[ 5.046693] aer 0000:00:01.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.046743] aer 0000:00:02.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.046782] aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.046820] aer 0000:00:04.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.046859] aer 0000:00:05.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.046897] aer 0000:00:06.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.046935] aer 0000:00:07.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.046974] aer 0000:00:08.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.047012] aer 0000:00:09.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.047051] aer 0000:00:0a.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.047112] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 5.047347] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 5.047352] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 5.051708] pci-stub: invalid id string ""
[ 5.052452] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 5.052489] ACPI: Power Button [PWRF]
[ 5.093150] thermal LNXTHERM:01: registered as thermal_zone0
[ 5.093201] ACPI: Thermal Zone [THM0] (8 C)
[ 5.097051] registering netback
[ 5.097240] alloc irq_desc for 492 on node 0
[ 5.097246] alloc kstat_irqs on node 0
[ 5.104099] alloc irq_desc for 491 on node 0
[ 5.104106] alloc kstat_irqs on node 0
[ 5.105519] hpet_acpi_add: no address or irqs in _CRS
[ 5.105695] Non-volatile memory driver v1.3
[ 5.105699] Linux agpgart interface v0.103
[ 5.105781] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 5.112754] brd: module loaded
[ 5.115491] loop: module loaded
[ 5.116595] Fixed MDIO Bus: probed
[ 5.116678] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009)
[ 5.116718] xen: registering gsi 16 triggering 0 polarity 1
[ 5.116723] xen_allocate_pirq: returning irq 16 for gsi 16
[ 5.116727] xen: --> irq=16
[ 5.116731] Already setup the GSI :16
[ 5.116735] bnx2 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 5.116750] bnx2 0000:02:00.0: setting latency timer to 64
[ 5.117139] bnx2 0000:02:00.0: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.117146] bnx2 0000:02:00.0: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.118215] eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f4000000, IRQ 16, node addr 00:24:81:e8:a5:1c
[ 5.118312] xen: registering gsi 17 triggering 0 polarity 1
[ 5.118322] alloc irq_desc for 17 on node 0
[ 5.118327] alloc kstat_irqs on node 0
[ 5.118337] xen: --> irq=17
[ 5.118343] bnx2 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 5.118359] bnx2 0000:02:00.1: setting latency timer to 64
[ 5.118730] bnx2 0000:02:00.1: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.118737] bnx2 0000:02:00.1: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.120124] eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f2000000, IRQ 17, node addr 00:24:81:e8:a5:1e
[ 5.120181] xen: registering gsi 18 triggering 0 polarity 1
[ 5.120190] alloc irq_desc for 18 on node 0
[ 5.120195] alloc kstat_irqs on node 0
[ 5.120204] xen: --> irq=18
[ 5.120210] bnx2 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 5.120225] bnx2 0000:03:00.0: setting latency timer to 64
[ 5.120585] bnx2 0000:03:00.0: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.120592] bnx2 0000:03:00.0: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.122011] eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f8000000, IRQ 18, node addr 00:24:81:e8:a5:20
[ 5.122069] xen: registering gsi 19 triggering 0 polarity 1
[ 5.122078] alloc irq_desc for 19 on node 0
[ 5.122083] alloc kstat_irqs on node 0
[ 5.122092] xen: --> irq=19
[ 5.122098] bnx2 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 5.122112] bnx2 0000:03:00.1: setting latency timer to 64
[ 5.122453] bnx2 0000:03:00.1: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.122460] bnx2 0000:03:00.1: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.123955] eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f6000000, IRQ 19, node addr 00:24:81:e8:a5:22
[ 5.124523] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.124614] xen: registering gsi 20 triggering 0 polarity 1
[ 5.124623] alloc irq_desc for 20 on node 0
[ 5.124628] alloc kstat_irqs on node 0
[ 5.124637] xen: --> irq=20
[ 5.124643] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 5.124680] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 5.124688] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 5.125495] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[ 5.125663] ehci_hcd 0000:00:1d.7: debug port 1
[ 5.129561] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 5.129619] ehci_hcd 0000:00:1d.7: irq 20, io mem 0xf1df0000
[ 5.147612] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 5.147853] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.147859] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.147864] usb usb1: Product: EHCI Host Controller
[ 5.147867] usb usb1: Manufacturer: Linux 2.6.32.21-xenoprof-1 ehci_hcd
[ 5.147872] usb usb1: SerialNumber: 0000:00:1d.7
[ 5.148391] usb usb1: configuration #1 chosen from 1 choice
[ 5.148648] hub 1-0:1.0: USB hub found
[ 5.148721] hub 1-0:1.0: 8 ports detected
[ 5.149324] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 5.149529] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.149747] xen: registering gsi 20 triggering 0 polarity 1
[ 5.149752] xen_allocate_pirq: returning irq 20 for gsi 20
[ 5.149755] xen: --> irq=20
[ 5.149759] Already setup the GSI :20
[ 5.149763] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 5.149782] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 5.149790] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 5.149978] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 5.150035] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001000
[ 5.150220] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.150226] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.150230] usb usb2: Product: UHCI Host Controller
[ 5.150234] usb usb2: Manufacturer: Linux 2.6.32.21-xenoprof-1 uhci_hcd
[ 5.150238] usb usb2: SerialNumber: 0000:00:1d.0
[ 5.150530] usb usb2: configuration #1 chosen from 1 choice
[ 5.150654] hub 2-0:1.0: USB hub found
[ 5.150751] hub 2-0:1.0: 2 ports detected
[ 5.151097] xen: registering gsi 23 triggering 0 polarity 1
[ 5.151111] alloc irq_desc for 23 on node 0
[ 5.151117] alloc kstat_irqs on node 0
[ 5.151126] xen: --> irq=23
[ 5.151131] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 23 (level, low) -> IRQ 23
[ 5.151151] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 5.151158] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 5.151364] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[ 5.151447] uhci_hcd 0000:00:1d.1: irq 23, io base 0x00001020
[ 5.151645] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.151650] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.151654] usb usb3: Product: UHCI Host Controller
[ 5.151658] usb usb3: Manufacturer: Linux 2.6.32.21-xenoprof-1 uhci_hcd
[ 5.151662] usb usb3: SerialNumber: 0000:00:1d.1
[ 5.151958] usb usb3: configuration #1 chosen from 1 choice
[ 5.152097] hub 3-0:1.0: USB hub found
[ 5.152140] hub 3-0:1.0: 2 ports detected
[ 5.152389] xen: registering gsi 22 triggering 0 polarity 1
[ 5.152398] alloc irq_desc for 22 on node 0
[ 5.152403] alloc kstat_irqs on node 0
[ 5.152412] xen: --> irq=22
[ 5.152418] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 5.152437] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 5.152445] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 5.152622] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[ 5.152706] uhci_hcd 0000:00:1d.2: irq 22, io base 0x00001040
[ 5.152899] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.152905] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.152909] usb usb4: Product: UHCI Host Controller
[ 5.152913] usb usb4: Manufacturer: Linux 2.6.32.21-xenoprof-1 uhci_hcd
[ 5.152917] usb usb4: SerialNumber: 0000:00:1d.2
[ 5.153208] usb usb4: configuration #1 chosen from 1 choice
[ 5.153333] hub 4-0:1.0: USB hub found
[ 5.153374] hub 4-0:1.0: 2 ports detected
[ 5.153601] xen: registering gsi 23 triggering 0 polarity 1
[ 5.153606] xen_allocate_pirq: returning irq 23 for gsi 23
[ 5.153610] xen: --> irq=23
[ 5.153613] Already setup the GSI :23
[ 5.153617] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 23 (level, low) -> IRQ 23
[ 5.153646] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 5.153653] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 5.153835] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[ 5.153910] uhci_hcd 0000:00:1d.3: irq 23, io base 0x00001060
[ 5.154093] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.154098] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.154103] usb usb5: Product: UHCI Host Controller
[ 5.154106] usb usb5: Manufacturer: Linux 2.6.32.21-xenoprof-1 uhci_hcd
[ 5.154110] usb usb5: SerialNumber: 0000:00:1d.3
[ 5.154398] usb usb5: configuration #1 chosen from 1 choice
[ 5.154606] hub 5-0:1.0: USB hub found
[ 5.154652] hub 5-0:1.0: 2 ports detected
[ 5.154940] xen: registering gsi 22 triggering 0 polarity 1
[ 5.154945] xen_allocate_pirq: returning irq 22 for gsi 22
[ 5.154949] xen: --> irq=22
[ 5.154952] Already setup the GSI :22
[ 5.154956] uhci_hcd 0000:01:04.4: PCI INT B -> GSI 22 (level, low) -> IRQ 22
[ 5.154976] uhci_hcd 0000:01:04.4: UHCI Host Controller
[ 5.155149] uhci_hcd 0000:01:04.4: new USB bus registered, assigned bus number 6
[ 5.155174] uhci_hcd 0000:01:04.4: port count misdetected? forcing to 2 ports
[ 5.155864] uhci_hcd 0000:01:04.4: irq 22, io base 0x00003800
[ 5.156117] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.156122] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.156126] usb usb6: Product: UHCI Host Controller
[ 5.156130] usb usb6: Manufacturer: Linux 2.6.32.21-xenoprof-1 uhci_hcd
[ 5.156134] usb usb6: SerialNumber: 0000:01:04.4
[ 5.156427] usb usb6: configuration #1 chosen from 1 choice
[ 5.156550] hub 6-0:1.0: USB hub found
[ 5.156592] hub 6-0:1.0: 2 ports detected
[ 5.157123] PNP: PS/2 Controller [PNP0303:KBD,PNP0f0e:PS2M] at 0x60,0x64 irq 1,12
[ 5.158955] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 5.158988] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 5.159531] mice: PS/2 mouse device common for all mice
[ 5.160272] rtc_cmos 00:09: RTC can wake from S4
[ 5.160517] rtc_cmos 00:09: rtc core: registered rtc_cmos as rtc0
[ 5.160582] rtc0: alarms up to one year, y3k, 114 bytes nvram
[ 5.161323] device-mapper: uevent: version 1.0.3
[ 5.161788] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[ 5.162495] cpuidle: using governor ladder
[ 5.162500] cpuidle: using governor menu
[ 5.162676] nf_conntrack version 0.5.0 (4066 buckets, 16264 max)
[ 5.163119] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[ 5.163124] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
[ 5.163128] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 5.166885] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 5.166919] TCP cubic registered
[ 5.166923] Initializing XFRM netlink socket
[ 5.166974] NET: Registered protocol family 17
[ 5.167539] PM: Resume from disk failed.
[ 5.167692] registered taskstats version 1
[ 5.168074] No TPM chip found, activating TPM-bypass!
[ 5.172191] Magic number: 10:294:998
[ 5.172215] pnp 00:00: hash matches
[ 5.172317] rtc_cmos 00:09: setting system clock to 2010-09-27 17:59:32 UTC (1285610372)
[ 5.172441] Initalizing network drop monitor service
[ 5.173643] Freeing unused kernel memory: 2620k freed
[ 5.174863] Write protecting the kernel read-only data: 8972k
[ 5.187360] busybox used greatest stack depth: 5168 bytes left
[ 5.204880] exe used greatest stack depth: 4752 bytes left
[ 5.258589] udev: starting version 151
[ 5.467676] usb 1-4: new high speed USB device using ehci_hcd and address 2
[ 5.620461] usb 1-4: New USB device found, idVendor=154b, idProduct=003a
[ 5.620468] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5.620473] usb 1-4: Product: USB 2.0 FD
[ 5.620477] usb 1-4: Manufacturer: PNY Technologies
[ 5.620480] usb 1-4: SerialNumber: AAA1194400020359
[ 5.620774] usb 1-4: configuration #1 chosen from 1 choice
[ 5.797876] usb 6-1: new full speed USB device using uhci_hcd and address 2
[ 5.956676] usb 6-1: New USB device found, idVendor=03f0, idProduct=1027
[ 5.956682] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5.956688] usb 6-1: Product: Virtual Keyboard
[ 5.956691] usb 6-1: Manufacturer: HP
[ 5.956954] usb 6-1: configuration #1 chosen from 1 choice
[ 5.961942] Initializing USB Mass Storage driver...
[ 5.990137] scsi0 : SCSI emulation for USB Mass Storage devices
[ 6.004410] usbcore: registered new interface driver usb-storage
[ 6.004644] USB Mass Storage support registered.
[ 6.004694] usb-storage: device found at 2
[ 6.004697] usb-storage: waiting for device to settle before scanning
[ 6.014328] HP CISS Driver (v 3.6.20)
[ 6.034636] xen: registering gsi 28 triggering 0 polarity 1
[ 6.034648] alloc irq_desc for 28 on node 0
[ 6.034654] alloc kstat_irqs on node 0
[ 6.034665] xen: --> irq=28
[ 6.034675] cciss 0000:04:00.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 6.034864] alloc irq_desc for 490 on node 0
[ 6.034870] alloc kstat_irqs on node 0
[ 6.034946] alloc irq_desc for 489 on node 0
[ 6.034951] alloc kstat_irqs on node 0
[ 6.035021] alloc irq_desc for 488 on node 0
[ 6.035026] alloc kstat_irqs on node 0
[ 6.035099] alloc irq_desc for 487 on node 0
[ 6.035105] alloc kstat_irqs on node 0
[ 6.037945] IRQ 488/cciss0: IRQF_DISABLED is not guaranteed on shared IRQs
[ 6.038002] cciss0: <0x323a> at PCI 0000:04:00.0 IRQ 488 using DAC
[ 6.067515] cciss/c0d0: p1 p2 < p5 >
[ 6.133924] modprobe used greatest stack depth: 3568 bytes left
[ 6.149806] usbcore: registered new interface driver hiddev
[ 6.155013] input: HP Virtual Keyboard as /devices/pci0000:00/0000:00:1e.0/0000:01:04.4/usb6/6-1/6-1:1.0/input/input1
[ 6.155990] generic-usb 0003:03F0:1027.0001: input,hidraw0: USB HID v1.01 Keyboard [HP Virtual Keyboard] on usb-0000:01:04.4-1/input0
[ 6.165501] input: HP Virtual Keyboard as /devices/pci0000:00/0000:00:1e.0/0000:01:04.4/usb6/6-1/6-1:1.1/input/input2
[ 6.166125] generic-usb 0003:03F0:1027.0002: input,hidraw1: USB HID v1.01 Mouse [HP Virtual Keyboard] on usb-0000:01:04.4-1/input1
[ 6.166252] usbcore: registered new interface driver usbhid
[ 6.166487] usbhid: v2.6:USB HID core driver
[ 6.237879] usb 5-2: new low speed USB device using uhci_hcd and address 2
[ 6.422053] usb 5-2: New USB device found, idVendor=0624, idProduct=0422
[ 6.422060] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.422065] usb 5-2: Product: Avocent USBIAC
[ 6.422068] usb 5-2: Manufacturer: Avocent
[ 6.422320] usb 5-2: configuration #1 chosen from 1 choice
[ 6.458085] input: Avocent Avocent USBIAC as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/input/input3
[ 6.458408] generic-usb 0003:0624:0422.0003: input,hidraw2: USB HID v1.10 Keyboard [Avocent Avocent USBIAC] on usb-0000:00:1d.3-2/input0
[ 6.488618] input: Avocent Avocent USBIAC as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/input/input4
[ 6.489247] generic-usb 0003:0624:0422.0004: input,hidraw3: USB HID v1.10 Mouse [Avocent Avocent USBIAC] on usb-0000:00:1d.3-2/input1
[ 7.272271] kjournald starting. Commit interval 5 seconds
[ 7.272491] EXT3-fs: mounted filesystem with ordered data mode.
[ 8.102778] plymouthd used greatest stack depth: 2144 bytes left
[ 8.706832] Adding 974840k swap on /dev/mapper/system-dom0_swap. Priority:-1 extents:1 across:974840k
[ 8.833510] udev: starting version 151
[ 9.495969] EXT3 FS on dm-2, internal journal
[ 10.446690] xen: registering gsi 22 triggering 0 polarity 1
[ 10.446694] xen_allocate_pirq: returning irq 22 for gsi 22
[ 10.446696] xen: --> irq=22
[ 10.446700] Already setup the GSI :22
[ 10.446703] hpilo 0000:01:04.2: PCI INT B -> GSI 22 (level, low) -> IRQ 22
[ 10.451789] xen: registering gsi 21 triggering 0 polarity 1
[ 10.451798] alloc irq_desc for 21 on node 0
[ 10.451803] alloc kstat_irqs on node 0
[ 10.451812] xen: --> irq=21
[ 10.451818] hpwdt 0000:01:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 10.451835] hpwdt: New timer passed in is 30 seconds.
[ 10.453137] hp Watchdog Timer Driver: 1.1.1, timer margin: 30 seconds (nowayout=0), allow kernel dump: OFF (default = 0/OFF), priority: LAST (default = 0/LAST).
[ 10.517188] ipmi message handler version 39.2
[ 10.572998] Bridge firewalling registered
[ 10.604169] IPMI System Interface driver.
[ 10.630842] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0
[ 11.010412] usb-storage: device scan complete
[ 11.028398] scsi 0:0:0:0: Direct-Access PNY USB 2.0 FD 4096 PQ: 0 ANSI: 0 CCS
[ 11.075016] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 11.099911] sd 0:0:0:0: [sda] 8028160 512-byte logical blocks: (4.11 GB/3.82 GiB)
[ 11.100916] sd 0:0:0:0: [sda] Write Protect is off
[ 11.100919] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 11.100921] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 11.112929] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 11.112958] sda: sda1 sda2 sda3
[ 11.135688] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 11.135700] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 11.179696] [drm] Initialized drm 1.1.0 20060810
[ 11.216506] tun: Universal TUN/TAP device driver, 1.6
[ 11.216509] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 11.303881] ipmi: Found new BMC (man_id: 0x00000b, prod_id: 0x0000, dev_id: 0x11)
[ 11.303970] IPMI kcs interface initialized
[ 11.303982] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
[ 11.303985] ipmi_si: duplicate interface
[ 11.304105] xen: registering gsi 21 triggering 0 polarity 1
[ 11.304109] xen_allocate_pirq: returning irq 21 for gsi 21
[ 11.304111] xen: --> irq=21
[ 11.304115] Already setup the GSI :21
[ 11.304117] ipmi_si 0000:01:04.6: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 11.304120] ipmi_si: Trying PCI-specified kcs state machine at mem address 0xf1ef0000, slave address 0x0, irq 21
[ 11.548637] egrep used greatest stack depth: 2032 bytes left
[ 11.587704] IRQ 21/ipmi_si: IRQF_DISABLED is not guaranteed on shared IRQs
[ 11.587780] Using irq 21
[ 11.643559] [drm] radeon defaulting to kernel modesetting.
[ 11.643562] [drm] radeon kernel modesetting enabled.
[ 11.814762] ipmi: interfacing existing BMC (man_id: 0x00000b, prod_id: 0x0000, dev_id: 0x11)
[ 11.814818] IPMI kcs interface initialized
[ 11.815059] xen: registering gsi 23 triggering 0 polarity 1
[ 11.815063] xen_allocate_pirq: returning irq 23 for gsi 23
[ 11.815065] xen: --> irq=23
[ 11.815069] Already setup the GSI :23
[ 11.815072] radeon 0000:01:03.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 11.817299] [drm] radeon: Initializing kernel modesetting.
[ 11.817338] [drm] register mmio base: 0xF1FF0000
[ 11.817340] [drm] register mmio size: 65536
[ 11.817649] [drm] GPU reset succeed (RBBM_STATUS=0x00000140)
[ 11.817665] [drm] radeon: VRAM 64M
[ 11.817667] [drm] radeon: VRAM from 0x00000000 to 0x03FFFFFF
[ 11.817669] [drm] radeon: GTT 512M
[ 11.817671] [drm] radeon: GTT from 0x20000000 to 0x3FFFFFFF
[ 11.818814] [drm] radeon: irq initialized.
[ 11.825542] [drm] Detected VRAM RAM=64M, BAR=128M
[ 11.825546] [drm] RAM width 16bits DDR
[ 11.826110] [TTM] Zone kernel: Available graphics memory: 261534 kiB.
[ 11.826330] [drm] radeon: 64M of VRAM memory ready
[ 11.826333] [drm] radeon: 512M of GTT memory ready.
[ 11.826563] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 11.838027] [drm] radeon: cp idle (0x00008080)
[ 11.838331] [drm] Loading R100 Microcode
[ 11.839096] platform radeon_cp.0: firmware: requesting radeon/R100_cp.bin
[ 12.043046] [drm] radeon: ring at 0x0000000020000000
[ 12.043105] [drm] ring test succeeded in 1 usecs
[ 12.048639] [drm] radeon: ib pool ready.
[ 12.061738] [drm] ib test succeeded in 0 usecs
[ 12.065969] [drm] Radeon Display Connectors
[ 12.065971] [drm] Connector 0:
[ 12.065973] [drm] VGA
[ 12.065975] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[ 12.065977] [drm] Encoders:
[ 12.065979] [drm] CRT1: INTERNAL_DAC1
[ 12.065980] [drm] Connector 1:
[ 12.065982] [drm] VGA
[ 12.065984] [drm] DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
[ 12.065986] [drm] Encoders:
[ 12.065987] [drm] CRT2: INTERNAL_DAC2
[ 12.077698] kjournald starting. Commit interval 5 seconds
[ 12.198752] EXT3 FS on dm-1, internal journal
[ 12.198769] EXT3-fs: mounted filesystem with ordered data mode.
[ 12.290574] [drm] fb mappable at 0xE8040000
[ 12.290577] [drm] vram apper at 0xE8000000
[ 12.290579] [drm] size 3145728
[ 12.290580] [drm] fb depth is 24
[ 12.290582] [drm] pitch is 4096
[ 12.291297] fb0: radeondrmfb frame buffer device
[ 12.291300] registered panic notifier
[ 12.291307] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:03.0 on minor 0
[ 12.625259] [drm] TV-10: set mode 1024x768 25
[ 12.637859] alloc irq_desc for 486 on node 0
[ 12.637863] alloc kstat_irqs on node 0
[ 12.670637] Console: switching to colour frame buffer device 128x48
[ 12.734126] Event-channel device installed.
[ 12.786871] bnx2: eth0: using MSI
[ 12.838467] dhclient-script used greatest stack depth: 1728 bytes left
[ 12.972779] board type is 1
[ 13.652195] NET: Registered protocol family 10
[ 13.665935] lo: Disabled Privacy Extensions
[ 13.674748] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 14.002336] EXT4-fs (sda1): mounted filesystem with ordered data mode
[ 14.036568] EXT4-fs (sda2): mounted filesystem with ordered data mode
[ 15.976458] bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
[ 15.976603] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 22.955592] svc: failed to register lockdv1 RPC service (errno 97).
[ 22.961190] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 22.967586] NFSD: starting 90-second grace period
[ 26.142222] bnx2: peth0: using MSI
[ 26.142289] ADDRCONF(NETDEV_UP): peth0: link is not ready
[ 29.089178] bnx2: peth0 NIC Copper Link is Up, 1000 Mbps full duplex
[ 29.089295] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready
[ 29.210363] device peth0 entered promiscuous mode
[ 29.259754] eth0: port 1(peth0) entering forwarding state
[ 31.081490] alloc irq_desc for 485 on node 0
[ 31.081496] alloc kstat_irqs on node 0
[ 31.081974] alloc irq_desc for 484 on node 0
[ 31.081984] alloc kstat_irqs on node 0
[ 31.089172] XENBUS: Unable to read cpu state
[ 39.287585] peth0: no IPv6 routers present
[ 433.198984] pciback 0000:07:00.0: seizing device
[ 433.199141] xen: registering gsi 32 triggering 0 polarity 1
[ 433.199165] alloc irq_desc for 32 on node 0
[ 433.199169] alloc kstat_irqs on node 0
[ 433.199180] xen: --> irq=32
[ 433.199189] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[ 433.199200] pciback 0000:07:00.0: PCI INT A disabled
[ 433.199597] pciback 0000:07:00.1: seizing device
[ 433.199697] xen: registering gsi 42 triggering 0 polarity 1
[ 433.199705] alloc irq_desc for 42 on node 0
[ 433.199708] alloc kstat_irqs on node 0
[ 433.199716] xen: --> irq=42
[ 433.199722] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[ 433.199732] pciback 0000:07:00.1: PCI INT B disabled
[ 433.200087] pciback 0000:07:00.2: seizing device
[ 433.200183] xen: registering gsi 47 triggering 0 polarity 1
[ 433.200190] alloc irq_desc for 47 on node 0
[ 433.200194] alloc kstat_irqs on node 0
[ 433.200202] xen: --> irq=47
[ 433.200208] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[ 433.200218] pciback 0000:07:00.2: PCI INT C disabled
[ 433.200578] pciback 0000:07:00.3: seizing device
[ 433.200666] xen: registering gsi 41 triggering 0 polarity 1
[ 433.200680] alloc irq_desc for 41 on node 0
[ 433.200684] alloc kstat_irqs on node 0
[ 433.200692] xen: --> irq=41
[ 433.200697] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[ 433.200708] pciback 0000:07:00.3: PCI INT D disabled
[ 449.622591] alloc irq_desc for 483 on node 0
[ 449.622597] alloc kstat_irqs on node 0
[ 450.319092] device vif1.0 entered promiscuous mode
[ 450.325997] eth0: port 2(vif1.0) entering forwarding state
[ 450.519310] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 451.131510] alloc irq_desc for 482 on node 0
[ 451.131515] alloc kstat_irqs on node 0
[ 454.246452] blkback: ring-ref 8, event-channel 73, protocol 1 (x86_64-abi)
[ 454.246545] alloc irq_desc for 481 on node 0
[ 454.246549] alloc kstat_irqs on node 0
[ 454.283392] alloc irq_desc for 480 on node 0
[ 454.283398] alloc kstat_irqs on node 0
[ 454.320612] alloc irq_desc for 479 on node 0
[ 454.320617] alloc kstat_irqs on node 0
[ 454.320705] ------------[ cut here ]------------
[ 454.320719] WARNING: at kernel/lockdep.c:2323 trace_hardirqs_on_caller+0x12f/0x190()
[ 454.320724] Hardware name: ProLiant DL380 G6
[ 454.320727] Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev xen_evtchn fbcon tileblit font bitblit softcursor xen_pciback radeon ttm drm_kms_helper tun drm ipmi_si i2c_algo_bit serio_raw ipmi_msghandler i2c_core hpwdt hpilo joydev bridge stp llc usbhid hid cciss usb_storage
[ 454.320792] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1
[ 454.320797] Call Trace:
[ 454.320800] <IRQ> [<ffffffff810aa18f>] ? trace_hardirqs_on_caller+0x12f/0x190
[ 454.320811] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
[ 454.320818] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40
[ 454.320824] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20
[ 454.320829] [<ffffffff810aa18f>] trace_hardirqs_on_caller+0x12f/0x190
[ 454.320835] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10
[ 454.320840] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40
[ 454.320847] [<ffffffff813c4fc5>] add_to_net_schedule_list_tail+0x85/0xd0
[ 454.320871] [<ffffffff813c6216>] netif_be_int+0x36/0x160
[ 454.320878] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180
[ 454.320883] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170
[ 454.320890] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
[ 454.320895] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
[ 454.320902] [<ffffffff8101647e>] xen_do_hypervisor_callback+0x1e/0x30
[ 454.320906] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 454.320916] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 454.320922] [<ffffffff813bce54>] ? xb_write+0x1e4/0x290
[ 454.320927] [<ffffffff813bd8ca>] ? xs_talkv+0x6a/0x1f0
[ 454.320932] [<ffffffff813bd8d8>] ? xs_talkv+0x78/0x1f0
[ 454.320937] [<ffffffff813bdbcd>] ? xs_single+0x4d/0x60
[ 454.320942] [<ffffffff813be502>] ? xenbus_read+0x52/0x80
[ 454.320947] [<ffffffff813c87fc>] ? frontend_changed+0x48c/0x770
[ 454.320954] [<ffffffff813bf76d>] ? xenbus_otherend_changed+0xdd/0x1b0
[ 454.320960] [<ffffffff8101122f>] ? xen_restore_fl_direct_end+0x0/0x1
[ 454.320965] [<ffffffff810ac830>] ? lock_release+0xb0/0x230
[ 454.320971] [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20
[ 454.320976] [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160
[ 454.320983] [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40
[ 454.320988] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160
[ 454.320993] [<ffffffff81093086>] ? kthread+0x96/0xb0
[ 454.320998] [<ffffffff8101632a>] ? child_rip+0xa/0x20
[ 454.321003] [<ffffffff81015c90>] ? restore_args+0x0/0x30
[ 454.321008] [<ffffffff81016320>] ? child_rip+0x0/0x20
[ 454.321012] ---[ end trace 26c184d3769c3621 ]---
[ 460.367572] vif1.0: no IPv6 routers present
[ 1433.846036] vcpu 0
[ 1433.846037] 0: masked=0 pending=0 event_sel 00000000
[ 1433.846044] pending:
[ 1433.846048] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846063] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846077] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846112] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846129] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846145] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846161] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846178] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846194]
[ 1433.846198] masks:
[ 1433.846199] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
[ 1433.846221] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
[ 1433.846242] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
[ 1433.846264] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
[ 1433.846286] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
[ 1433.846307] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
[ 1433.846329] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff
[ 1433.846350] ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff fffffffff8000001
[ 1433.846372]
[ 1433.846376] unmasked:
[ 1433.846377] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846394] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846410] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846426] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846442] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846459] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846475] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846491] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1433.846507]
[ 1433.846511] pending list:
[ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
[ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
[ 1882.269834] xen: --> irq=32
[ 1882.269841] Already setup the GSI :32
[ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
[ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a read-only configuration space field at offset 0x62, size 2. This may be harmless, but if you have problems with your device:
[ 1882.270465] 1) see permissive attribute in sysfs
[ 1882.270467] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
[ 1882.270615] alloc irq_desc for 478 on node 0
[ 1882.270625] alloc kstat_irqs on node 0
[ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
[ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
[ 1882.348445] xen: --> irq=42
[ 1882.348472] Already setup the GSI :42
[ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
[ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a read-only configuration space field at offset 0x62, size 2. This may be harmless, but if you have problems with your device:
[ 1882.349066] 1) see permissive attribute in sysfs
[ 1882.349067] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
[ 1882.349205] alloc irq_desc for 477 on node 0
[ 1882.349215] alloc kstat_irqs on node 0
[ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
[ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
[ 1882.402916] xen: --> irq=47
[ 1882.402921] Already setup the GSI :47
[ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
[ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a read-only configuration space field at offset 0x62, size 2. This may be harmless, but if you have problems with your device:
[ 1882.403282] 1) see permissive attribute in sysfs
[ 1882.403282] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
[ 1882.403380] alloc irq_desc for 476 on node 0
[ 1882.403386] alloc kstat_irqs on node 0
[ 1882.634541] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[ 1882.634561] xen: registering gsi 41 triggering 0 polarity 1
[ 1882.634568] xen_allocate_pirq: returning irq 41 for gsi 41
[ 1882.634573] xen: --> irq=41
[ 1882.634654] Already setup the GSI :41
[ 1882.634663] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[ 1882.634685] pciback 0000:07:00.3: setting latency timer to 64
[ 1882.635282] pciback 0000:07:00.3: Driver tried to write to a read-only configuration space field at offset 0x62, size 2. This may be harmless, but if you have problems with your device:
[ 1882.635284] 1) see permissive attribute in sysfs
[ 1882.635284] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
[ 1882.635385] alloc irq_desc for 475 on node 0
[ 1882.635391] alloc kstat_irqs on node 0
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-27 19:16 ` Bruce Edge
@ 2010-09-27 19:54 ` Konrad Rzeszutek Wilk
2010-09-27 23:54 ` Bruce Edge
0 siblings, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-09-27 19:54 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel
On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >
> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> > > One of our developers who is working on a tachyon driver is
> > > complaining that the pvops domU kernel is not working for these MSI
> > > interrupts.
> > > This is using the current head of xen/2.6.32.x on both a single
> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
> > >
> > > Here are his comments:
> > >
> > > - the driver has no problem to enable msi interrupt and request the
> > > interrupt through kernel functions pci_enable_msi & request_irq
> >
> > What shows up in the Xen console when you send the 'q' key? Does it
> > show that the vector is assigned to the appropiate guest?
>
> The Xen console q key shows that the domU is assigned:
>
> (XEN) Interrupts { 32, 41-42, 47 }
Aha!
>
> but the domU thinks it has:
>
> 124/125/126/127
>
> Is there some mapping that's taking place, or is this plain wrong?
That looks wrong. The IRQ numbers (even though they are MSI vectors) are
setup as IRQ numbers in the DomU guest. You should have seen
32:
41:
42:
47:
in you /proc/interrupts on your DomU guest.
I wonder what broke - can you use git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
It has the latest pcifront driver but without the PVonHVM enhancments
so we can try to eliminate the PvONHVM logic out of the picture.
>
> >
> > > - the interrupt does happen. But the interrupt service routine of
> > > tachyon driver doesn't detect any interrupt status related to this
> > > interrupt, which inhibits the tachyon chip from coming on-line. And
> > > there are high count of tachyon interrupt in /proc/interrupts
> >
> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
> > in the MMIO BAR?
> >
>
> The driver would check the appropriate register (tachyon registers) in
> the MMIO to determine the source of interrupts.
OK, so that isn't it. Is there anything at these vectors:
7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
an inkling what device this is set for.
>
> > >
> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> > > 124: 760415 0 0 0 0 0
> > > 0 0 0 0 0 0
> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > > 125: 762234 0 0 0 0 0
> > > 0 0 0 0 0 0
> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > > 126: 764180 0 0 0 0 0
> > > 0 0 0 0 0 0
> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > > 127: 764164 0 0 0 0 0
> > > 0 0 0 0 0 0
> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >
> > Can you provide the full dmesg output?
>
> Attached.
>
> Some possibly related messages on dom0 console:
>
> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
> [ 1882.269834] xen: --> irq=32
> [ 1882.269841] Already setup the GSI :32
> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
> read-only configuration space field at offset 0x62, size 2. This may
> be harmless, but if you have problems with your device:
Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
to find out what is at the configuration space. You could enable
it using the permissive attribute.
> [ 1882.270465] 1) see permissive attribute in sysfs
> [ 1882.270467] 2) report problems to the xen-devel mailing list along
> with details of your device obtained from lspci.
> [ 1882.270615] alloc irq_desc for 478 on node 0
> [ 1882.270625] alloc kstat_irqs on node 0
So for 478: what do you see? xen-pciback I presume?
> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
> [ 1882.348445] xen: --> irq=42
> [ 1882.348472] Already setup the GSI :42
> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
> read-only configuration space field at offset 0x62, size 2. This may
> be harmless, but if you have problems with your device:
> [ 1882.349066] 1) see permissive attribute in sysfs
> [ 1882.349067] 2) report problems to the xen-devel mailing list along
> with details of your device obtained from lspci.
> [ 1882.349205] alloc irq_desc for 477 on node 0
> [ 1882.349215] alloc kstat_irqs on node 0
> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
> [ 1882.402916] xen: --> irq=47
> [ 1882.402921] Already setup the GSI :47
> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
> read-only configuration space field at offset 0x62, size 2. This may
> be harmless, but if you have problems with your device:
> [ 1882.403282] 1) see permissive attribute in sysfs
> [ 1882.403282] 2) report problems to the xen-devel mailing list along
> with details of your device obtained from lspci.
> [ 1882.403380] alloc irq_desc for 476 on node 0
> [ 1882.403386] alloc kstat_irqs on node 0
> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> fault addr e6f80000, iommu reg = ffff82c3fff57000
> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
> (XEN) root_entry = ffff83019ff70000
> (XEN) root_entry[7] = 19cf52001
> (XEN) context = ffff83019cf52000
> (XEN) context[0] = 102_706dc005
> (XEN) l4 = ffff8300706dc000
> (XEN) l4_index = 0
> (XEN) l4[0] = 706db003
> (XEN) l3 = ffff8300706db000
> (XEN) l3_index = 3
> (XEN) l3[3] = 702b6003
> (XEN) l2 = ffff8300702b6000
> (XEN) l2_index = 137
> (XEN) l2[137] = 0
> (XEN) l2[137] not present
> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
That is not good. What changed from your earlier emails that this was triggered? Or
was it triggered all along? What happens if you run the system without the iommu enabled?
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-27 19:54 ` Konrad Rzeszutek Wilk
@ 2010-09-27 23:54 ` Bruce Edge
2010-09-28 1:15 ` Jiang, Yunhong
2010-09-28 14:56 ` Konrad Rzeszutek Wilk
0 siblings, 2 replies; 42+ messages in thread
From: Bruce Edge @ 2010-09-27 23:54 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> >
>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> > > One of our developers who is working on a tachyon driver is
>> > > complaining that the pvops domU kernel is not working for these MSI
>> > > interrupts.
>> > > This is using the current head of xen/2.6.32.x on both a single
>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
>> > >
>> > > Here are his comments:
>> > >
>> > > - the driver has no problem to enable msi interrupt and request the
>> > > interrupt through kernel functions pci_enable_msi & request_irq
>> >
>> > What shows up in the Xen console when you send the 'q' key? Does it
>> > show that the vector is assigned to the appropiate guest?
>>
>> The Xen console q key shows that the domU is assigned:
>>
>> (XEN) Interrupts { 32, 41-42, 47 }
>
> Aha!
>
>>
>> but the domU thinks it has:
>>
>> 124/125/126/127
>>
>> Is there some mapping that's taking place, or is this plain wrong?
>
> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
> setup as IRQ numbers in the DomU guest. You should have seen
>
> 32:
> 41:
> 42:
> 47:
> in you /proc/interrupts on your DomU guest.
>
> I wonder what broke - can you use git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
Please forgive the git ignorance.
Is this the right syntax?
git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32
linux-2.6.32-pv-pcifront
Initialized empty Git repository in
/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
fatal: The remote end hung up unexpectedly
Or:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
Initialized empty Git repository in
/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
remote: fatal: Failed to traverse parents of commit
979e121cb348add17ed8171bf447b27a3a9d1be3
remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed
>
> It has the latest pcifront driver but without the PVonHVM enhancments
> so we can try to eliminate the PvONHVM logic out of the picture.
>
>>
>> >
>> > > - the interrupt does happen. But the interrupt service routine of
>> > > tachyon driver doesn't detect any interrupt status related to this
>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
>> > > there are high count of tachyon interrupt in /proc/interrupts
>> >
>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
>> > in the MMIO BAR?
>> >
>>
>> The driver would check the appropriate register (tachyon registers) in
>> the MMIO to determine the source of interrupts.
>
> OK, so that isn't it. Is there anything at these vectors:
> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
> an inkling what device this is set for.
When I run a distro kernel in hvm mode, I get the expected irq mappings:
'i' - Note 66 - 69
(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
type=PCI-MSI status=00000010 in-flight=0
domain-list=10:127(----),
(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
type=PCI-MSI status=00000010 in-flight=0
domain-list=10:126(----),
(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
type=PCI-MSI status=00000010 in-flight=0
domain-list=10:125(----),
(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
type=PCI-MSI status=00000010 in-flight=0
domain-list=10:124(----)
'q'
(XEN) Interrupts { 32, 41-42, 47, 124-127 }
The same data with pv-ops kernel shows:
'i'
IRQ numbers stop at 65, no 66 - 69 present:
(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
type=PCI-MSI status=00000010 in-flight=0
domain-list=0:289(----),
(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
type=PCI-MSI status=00000002 mapped, unbound
(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
type=PCI-MSI status=00000010 in-flight=0
domain-list=0:287(----),
(XEN) IO-APIC interrupt information:
'q'
(XEN) Interrupts { 32, 41-42, 47 }
>
>>
>> > >
>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
>> > > 124: 760415 0 0 0 0 0
>> > > 0 0 0 0 0 0
>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> > > 125: 762234 0 0 0 0 0
>> > > 0 0 0 0 0 0
>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> > > 126: 764180 0 0 0 0 0
>> > > 0 0 0 0 0 0
>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> > > 127: 764164 0 0 0 0 0
>> > > 0 0 0 0 0 0
>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >
>> > Can you provide the full dmesg output?
>>
>> Attached.
>>
>> Some possibly related messages on dom0 console:
>>
>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
>> [ 1882.269834] xen: --> irq=32
>> [ 1882.269841] Already setup the GSI :32
>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
>> read-only configuration space field at offset 0x62, size 2. This may
>> be harmless, but if you have problems with your device:
>
> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> to find out what is at the configuration space. You could enable
> it using the permissive attribute.
>
>> [ 1882.270465] 1) see permissive attribute in sysfs
>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
>> with details of your device obtained from lspci.
>> [ 1882.270615] alloc irq_desc for 478 on node 0
>> [ 1882.270625] alloc kstat_irqs on node 0
>
> So for 478: what do you see? xen-pciback I presume?
>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
>> [ 1882.348445] xen: --> irq=42
>> [ 1882.348472] Already setup the GSI :42
>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
>> read-only configuration space field at offset 0x62, size 2. This may
>> be harmless, but if you have problems with your device:
>> [ 1882.349066] 1) see permissive attribute in sysfs
>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
>> with details of your device obtained from lspci.
>> [ 1882.349205] alloc irq_desc for 477 on node 0
>> [ 1882.349215] alloc kstat_irqs on node 0
>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
>> [ 1882.402916] xen: --> irq=47
>> [ 1882.402921] Already setup the GSI :47
>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
>> read-only configuration space field at offset 0x62, size 2. This may
>> be harmless, but if you have problems with your device:
>> [ 1882.403282] 1) see permissive attribute in sysfs
>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
>> with details of your device obtained from lspci.
>> [ 1882.403380] alloc irq_desc for 476 on node 0
>> [ 1882.403386] alloc kstat_irqs on node 0
>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
>> fault addr e6f80000, iommu reg = ffff82c3fff57000
>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
>> (XEN) root_entry = ffff83019ff70000
>> (XEN) root_entry[7] = 19cf52001
>> (XEN) context = ffff83019cf52000
>> (XEN) context[0] = 102_706dc005
>> (XEN) l4 = ffff8300706dc000
>> (XEN) l4_index = 0
>> (XEN) l4[0] = 706db003
>> (XEN) l3 = ffff8300706db000
>> (XEN) l3_index = 3
>> (XEN) l3[3] = 702b6003
>> (XEN) l2 = ffff8300702b6000
>> (XEN) l2_index = 137
>> (XEN) l2[137] = 0
>> (XEN) l2[137] not present
>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
>
> That is not good. What changed from your earlier emails that this was triggered?
Nothing
> Or was it triggered all along?
Yes, I just included it for completeness
> What happens if you run the system without the iommu enabled?
Haven't tried yet. Will check that next.
-Bruce
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-27 23:54 ` Bruce Edge
@ 2010-09-28 1:15 ` Jiang, Yunhong
2010-09-28 3:16 ` Bruce Edge
2010-09-28 14:56 ` Konrad Rzeszutek Wilk
1 sibling, 1 reply; 42+ messages in thread
From: Jiang, Yunhong @ 2010-09-28 1:15 UTC (permalink / raw)
To: Bruce Edge, Konrad Rzeszutek Wilk; +Cc: xen-devel@lists.xensource.com
Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
Also is it possible to share the xen output?
Thanks
--jyh
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
>Sent: Tuesday, September 28, 2010 7:54 AM
>To: Konrad Rzeszutek Wilk
>Cc: xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
>On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
><konrad.wilk@oracle.com> wrote:
>> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
>>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
>>> <konrad.wilk@oracle.com> wrote:
>>> >
>>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>>> > > One of our developers who is working on a tachyon driver is
>>> > > complaining that the pvops domU kernel is not working for these MSI
>>> > > interrupts.
>>> > > This is using the current head of xen/2.6.32.x on both a single
>>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
>>> > >
>>> > > Here are his comments:
>>> > >
>>> > > - the driver has no problem to enable msi interrupt and request the
>>> > > interrupt through kernel functions pci_enable_msi & request_irq
>>> >
>>> > What shows up in the Xen console when you send the 'q' key? Does it
>>> > show that the vector is assigned to the appropiate guest?
>>>
>>> The Xen console q key shows that the domU is assigned:
>>>
>>> (XEN) Interrupts { 32, 41-42, 47 }
>>
>> Aha!
>>
>>>
>>> but the domU thinks it has:
>>>
>>> 124/125/126/127
>>>
>>> Is there some mapping that's taking place, or is this plain wrong?
>>
>> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
>> setup as IRQ numbers in the DomU guest. You should have seen
>>
>> 32:
>> 41:
>> 42:
>> 47:
>> in you /proc/interrupts on your DomU guest.
>>
>> I wonder what broke - can you use
>git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
>
>Please forgive the git ignorance.
>
>Is this the right syntax?
>
>git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32
>linux-2.6.32-pv-pcifront
>
>Initialized empty Git repository in
>/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
>fatal: The remote end hung up unexpectedly
>
>Or:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>
>Initialized empty Git repository in
>/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
>remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
>remote: fatal: Failed to traverse parents of commit
>979e121cb348add17ed8171bf447b27a3a9d1be3
>remote: aborting due to possible repository corruption on the remote side.
>fatal: early EOF
>fatal: index-pack failed
>
>>
>> It has the latest pcifront driver but without the PVonHVM enhancments
>> so we can try to eliminate the PvONHVM logic out of the picture.
>>
>>>
>>> >
>>> > > - the interrupt does happen. But the interrupt service routine of
>>> > > tachyon driver doesn't detect any interrupt status related to this
>>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
>>> > > there are high count of tachyon interrupt in /proc/interrupts
>>> >
>>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
>>> > in the MMIO BAR?
>>> >
>>>
>>> The driver would check the appropriate register (tachyon registers) in
>>> the MMIO to determine the source of interrupts.
>>
>> OK, so that isn't it. Is there anything at these vectors:
>> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
>> an inkling what device this is set for.
>
>When I run a distro kernel in hvm mode, I get the expected irq mappings:
>
>'i' - Note 66 - 69
>(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:127(----),
>(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:126(----),
>(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:125(----),
>(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:124(----)
>
>
>'q'
>(XEN) Interrupts { 32, 41-42, 47, 124-127 }
>
>
>The same data with pv-ops kernel shows:
>
>'i'
>IRQ numbers stop at 65, no 66 - 69 present:
>
>(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=0:289(----),
>(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
>type=PCI-MSI status=00000002 mapped, unbound
>(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=0:287(----),
>(XEN) IO-APIC interrupt information:
>
>'q'
>(XEN) Interrupts { 32, 41-42, 47 }
>
>>
>>>
>>> > >
>>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
>>> > >
>124: 760415 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>125: 762234 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>126: 764180 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>127: 764164 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> >
>>> > Can you provide the full dmesg output?
>>>
>>> Attached.
>>>
>>> Some possibly related messages on dom0 console:
>>>
>>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
>>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
>>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
>>> [ 1882.269834] xen: --> irq=32
>>> [ 1882.269841] Already setup the GSI :32
>>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
>>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
>>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>
>> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
>> to find out what is at the configuration space. You could enable
>> it using the permissive attribute.
>>
>>> [ 1882.270465] 1) see permissive attribute in sysfs
>>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.270615] alloc irq_desc for 478 on node 0
>>> [ 1882.270625] alloc kstat_irqs on node 0
>>
>> So for 478: what do you see? xen-pciback I presume?
>>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
>>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
>>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
>>> [ 1882.348445] xen: --> irq=42
>>> [ 1882.348472] Already setup the GSI :42
>>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
>>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
>>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>> [ 1882.349066] 1) see permissive attribute in sysfs
>>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.349205] alloc irq_desc for 477 on node 0
>>> [ 1882.349215] alloc kstat_irqs on node 0
>>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
>>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
>>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
>>> [ 1882.402916] xen: --> irq=47
>>> [ 1882.402921] Already setup the GSI :47
>>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
>>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
>>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>> [ 1882.403282] 1) see permissive attribute in sysfs
>>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.403380] alloc irq_desc for 476 on node 0
>>> [ 1882.403386] alloc kstat_irqs on node 0
>>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
>>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
>>> fault addr e6f80000, iommu reg = ffff82c3fff57000
>>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
>>> (XEN) root_entry = ffff83019ff70000
>>> (XEN) root_entry[7] = 19cf52001
>>> (XEN) context = ffff83019cf52000
>>> (XEN) context[0] = 102_706dc005
>>> (XEN) l4 = ffff8300706dc000
>>> (XEN) l4_index = 0
>>> (XEN) l4[0] = 706db003
>>> (XEN) l3 = ffff8300706db000
>>> (XEN) l3_index = 3
>>> (XEN) l3[3] = 702b6003
>>> (XEN) l2 = ffff8300702b6000
>>> (XEN) l2_index = 137
>>> (XEN) l2[137] = 0
>>> (XEN) l2[137] not present
>>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
>>
>> That is not good. What changed from your earlier emails that this was triggered?
>
>Nothing
>> Or was it triggered all along?
>
>Yes, I just included it for completeness
>
>> What happens if you run the system without the iommu enabled?
>
>Haven't tried yet. Will check that next.
>
>-Bruce
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 1:15 ` Jiang, Yunhong
@ 2010-09-28 3:16 ` Bruce Edge
2010-09-28 3:26 ` Jiang, Yunhong
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-09-28 3:16 UTC (permalink / raw)
To: Jiang, Yunhong; +Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk
[-- Attachment #1.1: Type: text/plain, Size: 14479 bytes --]
On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com>wrote:
> Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
>
Yes, there is 1 quad port card is this sytem:
07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> Also is it possible to share the xen output?
>
I attached the dom0 boot output. Let me know if you wanted something else.
Also, here's the dom0 console output upon starting the VM: This lockdep
error started with the release of 2.6.32.21. Note that I'm running the same
kernel for the domU and dom0.
[ 1817.684097] ------------[ cut here ]------------
[ 1817.684113] WARNING: at kernel/lockdep.c:2323
trace_hardirqs_on_caller+0x12f/0x190()
[ 1817.684119] Hardware name: ProLiant DL380 G6
[ 1817.684122] Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs
xen_gntdev fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback
radeon ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core
ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss
usb_storage
[ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1
[ 1817.684195] Call Trace:
[ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
trace_hardirqs_on_caller+0x12f/0x190
[ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
[ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40
[ 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20
[ 1817.684229] [<ffffffff810aa18f>] trace_hardirqs_on_caller+0x12f/0x190
[ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10
[ 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40
[ 1817.684266] [<ffffffff813c4fc5>] add_to_net_schedule_list_tail+0x85/0xd0
[ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160
[ 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180
[ 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170
[ 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
[ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
[ 1817.684304] [<ffffffff8101647e>] xen_do_hypervisor_callback+0x1e/0x30
[ 1817.684308] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1817.684319] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1817.684325] [<ffffffff813bce54>] ? xb_write+0x1e4/0x290
[ 1817.684330] [<ffffffff813bd8ca>] ? xs_talkv+0x6a/0x1f0
[ 1817.684336] [<ffffffff813bd8d8>] ? xs_talkv+0x78/0x1f0
[ 1817.684341] [<ffffffff813bdbcd>] ? xs_single+0x4d/0x60
[ 1817.684346] [<ffffffff813be502>] ? xenbus_read+0x52/0x80
[ 1817.684352] [<ffffffff813c87fc>] ? frontend_changed+0x48c/0x770
[ 1817.684358] [<ffffffff813bf76d>] ? xenbus_otherend_changed+0xdd/0x1b0
[ 1817.684365] [<ffffffff8101122f>] ? xen_restore_fl_direct_end+0x0/0x1
[ 1817.684371] [<ffffffff810ac830>] ? lock_release+0xb0/0x230
[ 1817.684376] [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20
[ 1817.684382] [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160
[ 1817.684389] [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40
[ 1817.684394] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160
[ 1817.684400] [<ffffffff81093086>] ? kthread+0x96/0xb0
[ 1817.684405] [<ffffffff8101632a>] ? child_rip+0xa/0x20
[ 1817.684410] [<ffffffff81015c90>] ? restore_args+0x0/0x30
[ 1817.684415] [<ffffffff81016320>] ? child_rip+0x0/0x20
-Bruce
>
> Thanks
> --jyh
>
> >-----Original Message-----
> >From: xen-devel-bounces@lists.xensource.com
> >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
> >Sent: Tuesday, September 28, 2010 7:54 AM
> >To: Konrad Rzeszutek Wilk
> >Cc: xen-devel@lists.xensource.com
> >Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on
> Nehalem
> >
> >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> ><konrad.wilk@oracle.com> wrote:
> >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> >>> <konrad.wilk@oracle.com> wrote:
> >>> >
> >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> >>> > > One of our developers who is working on a tachyon driver is
> >>> > > complaining that the pvops domU kernel is not working for these MSI
> >>> > > interrupts.
> >>> > > This is using the current head of xen/2.6.32.x on both a single
> >>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> >>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
> >>> > >
> >>> > > Here are his comments:
> >>> > >
> >>> > > - the driver has no problem to enable msi interrupt and request the
> >>> > > interrupt through kernel functions pci_enable_msi & request_irq
> >>> >
> >>> > What shows up in the Xen console when you send the 'q' key? Does it
> >>> > show that the vector is assigned to the appropiate guest?
> >>>
> >>> The Xen console q key shows that the domU is assigned:
> >>>
> >>> (XEN) Interrupts { 32, 41-42, 47 }
> >>
> >> Aha!
> >>
> >>>
> >>> but the domU thinks it has:
> >>>
> >>> 124/125/126/127
> >>>
> >>> Is there some mapping that's taking place, or is this plain wrong?
> >>
> >> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
> >> setup as IRQ numbers in the DomU guest. You should have seen
> >>
> >> 32:
> >> 41:
> >> 42:
> >> 47:
> >> in you /proc/interrupts on your DomU guest.
> >>
> >> I wonder what broke - can you use
> >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> >
> >Please forgive the git ignorance.
> >
> >Is this the right syntax?
> >
> >git clone git://
> git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32
> >linux-2.6.32-pv-pcifront
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
> >fatal: The remote end hung up unexpectedly
> >
> >Or:
> >
> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> >remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> >remote: fatal: Failed to traverse parents of commit
> >979e121cb348add17ed8171bf447b27a3a9d1be3
> >remote: aborting due to possible repository corruption on the remote side.
> >fatal: early EOF
> >fatal: index-pack failed
> >
> >>
> >> It has the latest pcifront driver but without the PVonHVM enhancments
> >> so we can try to eliminate the PvONHVM logic out of the picture.
> >>
> >>>
> >>> >
> >>> > > - the interrupt does happen. But the interrupt service routine of
> >>> > > tachyon driver doesn't detect any interrupt status related to this
> >>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
> >>> > > there are high count of tachyon interrupt in /proc/interrupts
> >>> >
> >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
> >>> > in the MMIO BAR?
> >>> >
> >>>
> >>> The driver would check the appropriate register (tachyon registers) in
> >>> the MMIO to determine the source of interrupts.
> >>
> >> OK, so that isn't it. Is there anything at these vectors:
> >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should
> give you
> >> an inkling what device this is set for.
> >
> >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> >
> >'i' - Note 66 - 69
> >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:127(----),
> >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:126(----),
> >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:125(----),
> >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:124(----)
> >
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> >
> >
> >The same data with pv-ops kernel shows:
> >
> >'i'
> >IRQ numbers stop at 65, no 66 - 69 present:
> >
> >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:289(----),
> >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> >type=PCI-MSI status=00000002 mapped, unbound
> >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:287(----),
> >(XEN) IO-APIC interrupt information:
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47 }
> >
> >>
> >>>
> >>> > >
> >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> >>> > >
> >124: 760415 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >125: 762234 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >126: 764180 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >127: 764164 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> >
> >>> > Can you provide the full dmesg output?
> >>>
> >>> Attached.
> >>>
> >>> Some possibly related messages on dom0 console:
> >>>
> >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
> >>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
> >>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
> >>> [ 1882.269834] xen: --> irq=32
> >>> [ 1882.269841] Already setup the GSI :32
> >>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low)
> -> IRQ 32
> >>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
> >>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>
> >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> >> to find out what is at the configuration space. You could enable
> >> it using the permissive attribute.
> >>
> >>> [ 1882.270465] 1) see permissive attribute in sysfs
> >>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> >>> [ 1882.270625] alloc kstat_irqs on node 0
> >>
> >> So for 478: what do you see? xen-pciback I presume?
> >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
> >>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
> >>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
> >>> [ 1882.348445] xen: --> irq=42
> >>> [ 1882.348472] Already setup the GSI :42
> >>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low)
> -> IRQ 42
> >>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
> >>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>> [ 1882.349066] 1) see permissive attribute in sysfs
> >>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> >>> [ 1882.349215] alloc kstat_irqs on node 0
> >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
> >>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
> >>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
> >>> [ 1882.402916] xen: --> irq=47
> >>> [ 1882.402921] Already setup the GSI :47
> >>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low)
> -> IRQ 47
> >>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
> >>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>> [ 1882.403282] 1) see permissive attribute in sysfs
> >>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> >>> [ 1882.403386] alloc kstat_irqs on node 0
> >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> >>> fault addr e6f80000, iommu reg = ffff82c3fff57000
> >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn =
> e6f80
> >>> (XEN) root_entry = ffff83019ff70000
> >>> (XEN) root_entry[7] = 19cf52001
> >>> (XEN) context = ffff83019cf52000
> >>> (XEN) context[0] = 102_706dc005
> >>> (XEN) l4 = ffff8300706dc000
> >>> (XEN) l4_index = 0
> >>> (XEN) l4[0] = 706db003
> >>> (XEN) l3 = ffff8300706db000
> >>> (XEN) l3_index = 3
> >>> (XEN) l3[3] = 702b6003
> >>> (XEN) l2 = ffff8300702b6000
> >>> (XEN) l2_index = 137
> >>> (XEN) l2[137] = 0
> >>> (XEN) l2[137] not present
> >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
> >>
> >> That is not good. What changed from your earlier emails that this was
> triggered?
> >
> >Nothing
> >> Or was it triggered all along?
> >
> >Yes, I just included it for completeness
> >
> >> What happens if you run the system without the iommu enabled?
> >
> >Haven't tried yet. Will check that next.
> >
> >-Bruce
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com
> >http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 19380 bytes --]
[-- Attachment #2: dom0-boot.txt --]
[-- Type: text/plain, Size: 52909 bytes --]
__ __ _ _ ___ ____ _
\ \/ /___ _ __ | || | / _ \ |___ \ _ __ ___/ | _ __ _ __ ___
\ // _ \ '_ \ | || |_| | | | __) |__| '__/ __| |__| '_ \| '__/ _ \
/ \ __/ | | | |__ _| |_| | / __/|__| | | (__| |__| |_) | | | __/
/_/\_\___|_| |_| |_|(_)___(_)_____| |_| \___|_| | .__/|_| \___|
|_|
(XEN) Xen version 4.0.2-rc1-pre (bedge@) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) Tue Sep 21 22:20:16 PDT 2010
(XEN) Latest ChangeSet: Fri Sep 17 17:06:57 2010 +0100 21350:6e0ffcd2d9e0
(XEN) Bootloader: GRUB 1.98-1ubuntu7
(XEN) Command line: dummy=dummy dom0_mem=512M dom0_max_vcpus=1 dom0_vcpus_pin=true iommu=1,passthrough,no-intremap loglvl=all loglvl_guest=all loglevl=10 debug apic=on apic_verbosity=verbose extra_guest_irqs=80 com1=115200,8n1 console=com1 console_to_ring noirqbalance xen-pciback.permissive acpi=force numa=on
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009f400 (usable)
(XEN) 000000000009f400 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000df62f000 (usable)
(XEN) 00000000df62f000 - 00000000df63c000 (ACPI data)
(XEN) 00000000df63c000 - 00000000df63d000 (usable)
(XEN) 00000000df63d000 - 00000000e4000000 (reserved)
(XEN) 00000000fec00000 - 00000000fee10000 (reserved)
(XEN) 00000000ff800000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 000000031ffff000 (usable)
(XEN) ACPI: RSDP 000F4F00, 0024 (r2 HP )
(XEN) ACPI: XSDT DF630040, 00BC (r1 HP ProLiant 2 � 162E)
(XEN) ACPI: FACP DF630140, 00F4 (r3 HP ProLiant 2 � 162E)
(XEN) ACPI: DSDT DF630240, 2005 (r1 HP DSDT 1 INTL 20030228)
(XEN) ACPI: FACS DF62F100, 0040
(XEN) ACPI: SPCR DF62F140, 0050 (r1 HP SPCRRBSU 1 � 162E)
(XEN) ACPI: MCFG DF62F1C0, 003C (r1 HP ProLiant 1 0)
(XEN) ACPI: HPET DF62F200, 0038 (r1 HP ProLiant 2 � 162E)
(XEN) ACPI: FFFF DF62F240, 0064 (r2 HP ProLiant 2 � 162E)
(XEN) ACPI: SPMI DF62F2C0, 0040 (r5 HP ProLiant 1 � 162E)
(XEN) ACPI: ERST DF62F300, 01D0 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: APIC DF62F500, 015E (r1 HP ProLiant 2 0)
(XEN) ACPI: SRAT DF62F680, 0570 (r1 HP Proliant 1 � 162E)
(XEN) ACPI: FFFF DF62FC00, 0176 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: BERT DF62FD80, 0030 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: HEST DF62FDC0, 00BC (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: DMAR DF62FE80, 0154 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: SSDT DF632280, 0125 (r3 HP CRSPCI0 2 HP 1)
(XEN) ACPI: SSDT DF6323C0, 0255 (r3 HP riser1a 2 INTL 20061109)
(XEN) ACPI: SSDT DF632640, 025D (r3 HP riser2a 2 INTL 20061109)
(XEN) ACPI: SSDT DF6328C0, 03BB (r1 HP pcc 1 INTL 20090625)
(XEN) ACPI: SSDT DF632C80, 0377 (r1 HP pmab 1 INTL 20090625)
(XEN) ACPI: SSDT DF633000, 22E4 (r1 INTEL PPM RCM 1 INTL 20061109)
(XEN) System RAM: 12277MB (12572472kB)
(XEN) SRAT: PXM 0 -> APIC 0 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 1 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 2 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 3 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 4 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 5 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 6 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 7 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 16 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 17 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 18 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 19 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 20 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 21 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 22 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 23 -> Node 1
(XEN) SRAT: Node 0 PXM 0 0-e0000000
(XEN) SRAT: Node 0 PXM 0 100000000-1a0000000
(XEN) SRAT: Node 1 PXM 1 1a0000000-320000000
(XEN) NUMA: Using 17 for the hash shift.
(XEN) Reserving non-aligned node boundary @ mfn 0x1a0000
(XEN) Domain heap initialised DMA width 30 bits
(XEN) found SMP MP-table at 000f4f80
(XEN) DMI 2.6 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x908
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[904,0], pm1x_evt[900,0]
(XEN) ACPI: wakeup_vec[df62f10c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled)
(XEN) Processor #16 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
(XEN) Processor #4 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x24] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x14] enabled)
(XEN) Processor #20 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x34] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x22] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x12] enabled)
(XEN) Processor #18 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x32] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
(XEN) Processor #6 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x26] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x16] enabled)
(XEN) Processor #22 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x36] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x11] enabled)
(XEN) Processor #17 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x31] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
(XEN) Processor #5 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x25] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x15] enabled)
(XEN) Processor #21 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x35] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
(XEN) Processor #3 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x23] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x13] enabled)
(XEN) Processor #19 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x33] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
(XEN) Processor #7 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x27] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x17] enabled)
(XEN) Processor #23 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x37] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
(XEN) Overriding APIC driver with bigsmp
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec80000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 0, version 32, address 0xfec80000, GSI 24-47
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
(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: Phys. Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 63
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) mapped APIC to ffff82c3ffffe000 (fee00000)
(XEN) mapped IOAPIC to ffff82c3ffffd000 (fec00000)
(XEN) mapped IOAPIC to ffff82c3ffffc000 (fec80000)
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2533.497 MHz processor.
(XEN) Initing memory sharing.
(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) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel machine check reporting enabled
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) enabled ExtINT on CPU#0
(XEN) masked ExtINT on CPU#1
(XEN) masked ExtINT on CPU#2
(XEN) masked ExtINT on CPU#3
(XEN) masked ExtINT on CPU#4
(XEN) masked ExtINT on CPU#5
(XEN) masked ExtINT on CPU#6
(XEN) masked ExtINT on CPU#7
(XEN) masked ExtINT on CPU#8
(XEN) masked ExtINT on CPU#9
(XEN) masked ExtINT on CPU#10
(XEN) masked ExtINT on CPU#11
(XEN) masked ExtINT on CPU#12
(XEN) masked ExtINT on CPU#13
(XEN) masked ExtINT on CPU#14
(XEN) masked ExtINT on CPU#15
(XEN) Total of 16 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN) IO-APIC (apicid-pin) 8-0, 8-16, 8-17, 8-18, 8-19, 8-20, 8-21, 8-22, 8-23, 0-0, 0-1, 0-2, 0-3, 0-4, 0-5, 0-6, 0-7, 0-8, 0-9, 0-10, 0-11, 0-12, 0-13, 0-14, 0-15, 0-16, 0-17, 0-18, 0-19, 0-20, 0-21, 0-22, 0-23 not connected.
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #8 registers: 24.
(XEN) number of IO-APIC #0 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #8......
(XEN) .... register #00: 08000000
(XEN) ....... : physical APIC id: 08
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00170020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 0
(XEN) ....... : IO APIC version: 0020
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 000 00 0 0 0 0 0 0 0 30
(XEN) 02 000 00 0 0 0 0 0 0 0 F0
(XEN) 03 000 00 0 0 0 0 0 0 0 38
(XEN) 04 000 00 0 0 0 0 0 0 0 F1
(XEN) 05 000 00 0 0 0 0 0 0 0 40
(XEN) 06 000 00 0 0 0 0 0 0 0 48
(XEN) 07 000 00 0 0 0 0 0 0 0 50
(XEN) 08 000 00 0 0 0 0 0 0 0 58
(XEN) 09 000 00 1 1 0 0 0 0 0 60
(XEN) 0a 000 00 0 0 0 0 0 0 0 68
(XEN) 0b 000 00 0 0 0 0 0 0 0 70
(XEN) 0c 000 00 0 0 0 0 0 0 0 78
(XEN) 0d 000 00 0 0 0 0 0 0 0 88
(XEN) 0e 000 00 0 0 0 0 0 0 0 90
(XEN) 0f 000 00 0 0 0 0 0 0 0 98
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) IO APIC #0......
(XEN) .... register #00: 00000000
(XEN) ....... : physical APIC id: 00
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00170020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 0
(XEN) ....... : IO APIC version: 0020
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... register #03: 00000001
(XEN) ....... : Boot DT : 1
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 000 00 1 0 0 0 0 0 0 00
(XEN) 02 000 00 1 0 0 0 0 0 0 00
(XEN) 03 000 00 1 0 0 0 0 0 0 00
(XEN) 04 000 00 1 0 0 0 0 0 0 00
(XEN) 05 000 00 1 0 0 0 0 0 0 00
(XEN) 06 000 00 1 0 0 0 0 0 0 00
(XEN) 07 000 00 1 0 0 0 0 0 0 00
(XEN) 08 000 00 1 0 0 0 0 0 0 00
(XEN) 09 000 00 1 0 0 0 0 0 0 00
(XEN) 0a 000 00 1 0 0 0 0 0 0 00
(XEN) 0b 000 00 1 0 0 0 0 0 0 00
(XEN) 0c 000 00 1 0 0 0 0 0 0 00
(XEN) 0d 000 00 1 0 0 0 0 0 0 00
(XEN) 0e 000 00 1 0 0 0 0 0 0 00
(XEN) 0f 000 00 1 0 0 0 0 0 0 00
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ48 -> 0:1
(XEN) IRQ56 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ64 -> 0:5
(XEN) IRQ72 -> 0:6
(XEN) IRQ80 -> 0:7
(XEN) IRQ88 -> 0:8
(XEN) IRQ96 -> 0:9
(XEN) IRQ104 -> 0:10
(XEN) IRQ112 -> 0:11
(XEN) IRQ120 -> 0:12
(XEN) IRQ136 -> 0:13
(XEN) IRQ144 -> 0:14
(XEN) IRQ152 -> 0:15
(XEN) .................................... done.
(XEN) Using local APIC timer interrupts.
(XEN) calibrating APIC timer ...
(XEN) ..... CPU clock speed is 2533.4659 MHz.
(XEN) ..... host bus clock speed is 133.3403 MHz.
(XEN) ..... bus_scale = 0x0000888D
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
�(XEN) Allocated console ring of 128 KiB.
(XEN) Brought up 16 CPUs
(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) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2861000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000180000000->0000000190000000 (65536 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff82861000
(XEN) Init. ramdisk: ffffffff82861000->ffffffff8c05ac00
(XEN) Phys-Mach map: ffffffff8c05b000->ffffffff8c15b000
(XEN) Start info: ffffffff8c15b000->ffffffff8c15b4b4
(XEN) Page tables: ffffffff8c15c000->ffffffff8c1c1000
(XEN) Boot stack: ffffffff8c1c1000->ffffffff8c1c2000
(XEN) TOTAL: ffffffff80000000->ffffffff8c400000
(XEN) ENTRY ADDRESS: ffffffff81b7d200
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Scrubbing Free RAM: ....................................................................................................................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 176kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32.21-xenoprof-1 (root@kaan) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #1 SMP Wed Sep 22 16:02:23 PDT 2010
[ 0.000000] Command line: dummy=dummy root=/dev/mapper/system-dom0_0 ro earlyprintk=xen loglevel=10 debug acpi=force console=hvc0,115200n8
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] released 0 pages of unused memory
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 000000000009f400 (usable)
[ 0.000000] Xen: 000000000009f400 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000020000000 (usable)
[ 0.000000] Xen: 00000000df62f000 - 00000000df63c000 (ACPI data)
[ 0.000000] Xen: 00000000df63d000 - 00000000e4000000 (reserved)
[ 0.000000] Xen: 00000000fec00000 - 00000000fee10000 (reserved)
[ 0.000000] Xen: 00000000ff800000 - 0000000100000000 (reserved)
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] DMI 2.6 present.
[ 0.000000] last_pfn = 0x20000 max_arch_pfn = 0x400000000
[ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] init_memory_mapping: 0000000000000000-0000000020000000
[ 0.000000] 0000000000 - 0020000000 page 4k
[ 0.000000] kernel direct mapping tables up to 20000000 @ 100000-202000
[ 0.000000] RAMDISK: 02861000 - 0c05ac00
[ 0.000000] ACPI: RSDP 00000000000f4f00 00024 (v02 HP )
[ 0.000000] ACPI: XSDT 00000000df630040 000BC (v01 HP ProLiant 00000002 �? 0000162E)
[ 0.000000] ACPI: FACP 00000000df630140 000F4 (v03 HP ProLiant 00000002 �? 0000162E)
[ 0.000000] ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20090903/tbfadt-607)
[ 0.000000] ACPI Warning: Invalid length for Pm2ControlBlock: 32, using default 8 (20090903/tbfadt-607)
[ 0.000000] ACPI: DSDT 00000000df630240 02005 (v01 HP DSDT 00000001 INTL 20030228)
[ 0.000000] ACPI: FACS 00000000df62f100 00040
[ 0.000000] ACPI: SPCR 00000000df62f140 00050 (v01 HP SPCRRBSU 00000001 �? 0000162E)
[ 0.000000] ACPI: MCFG 00000000df62f1c0 0003C (v01 HP ProLiant 00000001 00000000)
[ 0.000000] ACPI: HPET 00000000df62f200 00038 (v01 HP ProLiant 00000002 �? 0000162E)
[ 0.000000] ACPI: FFFF 00000000df62f240 00064 (v02 HP ProLiant 00000002 �? 0000162E)
[ 0.000000] ACPI: SPMI 00000000df62f2c0 00040 (v05 HP ProLiant 00000001 �? 0000162E)
[ 0.000000] ACPI: ERST 00000000df62f300 001D0 (v01 HP ProLiant 00000001 �? 0000162E)
[ 0.000000] ACPI: APIC 00000000df62f500 0015E (v01 HP ProLiant 00000002 00000000)
[ 0.000000] ACPI: SRAT 00000000df62f680 00570 (v01 HP Proliant 00000001 �? 0000162E)
[ 0.000000] ACPI: FFFF 00000000df62fc00 00176 (v01 HP ProLiant 00000001 �? 0000162E)
[ 0.000000] ACPI: BERT 00000000df62fd80 00030 (v01 HP ProLiant 00000001 �? 0000162E)
[ 0.000000] ACPI: HEST 00000000df62fdc0 000BC (v01 HP ProLiant 00000001 �? 0000162E)
[ 0.000000] ACPI: XMAR 00000000df62fe80 00154 (v01 HP ProLiant 00000001 �? 0000162E)
[ 0.000000] ACPI: SSDT 00000000df632280 00125 (v03 HP CRSPCI0 00000002 HP 00000001)
[ 0.000000] ACPI: SSDT 00000000df6323c0 00255 (v03 HP riser1a 00000002 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000df632640 0025D (v03 HP riser2a 00000002 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000df6328c0 003BB (v01 HP pcc 00000001 INTL 20090625)
[ 0.000000] ACPI: SSDT 00000000df632c80 00377 (v01 HP pmab 00000001 INTL 20090625)
[ 0.000000] ACPI: SSDT 00000000df633000 022E4 (v01 INTEL PPM RCM 00000001 INTL 20061109)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] SRAT: PXM 0 -> APIC 0 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 1 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 2 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 3 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 4 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 5 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 6 -> Node 0
[ 0.000000] SRAT: PXM 0 -> APIC 7 -> Node 0
[ 0.000000] SRAT: PXM 1 -> APIC 16 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 17 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 18 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 19 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 20 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 21 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 22 -> Node 1
[ 0.000000] SRAT: PXM 1 -> APIC 23 -> Node 1
[ 0.000000] SRAT: Node 0 PXM 0 0-e0000000
[ 0.000000] SRAT: Node 0 PXM 0 100000000-1a0000000
[ 0.000000] SRAT: Node 1 PXM 1 1a0000000-320000000
[ 0.000000] NUMA: Using 29 for the hash shift.
[ 0.000000] Bootmem setup node 0 0000000000000000-0000000020000000
[ 0.000000] NODE_DATA [0000000000001000 - 0000000000004fff]
[ 0.000000] bootmap [0000000000008000 - 000000000000bfff] pages 4
[ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 0020000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [000c15c000 - 000c1c1000] XEN PAGETABLES ==> [000c15c000 - 000c1c1000]
[ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
[ 0.000000] #3 [0001000000 - 0002737520] TEXT DATA BSS ==> [0001000000 - 0002737520]
[ 0.000000] #4 [0002861000 - 000c05ac00] RAMDISK ==> [0002861000 - 000c05ac00]
[ 0.000000] #5 [000c05b000 - 000c15c000] XEN START INFO ==> [000c05b000 - 000c15c000]
[ 0.000000] #6 [0002738000 - 0002742180] BRK ==> [0002738000 - 0002742180]
[ 0.000000] #7 [0000100000 - 000019a000] PGTABLE ==> [0000100000 - 000019a000]
[ 0.000000] found SMP MP-table at [ffff8800000f4f80] f4f80
(XEN) mm.c:860:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry 8000000000100463 for l1e_owner=0, pg_owner=32753
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00100000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x00020000
[ 0.000000] On node 0 totalpages: 130975
[ 0.000000] DMA zone: 104 pages used for memmap
[ 0.000000] DMA zone: 157 pages reserved
[ 0.000000] DMA zone: 3738 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 3224 pages used for memmap
[ 0.000000] DMA32 zone: 123752 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x908
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x24] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x14] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x34] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x22] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x12] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x32] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x26] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x16] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x36] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x11] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x31] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x25] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x15] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x35] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x23] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x13] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x33] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x27] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x17] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x37] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-0
[ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec80000] gsi_base[24])
[ 0.000000] IOAPIC[1]: apic_id 0, version 0, address 0xfec80000, GSI 24-24
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 280
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 20000000 (gap: 20000000:bf62f000)
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.0.2-rc1-pre (preserve-AD) (dom0)
[ 0.000000] NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:1 nr_node_ids:2
[ 0.000000] PERCPU: Embedded 478 pages/cpu @ffff88000c267000 s1927064 r8192 d22632 u1957888
[ 0.000000] pcpu-alloc: s1927064 r8192 d22632 u1957888 alloc=478*4096
[ 0.000000] pcpu-alloc: [0] 0
[ 4.578704] trying to map vcpu_info 0 at ffff88000c272020, mfn 18c272, offset 32
[ 4.578710] cpu 0 using vcpu_info at ffff88000c272020
[ 4.578712] Xen: using vcpu_info placement
[ 4.578718] Built 1 zonelists in Node order, mobility grouping on. Total pages: 127490
[ 4.578721] Policy zone: DMA32
[ 4.578733] Kernel command line: dummy=dummy root=/dev/mapper/system-dom0_0 ro earlyprintk=xen loglevel=10 debug acpi=force console=hvc0,115200n8
[ 4.578787] PID hash table entries: 2048 (order: 2, 16384 bytes)
[ 4.579153] Initializing CPU#0
[ 4.588637] DMA: Placing 64MB software IO TLB between ffff88000d1ad000 - ffff8800111ad000
[ 4.588646] DMA: software IO TLB at phys 0xd1ad000 - 0x111ad000
[ 4.588649] xen_swiotlb_fixup: buf=ffff88000d1ad000 size=67108864
[ 4.609175] xen_swiotlb_fixup: buf=ffff88001120d000 size=32768
[ 4.666266] Memory: 260456k/524288k available (6123k kernel code, 388k absent, 263444k reserved, 3749k data, 2620k init)
[ 4.666308] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=2
[ 4.666440] Hierarchical RCU implementation.
[ 4.666475] NR_IRQS:4352 nr_irqs:512
[ 4.666593] xen: --> irq=0
[ 4.666602] xen: --> irq=1
[ 4.666609] xen: --> irq=2
[ 4.666616] xen: --> irq=3
[ 4.666622] xen: --> irq=4
[ 4.666629] xen: --> irq=5
[ 4.666635] xen: --> irq=6
[ 4.666642] xen: --> irq=7
[ 4.666648] xen: --> irq=8
[ 4.666655] xen: --> irq=9
[ 4.666662] xen: --> irq=10
[ 4.666668] xen: --> irq=11
[ 4.666675] xen: --> irq=12
[ 4.666681] xen: --> irq=13
[ 4.666688] xen: --> irq=14
[ 4.666694] xen: --> irq=15
[ 4.666708] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[ 4.666712] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 4.666716] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1
[ 4.666719] xen: registering gsi 9 triggering 0 polarity 0
[ 4.666723] xen_allocate_pirq: returning irq 9 for gsi 9
[ 4.666726] xen: --> irq=9
[ 4.666734] xen: acpi sci 9
[ 4.670209] Console: colour VGA+ 80x25
[ 4.670229] console [hvc0] enabled, bootconsole disabled
[ 4.670229] console [hvc0] enabled, bootconsole disabled
[ 4.670247] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[ 4.670252] ... MAX_LOCKDEP_SUBCLASSES: 8
[ 4.670255] ... MAX_LOCK_DEPTH: 48
[ 4.670258] ... MAX_LOCKDEP_KEYS: 8191
[ 4.670261] ... CLASSHASH_SIZE: 4096
[ 4.670265] ... MAX_LOCKDEP_ENTRIES: 16384
[ 4.670268] ... MAX_LOCKDEP_CHAINS: 32768
[ 4.670271] ... CHAINHASH_SIZE: 16384
[ 4.670275] memory used by lock dependency info: 6367 kB
[ 4.670279] per task-struct memory footprint: 2688 bytes
[ 4.671201] allocated 5242880 bytes of page_cgroup
[ 4.671206] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 4.671719] ODEBUG: 9 of 9 active objects replaced
[ 4.671803] Xen: using vcpuop timer interface
[ 4.671809] installing Xen timer for CPU 0
[ 4.671851] alloc irq_desc for 511 on node 0
[ 4.671858] alloc kstat_irqs on node 0
[ 4.671909] Detected 2533.496 MHz processor.
[ 4.671939] Calibrating delay loop (skipped), value calculated using timer frequency.. 5066.99 BogoMIPS (lpj=25334960)
[ 4.672025] Security Framework initialized
[ 4.672034] SELinux: Disabled at boot.
[ 4.672238] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 4.672413] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 4.672475] Mount-cache hash table entries: 256
[ 4.673609] Initializing cgroup subsys ns
[ 4.673616] Initializing cgroup subsys cpuacct
[ 4.673631] Initializing cgroup subsys memory
[ 4.673710] Initializing cgroup subsys devices
[ 4.673716] Initializing cgroup subsys freezer
[ 4.673721] Initializing cgroup subsys net_cls
[ 4.673852] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 4.673857] CPU: L2 cache: 256K
[ 4.673860] CPU: L3 cache: 8192K
[ 4.673866] CPU 0/0x0 -> Node 0
[ 4.673870] CPU: Unsupported number of siblings 16
[ 4.673875] mce: CPU supports 9 MCE banks
[ 4.673905] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only.
[ 4.673921] SMP alternatives: switching to UP code
[ 4.708072] Freeing SMP alternatives: 39k freed
[ 4.708094] ACPI: Core revision 20090903
[ 4.734655] ftrace: converting mcount calls to 0f 1f 44 00 00
[ 4.734663] ftrace: allocating 24198 entries in 95 pages
[ 4.741305] alloc irq_desc for 510 on node 0
[ 4.741312] alloc kstat_irqs on node 0
[ 4.741330] alloc irq_desc for 509 on node 0
[ 4.741355] alloc kstat_irqs on node 0
[ 4.741370] alloc irq_desc for 508 on node 0
[ 4.741376] alloc kstat_irqs on node 0
[ 4.741391] alloc irq_desc for 507 on node 0
[ 4.741397] alloc kstat_irqs on node 0
[ 4.741917] Brought up 1 CPUs
[ 4.741978] CPU0 attaching NULL sched-domain.
[ 4.742596] devtmpfs: initialized
[ 4.744998] Grant table initialized
[ 4.745003] regulator: core version 0.5
[ 4.745063] Time: 23:16:29 Date: 09/27/10
[ 4.745326] NET: Registered protocol family 16
[ 4.745760] alloc irq_desc for 506 on node 0
[ 4.745767] alloc kstat_irqs on node 0
[ 4.747030] ACPI: bus type pci registered
[ 4.747325] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 63
[ 4.747331] PCI: MCFG area at e0000000 reserved in E820
[ 4.757333] PCI: Using MMCONFIG at e0000000 - e3ffffff
[ 4.757358] PCI: Using configuration type 1 for base access
[ 4.757365] PCI: HP ProLiant DL380 detected, enabling pci=bfsort.
[ 4.766263] bio: create slab <bio-0> at 0
[ 4.771661] ERROR: Unable to locate IOAPIC for GSI 9
[ 4.771736] ACPI: EC: Look up EC in DSDT
[ 4.776516] ACPI Error: Field [CDW3] at 96 exceeds Buffer [NULL] size 64 (bits) (20090903/dsopcode-596)
[ 4.776538] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_._OSC] (Node ffff88001fd171a0), AE_AML_BUFFER_LIMIT
[ 4.790572] ACPI: Interpreter enabled
[ 4.790577] ACPI: (supports S0 S4 S5)
[ 4.790699] ACPI: Using IOAPIC for interrupt routing
[ 4.825363] ACPI: No dock devices found.
[ 4.825451] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 4.825886] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 4.825897] pci 0000:00:00.0: PME# disabled
[ 4.826151] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 4.826161] pci 0000:00:01.0: PME# disabled
[ 4.826427] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
[ 4.826438] pci 0000:00:02.0: PME# disabled
[ 4.826689] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 4.826699] pci 0000:00:03.0: PME# disabled
[ 4.826944] pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
[ 4.826955] pci 0000:00:04.0: PME# disabled
[ 4.827198] pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
[ 4.827209] pci 0000:00:05.0: PME# disabled
[ 4.827471] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
[ 4.827482] pci 0000:00:06.0: PME# disabled
[ 4.827725] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[ 4.827736] pci 0000:00:07.0: PME# disabled
[ 4.827990] pci 0000:00:08.0: PME# supported from D0 D3hot D3cold
[ 4.828000] pci 0000:00:08.0: PME# disabled
[ 4.828244] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
[ 4.828254] pci 0000:00:09.0: PME# disabled
[ 4.828518] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
[ 4.828529] pci 0000:00:0a.0: PME# disabled
[ 4.831688] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 4.831700] pci 0000:00:1c.0: PME# disabled
[ 4.831937] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 4.831948] pci 0000:00:1c.2: PME# disabled
[ 4.832156] pci 0000:00:1d.0: reg 20 io port: [0x1000-0x101f]
[ 4.832420] pci 0000:00:1d.1: reg 20 io port: [0x1020-0x103f]
[ 4.832662] pci 0000:00:1d.2: reg 20 io port: [0x1040-0x105f]
[ 4.832917] pci 0000:00:1d.3: reg 20 io port: [0x1060-0x107f]
[ 4.833176] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf1df0000-0xf1df03ff]
[ 4.833356] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 4.833367] pci 0000:00:1d.7: PME# disabled
[ 4.833933] pci 0000:04:00.0: reg 10 64bit mmio: [0xfb400000-0xfb7fffff]
[ 4.833963] pci 0000:04:00.0: reg 18 64bit mmio: [0xfb3f0000-0xfb3f0fff]
[ 4.833980] pci 0000:04:00.0: reg 20 io port: [0x4000-0x40ff]
[ 4.834010] pci 0000:04:00.0: reg 30 32bit mmio pref: [0x000000-0x07ffff]
[ 4.834088] pci 0000:04:00.0: supports D1
[ 4.834091] pci 0000:04:00.0: PME# supported from D0
[ 4.834102] pci 0000:04:00.0: PME# disabled
[ 4.851923] pci 0000:00:01.0: bridge io port: [0x4000-0x4fff]
[ 4.851935] pci 0000:00:01.0: bridge 32bit mmio: [0xfb300000-0xfb7fffff]
[ 4.852850] pci 0000:0d:00.0: reg 10 io port: [0x7000-0x70ff]
[ 4.852879] pci 0000:0d:00.0: reg 14 64bit mmio: [0xfbff0000-0xfbff3fff]
[ 4.852909] pci 0000:0d:00.0: reg 1c 64bit mmio: [0xfbe00000-0xfbefffff]
[ 4.852938] pci 0000:0d:00.0: reg 30 32bit mmio pref: [0x000000-0x03ffff]
[ 4.853132] pci 0000:0d:00.1: reg 10 io port: [0x7400-0x74ff]
[ 4.853161] pci 0000:0d:00.1: reg 14 64bit mmio: [0xfbdf0000-0xfbdf3fff]
[ 4.853191] pci 0000:0d:00.1: reg 1c 64bit mmio: [0xfbc00000-0xfbcfffff]
[ 4.853220] pci 0000:0d:00.1: reg 30 32bit mmio pref: [0x000000-0x03ffff]
[ 4.871902] pci 0000:00:07.0: bridge io port: [0x7000-0x7fff]
[ 4.871914] pci 0000:00:07.0: bridge 32bit mmio: [0xfbc00000-0xfbffffff]
[ 4.872219] pci 0000:07:00.0: reg 18 io port: [0x5000-0x50ff]
[ 4.872236] pci 0000:07:00.0: reg 1c io port: [0x5400-0x54ff]
[ 4.872265] pci 0000:07:00.0: reg 20 64bit mmio: [0xfbbf0000-0xfbbf7fff]
[ 4.872500] pci 0000:07:00.1: reg 18 io port: [0x5800-0x58ff]
[ 4.872517] pci 0000:07:00.1: reg 1c io port: [0x5c00-0x5cff]
[ 4.872546] pci 0000:07:00.1: reg 20 64bit mmio: [0xfbbe0000-0xfbbe7fff]
[ 4.872799] pci 0000:07:00.2: reg 18 io port: [0x6000-0x60ff]
[ 4.872816] pci 0000:07:00.2: reg 1c io port: [0x6400-0x64ff]
[ 4.872847] pci 0000:07:00.2: reg 20 64[ 5.457665] DMA-API: preallocated 32768 debug entries
[ 5.457672] DMA-API: debugging enabled by kernel config
[ 5.457678] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 5.457684] DMA: Placing 64MB software IO TLB between ffff88000d1ad000 - ffff8800111ad000
[ 5.457689] DMA: software IO TLB at phys 0xd1ad000 - 0x111ad000
[ 5.459690] audit: initializing netlink socket (disabled)
[ 5.459757] type=2000 audit(1285629390.411:1): initialized
[ 5.469619] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 5.485696] VFS: Disk quotas dquot_6.5.2
[ 5.486028] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 5.490662] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 5.492367] fuse init (API version 7.13)
[ 5.492813] msgmni has been set to 812
[ 5.493867] cryptomgr_test used greatest stack depth: 5896 bytes left
[ 5.494486] alg: No test for stdrng (krng)
[ 5.494731] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 5.494751] io scheduler noop registered
[ 5.494755] io scheduler anticipatory registered
[ 5.494760] io scheduler deadline registered
[ 5.495135] io scheduler cfq registered (default)
[ 5.497182] alloc irq_desc for 504 on node 0
[ 5.497190] alloc kstat_irqs on node 0
[ 5.497240] pcieport 0000:00:01.0: setting latency timer to 64
[ 5.497771] alloc irq_desc for 503 on node 0
[ 5.497778] alloc kstat_irqs on node 0
[ 5.497818] pcieport 0000:00:02.0: setting latency timer to 64
[ 5.498280] alloc irq_desc for 502 on node 0
[ 5.498287] alloc kstat_irqs on node 0
[ 5.498345] pcieport 0000:00:03.0: setting latency timer to 64
[ 5.498791] alloc irq_desc for 501 on node 0
[ 5.498797] alloc kstat_irqs on node 0
[ 5.498836] pcieport 0000:00:04.0: setting latency timer to 64
[ 5.499292] alloc irq_desc for 500 on node 0
[ 5.499298] alloc kstat_irqs on node 0
[ 5.499356] pcieport 0000:00:05.0: setting latency timer to 64
[ 5.499802] alloc irq_desc for 499 on node 0
[ 5.499808] alloc kstat_irqs on node 0
[ 5.499847] pcieport 0000:00:06.0: setting latency timer to 64
[ 5.500306] alloc irq_desc for 498 on node 0
[ 5.500313] alloc kstat_irqs on node 0
[ 5.500370] pcieport 0000:00:07.0: setting latency timer to 64
[ 5.500816] alloc irq_desc for 497 on node 0
[ 5.500823] alloc kstat_irqs on node 0
[ 5.500861] pcieport 0000:00:08.0: setting latency timer to 64
[ 5.501320] alloc irq_desc for 496 on node 0
[ 5.501326] alloc kstat_irqs on node 0
[ 5.501365] pcieport 0000:00:09.0: setting latency timer to 64
[ 5.501837] alloc irq_desc for 495 on node 0
[ 5.501843] alloc kstat_irqs on node 0
[ 5.501883] pcieport 0000:00:0a.0: setting latency timer to 64
[ 5.502354] alloc irq_desc for 494 on node 0
[ 5.502361] alloc kstat_irqs on node 0
[ 5.502406] pcieport 0000:00:1c.0: setting latency timer to 64
[ 5.502814] alloc irq_desc for 493 on node 0
[ 5.502820] alloc kstat_irqs on node 0
[ 5.502864] pcieport 0000:00:1c.2: setting latency timer to 64
[ 5.503316] aer 0000:00:01.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503387] aer 0000:00:02.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503428] aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503469] aer 0000:00:04.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503509] aer 0000:00:05.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503550] aer 0000:00:06.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503590] aer 0000:00:07.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503630] aer 0000:00:08.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503671] aer 0000:00:09.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503711] aer 0000:00:0a.0:pcie02: AER service couldn't init device: no _OSC support
[ 5.503776] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 5.504003] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 5.504008] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 5.509034] pci-stub: invalid id string ""
[ 5.509810] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 5.509850] ACPI: Power Button [PWRF]
[ 5.552474] thermal LNXTHERM:01: registered as thermal_zone0
[ 5.552528] ACPI: Thermal Zone [THM0] (8 C)
[ 5.556565] registering netback
[ 5.556760] alloc irq_desc for 492 on node 0
[ 5.556767] alloc kstat_irqs on node 0
[ 5.563955] alloc irq_desc for 491 on node 0
[ 5.563963] alloc kstat_irqs on node 0
[ 5.565467] hpet_acpi_add: no address or irqs in _CRS
[ 5.565651] Non-volatile memory driver v1.3
[ 5.565656] Linux agpgart interface v0.103
[ 5.565741] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 5.573054] brd: module loaded
[ 5.575956] loop: module loaded
[ 5.577098] Fixed MDIO Bus: probed
[ 5.577203] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009)
[ 5.577245] xen: registering gsi 16 triggering 0 polarity 1
[ 5.577250] xen_allocate_pirq: returning irq 16 for gsi 16
[ 5.577254] xen: --> irq=16
[ 5.577259] Already setup the GSI :16
[ 5.577263] bnx2 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 5.577279] bnx2 0000:02:00.0: setting latency timer to 64
[ 5.577704] bnx2 0000:02:00.0: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.577711] bnx2 0000:02:00.0: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.579121] eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f4000000, IRQ 16, node addr 00:24:81:e8:a5:1c
[ 5.579182] xen: registering gsi 17 triggering 0 polarity 1
[ 5.579192] alloc irq_desc for 17 on node 0
[ 5.579198] alloc kstat_irqs on node 0
[ 5.579207] xen: --> irq=17
[ 5.579215] bnx2 0000:02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 5.579230] bnx2 0000:02:00.1: setting latency timer to 64
[ 5.579594] bnx2 0000:02:00.1: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.579601] bnx2 0000:02:00.1: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.581073] eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f2000000, IRQ 17, node addr 00:24:81:e8:a5:1e
[ 5.581151] xen: registering gsi 18 triggering 0 polarity 1
[ 5.581161] alloc irq_desc for 18 on node 0
[ 5.581167] alloc kstat_irqs on node 0
[ 5.581176] xen: --> irq=18
[ 5.581182] bnx2 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 5.581197] bnx2 0000:03:00.0: setting latency timer to 64
[ 5.581571] bnx2 0000:03:00.0: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.581577] bnx2 0000:03:00.0: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.583071] eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f8000000, IRQ 18, node addr 00:24:81:e8:a5:20
[ 5.583131] xen: registering gsi 19 triggering 0 polarity 1
[ 5.583141] alloc irq_desc for 19 on node 0
[ 5.583147] alloc kstat_irqs on node 0
[ 5.583156] xen: --> irq=19
[ 5.583162] bnx2 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 5.583177] bnx2 0000:03:00.1: setting latency timer to 64
[ 5.583531] bnx2 0000:03:00.1: firmware: using built-in firmware bnx2/bnx2-mips-09-5.0.0.j3.fw
[ 5.583538] bnx2 0000:03:00.1: firmware: using built-in firmware bnx2/bnx2-rv2p-09-5.0.0.j3.fw
[ 5.585112] eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f6000000, IRQ 19, node addr 00:24:81:e8:a5:22
[ 5.585704] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.585818] xen: registering gsi 20 triggering 0 polarity 1
[ 5.585827] alloc irq_desc for 20 on node 0
[ 5.585833] alloc kstat_irqs on node 0
[ 5.585842] xen: --> irq=20
[ 5.585848] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 5.585887] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 5.585895] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 5.586723] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[ 5.586914] ehci_hcd 0000:00:1d.7: debug port 1
[ 5.590814] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 5.590874] ehci_hcd 0000:00:1d.7: irq 20, io mem 0xf1df0000
[ 5.607555] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 5.607809] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.607815] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.607820] usb usb1: Product: EHCI Host Controller
[ 5.607824] usb usb1: Manufacturer: Linux 2.6.32.21-xenoprof-1 ehci_hcd
[ 5.607828] usb usb1: SerialNumber: 0000:00:1d.7
[ 5.608374] usb usb1: configuration #1 chosen from 1 choice
[ 5.608642] hub 1-0:1.0: USB hub found
[ 5.608719] hub 1-0:1.0: 8 ports detected
[ 5.609353] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 5.609549] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.609778] xen: registering gsi 20 triggering 0 polarity 1
[ 5.609783] xen_allocate_pirq: returning irq 20 for gsi 20
[ 5.609787] xen: --> irq=20
[ 5.609791] Already setup the GSI :20
[ 5.609795] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 5.609815] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 5.609823] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 5.610019] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 5.610077] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00001000
[ 5.610273] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.610278] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.610283] usb usb2: Product: UHCI Host Controller
[ 5.610286] usb usb2: Manufacturer: Linux 2.6.32.21-xenoprof-1 uhci_hcd
[ 5.610291] usb usb2: SerialNumber: 0000:00:1d.0
[ 5.610617] usb usb2: configuration #1 chosen from 1 choice
[ 5.610748] hub 2-0:1.0: USB hub found
[ 5.610826] hub 2-0:1.0: 2 ports detected
[ 5.611169] xen: registering gsi 23 triggering 0 polarity 1
[ 5.611183] alloc irq_desc for 23 on node 0
[ 5.611189] alloc kstat_irqs on node 0
[ 5.611199] xen: --> irq=23
[ 5.611205] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 23 (level, low) -> IRQ 23
[ 5.611226] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 5.611234] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 5.611450] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[ 5.611537] uhci_hcd 0000:00:1d.1: irq 23, io base 0x00001020
[ 5.611764] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.611[ 6.257976] usb 6-1: new full speed USB device using uhci_hcd and address 2
[ 6.406827] Initializing USB Mass Storage driver...
[ 6.416764] usb 6-1: New USB device found, idVendor=03f0, idProduct=1027
[ 6.416770] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.416776] usb 6-1: Product: Virtual Keyboard
[ 6.416779] usb 6-1: Manufacturer: HP
[ 6.417060] usb 6-1: configuration #1 chosen from 1 choice
[ 6.430905] scsi0 : SCSI emulation for USB Mass Storage devices
[ 6.449342] usbcore: registered new interface driver usb-storage
[ 6.449566] USB Mass Storage support registered.
[ 6.449621] usb-storage: device found at 2
[ 6.449625] usb-storage: waiting for device to settle before scanning
[ 6.534699] HP CISS Driver (v 3.6.20)
[ 6.559523] xen: registering gsi 28 triggering 0 polarity 1
[ 6.559535] alloc irq_desc for 28 on node 0
[ 6.559542] alloc kstat_irqs on node 0
[ 6.559553] xen: --> irq=28
[ 6.559563] cciss 0000:04:00.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
[ 6.559765] alloc irq_desc for 490 on node 0
[ 6.559772] alloc kstat_irqs on node 0
[ 6.559850] alloc irq_desc for 489 on node 0
[ 6.559856] alloc kstat_irqs on node 0
[ 6.559927] alloc irq_desc for 488 on node 0
[ 6.559933] alloc kstat_irqs on node 0
[ 6.560010] alloc irq_desc for 487 on node 0
[ 6.560016] alloc kstat_irqs on node 0
[ 6.567937] IRQ 488/cciss0: IRQF_DISABLED is not guaranteed on shared IRQs
[ 6.567999] cciss0: <0x323a> at PCI 0000:04:00.0 IRQ 488 using DAC
[ 6.587793] cciss/c0d0: p1 p2 < p5 >
[ 6.619475] modprobe used greatest stack depth: 3520 bytes left
[ 6.651387] usbcore: registered new interface driver hiddev
[ 6.657196] input: HP Virtual Keyboard as /devices/pci0000:00/0000:00:1e.0/0000:01:04.4/usb6/6-1/6-1:1.0/input/input1
[ 6.658386] generic-usb 0003:03F0:1027.0001: input,hidraw0: USB HID v1.01 Keyboard [HP Virtual Keyboard] on usb-0000:01:04.4-1/input0
[ 6.663558] input: HP Virtual Keyboard as /devices/pci0000:00/0000:00:1e.0/0000:01:04.4/usb6/6-1/6-1:1.1/input/input2
[ 6.664270] generic-usb 0003:03F0:1027.0002: input,hidraw1: USB HID v1.01 Mouse [HP Virtual Keyboard] on usb-0000:01:04.4-1/input1
[ 6.664436] usbcore: registered new interface driver usbhid
[ 6.664668] usbhid: v2.6:USB HID core driver
[ 6.697978] usb 5-2: new low speed USB device using uhci_hcd and address 2
[ 6.882315] usb 5-2: New USB device found, idVendor=0624, idProduct=0422
[ 6.882322] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.882328] usb 5-2: Product: Avocent USBIAC
[ 6.882331] usb 5-2: Manufacturer: Avocent
[ 6.882596] usb 5-2: configuration #1 chosen from 1 choice
[ 6.918069] input: Avocent Avocent USBIAC as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/input/input3
[ 6.918366] generic-usb 0003:0624:0422.0003: input,hidraw2: USB HID v1.10 Keyboard [Avocent Avocent USBIAC] on usb-0000:00:1d.3-2/input0
[ 6.949924] input: Avocent Avocent USBIAC as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/input/input4
[ 6.950357] generic-usb 0003:0624:0422.0004: input,hidraw3: USB HID v1.10 Mouse [Avocent Avocent USBIAC] on usb-0000:00:1d.3-2/input1
[ 7.647856] kjournald starting. Commit interval 5 seconds
[ 7.648102] EXT3-fs: mounted filesystem with ordered data mode.
[ 8.556908] hostname used greatest stack depth: 3360 bytes left
[ 8.605840] hwclock used greatest stack depth: 2880 bytes left
init: ureadahead main process (412) terminated with status 5
[ 8.692450] plymouthd used greatest stack depth: 2032 bytes left
[ 11.667704] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 11.697690] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 11.743536] sd 0:0:0:0: [sda] Assuming drive cache: write through
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
e2fsck 1.41.11 (14-Mar-2010)
/dev/mapper/system-dom0_0: clean, 62945/203600 files, 661444/814080 blocks
/dev/mapper/system-common: clean, 188/101712 files, 22748/406528 blocks
init: ureadahead-other main process (984) terminated with status 4
init: ureadahead-other main process (998) terminated with status 4
* Enable login on console [ OK ]
* Config osa partitions
...done.
* Check for hostname changes... [ OK ]
...done.
* Setting sensors limits No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
[ OK ]
* Initializing random number generator... [ OK ]
...done.
* Setting up X server socket directory /tmp/.X11-unix... [ OK ]
* Setting up ICE socket directory /tmp/.ICE-unix... [ OK ]
Starting OpenLDAP: slapd.
* Exporting directories for NFS kernel daemon... [ OK ]
* Starting NFS kernel daemon [ OK ]
* Starting internet superserver inetd [ OK ]
Starting openntpd: * Starting Postfix Mail Transport Agent postfix [ OK ]
*
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 3:16 ` Bruce Edge
@ 2010-09-28 3:26 ` Jiang, Yunhong
2010-09-28 4:45 ` Bruce Edge
0 siblings, 1 reply; 42+ messages in thread
From: Jiang, Yunhong @ 2010-09-28 3:26 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk
[-- Attachment #1.1: Type: text/plain, Size: 15129 bytes --]
"xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
Thanks
--jyh
From: Bruce Edge [mailto:bruce.edge@gmail.com]
Sent: Tuesday, September 28, 2010 11:16 AM
To: Jiang, Yunhong
Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
Yes, there is 1 quad port card is this sytem:
07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
Also is it possible to share the xen output?
I attached the dom0 boot output. Let me know if you wanted something else.
Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
[ 1817.684097] ------------[ cut here ]------------
[ 1817.684113] WARNING: at kernel/lockdep.c:2323 trace_hardirqs_on_caller+0x12f/0x190()
[ 1817.684119] Hardware name: ProLiant DL380 G6
[ 1817.684122] Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage
[ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1
[ 1817.684195] Call Trace:
[ 1817.684197] <IRQ> [<ffffffff810aa18f>] ? trace_hardirqs_on_caller+0x12f/0x190
[ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
[ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40
[ 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20
[ 1817.684229] [<ffffffff810aa18f>] trace_hardirqs_on_caller+0x12f/0x190
[ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10
[ 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40
[ 1817.684266] [<ffffffff813c4fc5>] add_to_net_schedule_list_tail+0x85/0xd0
[ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160
[ 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180
[ 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170
[ 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
[ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
[ 1817.684304] [<ffffffff8101647e>] xen_do_hypervisor_callback+0x1e/0x30
[ 1817.684308] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1817.684319] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1817.684325] [<ffffffff813bce54>] ? xb_write+0x1e4/0x290
[ 1817.684330] [<ffffffff813bd8ca>] ? xs_talkv+0x6a/0x1f0
[ 1817.684336] [<ffffffff813bd8d8>] ? xs_talkv+0x78/0x1f0
[ 1817.684341] [<ffffffff813bdbcd>] ? xs_single+0x4d/0x60
[ 1817.684346] [<ffffffff813be502>] ? xenbus_read+0x52/0x80
[ 1817.684352] [<ffffffff813c87fc>] ? frontend_changed+0x48c/0x770
[ 1817.684358] [<ffffffff813bf76d>] ? xenbus_otherend_changed+0xdd/0x1b0
[ 1817.684365] [<ffffffff8101122f>] ? xen_restore_fl_direct_end+0x0/0x1
[ 1817.684371] [<ffffffff810ac830>] ? lock_release+0xb0/0x230
[ 1817.684376] [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20
[ 1817.684382] [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160
[ 1817.684389] [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40
[ 1817.684394] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160
[ 1817.684400] [<ffffffff81093086>] ? kthread+0x96/0xb0
[ 1817.684405] [<ffffffff8101632a>] ? child_rip+0xa/0x20
[ 1817.684410] [<ffffffff81015c90>] ? restore_args+0x0/0x30
[ 1817.684415] [<ffffffff81016320>] ? child_rip+0x0/0x20
-Bruce
Thanks
--jyh
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com>
>[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com>] On Behalf Of Bruce Edge
>Sent: Tuesday, September 28, 2010 7:54 AM
>To: Konrad Rzeszutek Wilk
>Cc: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
>On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
>>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
>>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>>> >
>>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>>> > > One of our developers who is working on a tachyon driver is
>>> > > complaining that the pvops domU kernel is not working for these MSI
>>> > > interrupts.
>>> > > This is using the current head of xen/2.6.32.x on both a single
>>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
>>> > >
>>> > > Here are his comments:
>>> > >
>>> > > - the driver has no problem to enable msi interrupt and request the
>>> > > interrupt through kernel functions pci_enable_msi & request_irq
>>> >
>>> > What shows up in the Xen console when you send the 'q' key? Does it
>>> > show that the vector is assigned to the appropiate guest?
>>>
>>> The Xen console q key shows that the domU is assigned:
>>>
>>> (XEN) Interrupts { 32, 41-42, 47 }
>>
>> Aha!
>>
>>>
>>> but the domU thinks it has:
>>>
>>> 124/125/126/127
>>>
>>> Is there some mapping that's taking place, or is this plain wrong?
>>
>> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
>> setup as IRQ numbers in the DomU guest. You should have seen
>>
>> 32:
>> 41:
>> 42:
>> 47:
>> in you /proc/interrupts on your DomU guest.
>>
>> I wonder what broke - can you use
>git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
>> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
>
>Please forgive the git ignorance.
>
>Is this the right syntax?
>
>git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32>
>linux-2.6.32-pv-pcifront
>
>Initialized empty Git repository in
>/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
>fatal: The remote end hung up unexpectedly
>
>Or:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
>
>Initialized empty Git repository in
>/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
>remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
>remote: fatal: Failed to traverse parents of commit
>979e121cb348add17ed8171bf447b27a3a9d1be3
>remote: aborting due to possible repository corruption on the remote side.
>fatal: early EOF
>fatal: index-pack failed
>
>>
>> It has the latest pcifront driver but without the PVonHVM enhancments
>> so we can try to eliminate the PvONHVM logic out of the picture.
>>
>>>
>>> >
>>> > > - the interrupt does happen. But the interrupt service routine of
>>> > > tachyon driver doesn't detect any interrupt status related to this
>>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
>>> > > there are high count of tachyon interrupt in /proc/interrupts
>>> >
>>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
>>> > in the MMIO BAR?
>>> >
>>>
>>> The driver would check the appropriate register (tachyon registers) in
>>> the MMIO to determine the source of interrupts.
>>
>> OK, so that isn't it. Is there anything at these vectors:
>> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
>> an inkling what device this is set for.
>
>When I run a distro kernel in hvm mode, I get the expected irq mappings:
>
>'i' - Note 66 - 69
>(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:127(----),
>(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:126(----),
>(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:125(----),
>(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:124(----)
>
>
>'q'
>(XEN) Interrupts { 32, 41-42, 47, 124-127 }
>
>
>The same data with pv-ops kernel shows:
>
>'i'
>IRQ numbers stop at 65, no 66 - 69 present:
>
>(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=0:289(----),
>(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
>type=PCI-MSI status=00000002 mapped, unbound
>(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=0:287(----),
>(XEN) IO-APIC interrupt information:
>
>'q'
>(XEN) Interrupts { 32, 41-42, 47 }
>
>>
>>>
>>> > >
>>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
>>> > >
>124: 760415 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>125: 762234 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>126: 764180 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>127: 764164 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> >
>>> > Can you provide the full dmesg output?
>>>
>>> Attached.
>>>
>>> Some possibly related messages on dom0 console:
>>>
>>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
>>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
>>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
>>> [ 1882.269834] xen: --> irq=32
>>> [ 1882.269841] Already setup the GSI :32
>>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
>>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
>>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>
>> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
>> to find out what is at the configuration space. You could enable
>> it using the permissive attribute.
>>
>>> [ 1882.270465] 1) see permissive attribute in sysfs
>>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.270615] alloc irq_desc for 478 on node 0
>>> [ 1882.270625] alloc kstat_irqs on node 0
>>
>> So for 478: what do you see? xen-pciback I presume?
>>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
>>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
>>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
>>> [ 1882.348445] xen: --> irq=42
>>> [ 1882.348472] Already setup the GSI :42
>>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
>>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
>>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>> [ 1882.349066] 1) see permissive attribute in sysfs
>>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.349205] alloc irq_desc for 477 on node 0
>>> [ 1882.349215] alloc kstat_irqs on node 0
>>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
>>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
>>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
>>> [ 1882.402916] xen: --> irq=47
>>> [ 1882.402921] Already setup the GSI :47
>>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
>>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
>>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>> [ 1882.403282] 1) see permissive attribute in sysfs
>>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.403380] alloc irq_desc for 476 on node 0
>>> [ 1882.403386] alloc kstat_irqs on node 0
>>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
>>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
>>> fault addr e6f80000, iommu reg = ffff82c3fff57000
>>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
>>> (XEN) root_entry = ffff83019ff70000
>>> (XEN) root_entry[7] = 19cf52001
>>> (XEN) context = ffff83019cf52000
>>> (XEN) context[0] = 102_706dc005
>>> (XEN) l4 = ffff8300706dc000
>>> (XEN) l4_index = 0
>>> (XEN) l4[0] = 706db003
>>> (XEN) l3 = ffff8300706db000
>>> (XEN) l3_index = 3
>>> (XEN) l3[3] = 702b6003
>>> (XEN) l2 = ffff8300702b6000
>>> (XEN) l2_index = 137
>>> (XEN) l2[137] = 0
>>> (XEN) l2[137] not present
>>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
>>
>> That is not good. What changed from your earlier emails that this was triggered?
>
>Nothing
>> Or was it triggered all along?
>
>Yes, I just included it for completeness
>
>> What happens if you run the system without the iommu enabled?
>
>Haven't tried yet. Will check that next.
>
>-Bruce
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
>http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 29159 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 3:26 ` Jiang, Yunhong
@ 2010-09-28 4:45 ` Bruce Edge
2010-09-28 16:08 ` Lin, Ray
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-09-28 4:45 UTC (permalink / raw)
To: Jiang, Yunhong; +Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk
[-- Attachment #1.1: Type: text/plain, Size: 15428 bytes --]
On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com>wrote:
> "xm dmesg" should gives xen's boot log, and sometimes it contain some
> helpful information, I think, especially loglvl and guest_loglvl is set to
> all.
>
>
I looked at the xm dmesg output and there's nothing more than what I already
provided, aside from a bunch of commands from me poking at it.
-Bruce
>
>
> Thanks
>
> --jyh
>
>
>
> *From:* Bruce Edge [mailto:bruce.edge@gmail.com]
> *Sent:* Tuesday, September 28, 2010 11:16 AM
> *To:* Jiang, Yunhong
> *Cc:* Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com
>
> *Subject:* Re: [Xen-devel] pv-ops domU not working with MSI interrupts on
> Nehalem
>
>
>
> On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com>
> wrote:
>
> Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
>
>
>
> Yes, there is 1 quad port card is this sytem:
>
>
>
> 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>
> 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>
> 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>
> 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>
>
>
>
>
> Also is it possible to share the xen output?
>
>
>
> I attached the dom0 boot output. Let me know if you wanted something else.
>
>
>
> Also, here's the dom0 console output upon starting the VM: This lockdep
> error started with the release of 2.6.32.21. Note that I'm running the same
> kernel for the domU and dom0.
>
>
>
> [ 1817.684097] ------------[ cut here ]------------
>
> [ 1817.684113] WARNING: at kernel/lockdep.c:2323
> trace_hardirqs_on_caller+0x12f/0x190()
>
> [ 1817.684119] Hardware name: ProLiant DL380 G6
>
> [ 1817.684122] Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs
> xen_gntdev fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback
> radeon ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core
> ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss
> usb_storage
>
> [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1
>
> [ 1817.684195] Call Trace:
>
> [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
> trace_hardirqs_on_caller+0x12f/0x190
>
> [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
>
> [ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40
>
> [ 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20
>
> [ 1817.684229] [<ffffffff810aa18f>] trace_hardirqs_on_caller+0x12f/0x190
>
> [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10
>
> [ 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40
>
> [ 1817.684266] [<ffffffff813c4fc5>]
> add_to_net_schedule_list_tail+0x85/0xd0
>
> [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160
>
> [ 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180
>
> [ 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170
>
> [ 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
>
> [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
>
> [ 1817.684304] [<ffffffff8101647e>] xen_do_hypervisor_callback+0x1e/0x30
>
> [ 1817.684308] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
>
> [ 1817.684319] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
>
> [ 1817.684325] [<ffffffff813bce54>] ? xb_write+0x1e4/0x290
>
> [ 1817.684330] [<ffffffff813bd8ca>] ? xs_talkv+0x6a/0x1f0
>
> [ 1817.684336] [<ffffffff813bd8d8>] ? xs_talkv+0x78/0x1f0
>
> [ 1817.684341] [<ffffffff813bdbcd>] ? xs_single+0x4d/0x60
>
> [ 1817.684346] [<ffffffff813be502>] ? xenbus_read+0x52/0x80
>
> [ 1817.684352] [<ffffffff813c87fc>] ? frontend_changed+0x48c/0x770
>
> [ 1817.684358] [<ffffffff813bf76d>] ? xenbus_otherend_changed+0xdd/0x1b0
>
> [ 1817.684365] [<ffffffff8101122f>] ? xen_restore_fl_direct_end+0x0/0x1
>
> [ 1817.684371] [<ffffffff810ac830>] ? lock_release+0xb0/0x230
>
> [ 1817.684376] [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20
>
> [ 1817.684382] [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160
>
> [ 1817.684389] [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40
>
> [ 1817.684394] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160
>
> [ 1817.684400] [<ffffffff81093086>] ? kthread+0x96/0xb0
>
> [ 1817.684405] [<ffffffff8101632a>] ? child_rip+0xa/0x20
>
> [ 1817.684410] [<ffffffff81015c90>] ? restore_args+0x0/0x30
>
> [ 1817.684415] [<ffffffff81016320>] ? child_rip+0x0/0x20
>
>
>
> -Bruce
>
>
>
>
>
>
> Thanks
> --jyh
>
>
> >-----Original Message-----
> >From: xen-devel-bounces@lists.xensource.com
> >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
> >Sent: Tuesday, September 28, 2010 7:54 AM
> >To: Konrad Rzeszutek Wilk
> >Cc: xen-devel@lists.xensource.com
>
> >Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on
> Nehalem
> >
>
> >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> ><konrad.wilk@oracle.com> wrote:
> >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> >>> <konrad.wilk@oracle.com> wrote:
> >>> >
> >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> >>> > > One of our developers who is working on a tachyon driver is
> >>> > > complaining that the pvops domU kernel is not working for these MSI
> >>> > > interrupts.
> >>> > > This is using the current head of xen/2.6.32.x on both a single
> >>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> >>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
> >>> > >
> >>> > > Here are his comments:
> >>> > >
> >>> > > - the driver has no problem to enable msi interrupt and request the
> >>> > > interrupt through kernel functions pci_enable_msi & request_irq
> >>> >
> >>> > What shows up in the Xen console when you send the 'q' key? Does it
> >>> > show that the vector is assigned to the appropiate guest?
> >>>
> >>> The Xen console q key shows that the domU is assigned:
> >>>
> >>> (XEN) Interrupts { 32, 41-42, 47 }
> >>
> >> Aha!
> >>
> >>>
> >>> but the domU thinks it has:
> >>>
> >>> 124/125/126/127
> >>>
> >>> Is there some mapping that's taking place, or is this plain wrong?
> >>
> >> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
> >> setup as IRQ numbers in the DomU guest. You should have seen
> >>
> >> 32:
> >> 41:
> >> 42:
> >> 47:
> >> in you /proc/interrupts on your DomU guest.
> >>
> >> I wonder what broke - can you use
> >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> >
> >Please forgive the git ignorance.
> >
> >Is this the right syntax?
> >
> >git clone git://
> git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32
> >linux-2.6.32-pv-pcifront
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
> >fatal: The remote end hung up unexpectedly
> >
> >Or:
> >
> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> >remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> >remote: fatal: Failed to traverse parents of commit
> >979e121cb348add17ed8171bf447b27a3a9d1be3
> >remote: aborting due to possible repository corruption on the remote side.
> >fatal: early EOF
> >fatal: index-pack failed
> >
> >>
> >> It has the latest pcifront driver but without the PVonHVM enhancments
> >> so we can try to eliminate the PvONHVM logic out of the picture.
> >>
> >>>
> >>> >
> >>> > > - the interrupt does happen. But the interrupt service routine of
> >>> > > tachyon driver doesn't detect any interrupt status related to this
> >>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
> >>> > > there are high count of tachyon interrupt in /proc/interrupts
> >>> >
> >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
> >>> > in the MMIO BAR?
> >>> >
> >>>
> >>> The driver would check the appropriate register (tachyon registers) in
> >>> the MMIO to determine the source of interrupts.
> >>
> >> OK, so that isn't it. Is there anything at these vectors:
> >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should
> give you
> >> an inkling what device this is set for.
> >
> >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> >
> >'i' - Note 66 - 69
> >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:127(----),
> >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:126(----),
> >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:125(----),
> >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:124(----)
> >
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> >
> >
> >The same data with pv-ops kernel shows:
> >
> >'i'
> >IRQ numbers stop at 65, no 66 - 69 present:
> >
> >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:289(----),
> >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> >type=PCI-MSI status=00000002 mapped, unbound
> >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:287(----),
> >(XEN) IO-APIC interrupt information:
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47 }
> >
> >>
> >>>
> >>> > >
> >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> >>> > >
> >124: 760415 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >125: 762234 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >126: 764180 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >127: 764164 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> >
> >>> > Can you provide the full dmesg output?
> >>>
> >>> Attached.
> >>>
> >>> Some possibly related messages on dom0 console:
> >>>
> >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
> >>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
> >>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
> >>> [ 1882.269834] xen: --> irq=32
> >>> [ 1882.269841] Already setup the GSI :32
> >>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low)
> -> IRQ 32
> >>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
> >>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>
> >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> >> to find out what is at the configuration space. You could enable
> >> it using the permissive attribute.
> >>
> >>> [ 1882.270465] 1) see permissive attribute in sysfs
> >>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> >>> [ 1882.270625] alloc kstat_irqs on node 0
> >>
> >> So for 478: what do you see? xen-pciback I presume?
> >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
> >>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
> >>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
> >>> [ 1882.348445] xen: --> irq=42
> >>> [ 1882.348472] Already setup the GSI :42
> >>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low)
> -> IRQ 42
> >>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
> >>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>> [ 1882.349066] 1) see permissive attribute in sysfs
> >>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> >>> [ 1882.349215] alloc kstat_irqs on node 0
> >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
> >>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
> >>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
> >>> [ 1882.402916] xen: --> irq=47
> >>> [ 1882.402921] Already setup the GSI :47
> >>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low)
> -> IRQ 47
> >>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
> >>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>> [ 1882.403282] 1) see permissive attribute in sysfs
> >>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> >>> [ 1882.403386] alloc kstat_irqs on node 0
> >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> >>> fault addr e6f80000, iommu reg = ffff82c3fff57000
> >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn =
> e6f80
> >>> (XEN) root_entry = ffff83019ff70000
> >>> (XEN) root_entry[7] = 19cf52001
> >>> (XEN) context = ffff83019cf52000
> >>> (XEN) context[0] = 102_706dc005
> >>> (XEN) l4 = ffff8300706dc000
> >>> (XEN) l4_index = 0
> >>> (XEN) l4[0] = 706db003
> >>> (XEN) l3 = ffff8300706db000
> >>> (XEN) l3_index = 3
> >>> (XEN) l3[3] = 702b6003
> >>> (XEN) l2 = ffff8300702b6000
> >>> (XEN) l2_index = 137
> >>> (XEN) l2[137] = 0
> >>> (XEN) l2[137] not present
> >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
> >>
> >> That is not good. What changed from your earlier emails that this was
> triggered?
> >
> >Nothing
> >> Or was it triggered all along?
> >
> >Yes, I just included it for completeness
> >
> >> What happens if you run the system without the iommu enabled?
> >
> >Haven't tried yet. Will check that next.
> >
> >-Bruce
> >
>
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com
> >http://lists.xensource.com/xen-devel
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 25959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-27 23:54 ` Bruce Edge
2010-09-28 1:15 ` Jiang, Yunhong
@ 2010-09-28 14:56 ` Konrad Rzeszutek Wilk
2010-09-30 18:55 ` Bruce Edge
1 sibling, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-09-28 14:56 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>
> Initialized empty Git repository in
> /import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> remote: fatal: Failed to traverse parents of commit
> 979e121cb348add17ed8171bf447b27a3a9d1be3
> remote: aborting due to possible repository corruption on the remote side.
> fatal: early EOF
> fatal: index-pack failed
That should have worked, but it looks as my git repo is busted. Let me fix that
and once it done you should be able to do
cd xen
git checkout origin/pv/pcifront-2.6.32
>
> >
> > It has the latest pcifront driver but without the PVonHVM enhancments
> > so we can try to eliminate the PvONHVM logic out of the picture.
> >
> >>
> >> >
> >> > > - the interrupt does happen. But the interrupt service routine of
> >> > > tachyon driver doesn't detect any interrupt status related to this
> >> > > interrupt, which inhibits the tachyon chip from coming on-line. And
> >> > > there are high count of tachyon interrupt in /proc/interrupts
> >> >
> >> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
> >> > in the MMIO BAR?
> >> >
> >>
> >> The driver would check the appropriate register (tachyon registers) in
> >> the MMIO to determine the source of interrupts.
> >
> > OK, so that isn't it. Is there anything at these vectors:
> > 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
> > an inkling what device this is set for.
>
> When I run a distro kernel in hvm mode, I get the expected irq mappings:
>
> 'i' - Note 66 - 69
> (XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> type=PCI-MSI status=00000010 in-flight=0
> domain-list=10:127(----),
> (XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> type=PCI-MSI status=00000010 in-flight=0
> domain-list=10:126(----),
> (XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> type=PCI-MSI status=00000010 in-flight=0
> domain-list=10:125(----),
> (XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> type=PCI-MSI status=00000010 in-flight=0
> domain-list=10:124(----)
>
What does cat /proc/interrupts (don't do the grep) for this HVM guest?
>
> 'q'
> (XEN) Interrupts { 32, 41-42, 47, 124-127 }
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 4:45 ` Bruce Edge
@ 2010-09-28 16:08 ` Lin, Ray
2010-09-28 16:19 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 42+ messages in thread
From: Lin, Ray @ 2010-09-28 16:08 UTC (permalink / raw)
To: Bruce Edge, Jiang, Yunhong
Cc: xen-devel@lists.xensource.com, Rzeszutek Wilk, Konrad
[-- Attachment #1.1: Type: text/plain, Size: 16835 bytes --]
I just checked the "xen dmesg". Look like DMA/iommu is the root cause of this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA write to a dword memory location to indicate the source of interrupt. What iommu option do you recommend to use ?
(XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0] fault addr c00000, iommu reg = ffff82c3fff57000
(XEN) DMAR:[fault reason 05h] PTE Write access is not set
(XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
(XEN) root_entry = ffff83019ff70000
(XEN) root_entry[7] = 19cf52001
(XEN) context = ffff83019cf52000
(XEN) context[0] = 102_706dc005
(XEN) l4 = ffff8300706dc000
(XEN) l4_index = 0
(XEN) l4[0] = 706db003
(XEN) l3 = ffff8300706db000
(XEN) l3_index = 0
(XEN) l3[0] = 706da003
(XEN) l2 = ffff8300706da000
(XEN) l2_index = 6
(XEN) l2[6] = 0
-Ray
________________________________
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
Sent: Monday, September 27, 2010 9:46 PM
To: Jiang, Yunhong
Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
"xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
I looked at the xm dmesg output and there's nothing more than what I already provided, aside from a bunch of commands from me poking at it.
-Bruce
Thanks
--jyh
From: Bruce Edge [mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
Sent: Tuesday, September 28, 2010 11:16 AM
To: Jiang, Yunhong
Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
Yes, there is 1 quad port card is this sytem:
07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
Also is it possible to share the xen output?
I attached the dom0 boot output. Let me know if you wanted something else.
Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
[ 1817.684097] ------------[ cut here ]------------
[ 1817.684113] WARNING: at kernel/lockdep.c:2323 trace_hardirqs_on_caller+0x12f/0x190()
[ 1817.684119] Hardware name: ProLiant DL380 G6
[ 1817.684122] Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage
[ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1
[ 1817.684195] Call Trace:
[ 1817.684197] <IRQ> [<ffffffff810aa18f>] ? trace_hardirqs_on_caller+0x12f/0x190
[ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
[ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40
[ 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20
[ 1817.684229] [<ffffffff810aa18f>] trace_hardirqs_on_caller+0x12f/0x190
[ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10
[ 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40
[ 1817.684266] [<ffffffff813c4fc5>] add_to_net_schedule_list_tail+0x85/0xd0
[ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160
[ 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180
[ 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170
[ 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
[ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
[ 1817.684304] [<ffffffff8101647e>] xen_do_hypervisor_callback+0x1e/0x30
[ 1817.684308] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1817.684319] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1817.684325] [<ffffffff813bce54>] ? xb_write+0x1e4/0x290
[ 1817.684330] [<ffffffff813bd8ca>] ? xs_talkv+0x6a/0x1f0
[ 1817.684336] [<ffffffff813bd8d8>] ? xs_talkv+0x78/0x1f0
[ 1817.684341] [<ffffffff813bdbcd>] ? xs_single+0x4d/0x60
[ 1817.684346] [<ffffffff813be502>] ? xenbus_read+0x52/0x80
[ 1817.684352] [<ffffffff813c87fc>] ? frontend_changed+0x48c/0x770
[ 1817.684358] [<ffffffff813bf76d>] ? xenbus_otherend_changed+0xdd/0x1b0
[ 1817.684365] [<ffffffff8101122f>] ? xen_restore_fl_direct_end+0x0/0x1
[ 1817.684371] [<ffffffff810ac830>] ? lock_release+0xb0/0x230
[ 1817.684376] [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20
[ 1817.684382] [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160
[ 1817.684389] [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40
[ 1817.684394] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160
[ 1817.684400] [<ffffffff81093086>] ? kthread+0x96/0xb0
[ 1817.684405] [<ffffffff8101632a>] ? child_rip+0xa/0x20
[ 1817.684410] [<ffffffff81015c90>] ? restore_args+0x0/0x30
[ 1817.684415] [<ffffffff81016320>] ? child_rip+0x0/0x20
-Bruce
Thanks
--jyh
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com>
>[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com>] On Behalf Of Bruce Edge
>Sent: Tuesday, September 28, 2010 7:54 AM
>To: Konrad Rzeszutek Wilk
>Cc: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
>On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
>>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
>>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>>> >
>>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>>> > > One of our developers who is working on a tachyon driver is
>>> > > complaining that the pvops domU kernel is not working for these MSI
>>> > > interrupts.
>>> > > This is using the current head of xen/2.6.32.x on both a single
>>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
>>> > >
>>> > > Here are his comments:
>>> > >
>>> > > - the driver has no problem to enable msi interrupt and request the
>>> > > interrupt through kernel functions pci_enable_msi & request_irq
>>> >
>>> > What shows up in the Xen console when you send the 'q' key? Does it
>>> > show that the vector is assigned to the appropiate guest?
>>>
>>> The Xen console q key shows that the domU is assigned:
>>>
>>> (XEN) Interrupts { 32, 41-42, 47 }
>>
>> Aha!
>>
>>>
>>> but the domU thinks it has:
>>>
>>> 124/125/126/127
>>>
>>> Is there some mapping that's taking place, or is this plain wrong?
>>
>> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
>> setup as IRQ numbers in the DomU guest. You should have seen
>>
>> 32:
>> 41:
>> 42:
>> 47:
>> in you /proc/interrupts on your DomU guest.
>>
>> I wonder what broke - can you use
>git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
>> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
>
>Please forgive the git ignorance.
>
>Is this the right syntax?
>
>git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32>
>linux-2.6.32-pv-pcifront
>
>Initialized empty Git repository in
>/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
>fatal: The remote end hung up unexpectedly
>
>Or:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
>
>Initialized empty Git repository in
>/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
>remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
>remote: fatal: Failed to traverse parents of commit
>979e121cb348add17ed8171bf447b27a3a9d1be3
>remote: aborting due to possible repository corruption on the remote side.
>fatal: early EOF
>fatal: index-pack failed
>
>>
>> It has the latest pcifront driver but without the PVonHVM enhancments
>> so we can try to eliminate the PvONHVM logic out of the picture.
>>
>>>
>>> >
>>> > > - the interrupt does happen. But the interrupt service routine of
>>> > > tachyon driver doesn't detect any interrupt status related to this
>>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
>>> > > there are high count of tachyon interrupt in /proc/interrupts
>>> >
>>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
>>> > in the MMIO BAR?
>>> >
>>>
>>> The driver would check the appropriate register (tachyon registers) in
>>> the MMIO to determine the source of interrupts.
>>
>> OK, so that isn't it. Is there anything at these vectors:
>> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
>> an inkling what device this is set for.
>
>When I run a distro kernel in hvm mode, I get the expected irq mappings:
>
>'i' - Note 66 - 69
>(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:127(----),
>(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:126(----),
>(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:125(----),
>(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=10:124(----)
>
>
>'q'
>(XEN) Interrupts { 32, 41-42, 47, 124-127 }
>
>
>The same data with pv-ops kernel shows:
>
>'i'
>IRQ numbers stop at 65, no 66 - 69 present:
>
>(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=0:289(----),
>(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
>type=PCI-MSI status=00000002 mapped, unbound
>(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
>type=PCI-MSI status=00000010 in-flight=0
>domain-list=0:287(----),
>(XEN) IO-APIC interrupt information:
>
>'q'
>(XEN) Interrupts { 32, 41-42, 47 }
>
>>
>>>
>>> > >
>>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
>>> > >
>124: 760415 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>125: 762234 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>126: 764180 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> > >
>127: 764164 0 0 0 0
> 0
>>> > > 0 0 0 0 0
> 0
>>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>> >
>>> > Can you provide the full dmesg output?
>>>
>>> Attached.
>>>
>>> Some possibly related messages on dom0 console:
>>>
>>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
>>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
>>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
>>> [ 1882.269834] xen: --> irq=32
>>> [ 1882.269841] Already setup the GSI :32
>>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
>>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
>>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>
>> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
>> to find out what is at the configuration space. You could enable
>> it using the permissive attribute.
>>
>>> [ 1882.270465] 1) see permissive attribute in sysfs
>>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.270615] alloc irq_desc for 478 on node 0
>>> [ 1882.270625] alloc kstat_irqs on node 0
>>
>> So for 478: what do you see? xen-pciback I presume?
>>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
>>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
>>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
>>> [ 1882.348445] xen: --> irq=42
>>> [ 1882.348472] Already setup the GSI :42
>>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
>>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
>>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>> [ 1882.349066] 1) see permissive attribute in sysfs
>>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.349205] alloc irq_desc for 477 on node 0
>>> [ 1882.349215] alloc kstat_irqs on node 0
>>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
>>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
>>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
>>> [ 1882.402916] xen: --> irq=47
>>> [ 1882.402921] Already setup the GSI :47
>>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
>>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
>>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
>>> read-only configuration space field at offset 0x62, size 2. This may
>>> be harmless, but if you have problems with your device:
>>> [ 1882.403282] 1) see permissive attribute in sysfs
>>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
>>> with details of your device obtained from lspci.
>>> [ 1882.403380] alloc irq_desc for 476 on node 0
>>> [ 1882.403386] alloc kstat_irqs on node 0
>>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
>>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
>>> fault addr e6f80000, iommu reg = ffff82c3fff57000
>>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
>>> (XEN) root_entry = ffff83019ff70000
>>> (XEN) root_entry[7] = 19cf52001
>>> (XEN) context = ffff83019cf52000
>>> (XEN) context[0] = 102_706dc005
>>> (XEN) l4 = ffff8300706dc000
>>> (XEN) l4_index = 0
>>> (XEN) l4[0] = 706db003
>>> (XEN) l3 = ffff8300706db000
>>> (XEN) l3_index = 3
>>> (XEN) l3[3] = 702b6003
>>> (XEN) l2 = ffff8300702b6000
>>> (XEN) l2_index = 137
>>> (XEN) l2[137] = 0
>>> (XEN) l2[137] not present
>>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
>>
>> That is not good. What changed from your earlier emails that this was triggered?
>
>Nothing
>> Or was it triggered all along?
>
>Yes, I just included it for completeness
>
>> What happens if you run the system without the iommu enabled?
>
>Haven't tried yet. Will check that next.
>
>-Bruce
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
>http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 31995 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 16:08 ` Lin, Ray
@ 2010-09-28 16:19 ` Konrad Rzeszutek Wilk
2010-09-28 18:35 ` Lin, Ray
2010-09-29 0:53 ` Jiang, Yunhong
0 siblings, 2 replies; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-09-28 16:19 UTC (permalink / raw)
To: Lin, Ray, JBeulich
Cc: xen-devel@lists.xensource.com, Jiang, Yunhong, Bruce Edge
On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
> I just checked the "xen dmesg". Look like DMA/iommu is the root cause of this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA write to a dword memory location to indicate the source of interrupt. What iommu option do you recommend to use ?
Lets get Jan involved in this discussion.
Jan, would some of your patches that inhibit the MSI write affect this
in a PV guest?
>
> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0] fault addr c00000, iommu reg = ffff82c3fff57000
> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
> (XEN) root_entry = ffff83019ff70000
> (XEN) root_entry[7] = 19cf52001
> (XEN) context = ffff83019cf52000
> (XEN) context[0] = 102_706dc005
> (XEN) l4 = ffff8300706dc000
> (XEN) l4_index = 0
> (XEN) l4[0] = 706db003
> (XEN) l3 = ffff8300706db000
> (XEN) l3_index = 0
> (XEN) l3[0] = 706da003
> (XEN) l2 = ffff8300706da000
> (XEN) l2_index = 6
> (XEN) l2[6] = 0
>
>
> -Ray
>
>
> ________________________________
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
> Sent: Monday, September 27, 2010 9:46 PM
> To: Jiang, Yunhong
> Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
> On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> "xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
>
> I looked at the xm dmesg output and there's nothing more than what I already provided, aside from a bunch of commands from me poking at it.
>
> -Bruce
>
>
> Thanks
> --jyh
>
> From: Bruce Edge [mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
> Sent: Tuesday, September 28, 2010 11:16 AM
> To: Jiang, Yunhong
> Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
> On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
>
> Yes, there is 1 quad port card is this sytem:
>
> 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>
>
> Also is it possible to share the xen output?
>
> I attached the dom0 boot output. Let me know if you wanted something else.
>
> Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
>
> [ 1817.684097] ------------[ cut here ]------------
> [ 1817.684113] WARNING: at kernel/lockdep.c:2323 trace_hardirqs_on_caller+0x12f/0x190()
> [ 1817.684119] Hardware name: ProLiant DL380 G6
> [ 1817.684122] Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage
> [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1
> [ 1817.684195] Call Trace:
> [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ? trace_hardirqs_on_caller+0x12f/0x190
> [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
> [ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40
> [ 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20
> [ 1817.684229] [<ffffffff810aa18f>] trace_hardirqs_on_caller+0x12f/0x190
> [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10
> [ 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40
> [ 1817.684266] [<ffffffff813c4fc5>] add_to_net_schedule_list_tail+0x85/0xd0
> [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160
> [ 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180
> [ 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170
> [ 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
> [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
> [ 1817.684304] [<ffffffff8101647e>] xen_do_hypervisor_callback+0x1e/0x30
> [ 1817.684308] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
> [ 1817.684319] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
> [ 1817.684325] [<ffffffff813bce54>] ? xb_write+0x1e4/0x290
> [ 1817.684330] [<ffffffff813bd8ca>] ? xs_talkv+0x6a/0x1f0
> [ 1817.684336] [<ffffffff813bd8d8>] ? xs_talkv+0x78/0x1f0
> [ 1817.684341] [<ffffffff813bdbcd>] ? xs_single+0x4d/0x60
> [ 1817.684346] [<ffffffff813be502>] ? xenbus_read+0x52/0x80
> [ 1817.684352] [<ffffffff813c87fc>] ? frontend_changed+0x48c/0x770
> [ 1817.684358] [<ffffffff813bf76d>] ? xenbus_otherend_changed+0xdd/0x1b0
> [ 1817.684365] [<ffffffff8101122f>] ? xen_restore_fl_direct_end+0x0/0x1
> [ 1817.684371] [<ffffffff810ac830>] ? lock_release+0xb0/0x230
> [ 1817.684376] [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20
> [ 1817.684382] [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160
> [ 1817.684389] [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40
> [ 1817.684394] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160
> [ 1817.684400] [<ffffffff81093086>] ? kthread+0x96/0xb0
> [ 1817.684405] [<ffffffff8101632a>] ? child_rip+0xa/0x20
> [ 1817.684410] [<ffffffff81015c90>] ? restore_args+0x0/0x30
> [ 1817.684415] [<ffffffff81016320>] ? child_rip+0x0/0x20
>
> -Bruce
>
>
>
> Thanks
> --jyh
>
> >-----Original Message-----
> >From: xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com>
> >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensource.com>] On Behalf Of Bruce Edge
> >Sent: Tuesday, September 28, 2010 7:54 AM
> >To: Konrad Rzeszutek Wilk
> >Cc: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> >Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
> >
> >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> >>> >
> >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> >>> > > One of our developers who is working on a tachyon driver is
> >>> > > complaining that the pvops domU kernel is not working for these MSI
> >>> > > interrupts.
> >>> > > This is using the current head of xen/2.6.32.x on both a single
> >>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> >>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
> >>> > >
> >>> > > Here are his comments:
> >>> > >
> >>> > > - the driver has no problem to enable msi interrupt and request the
> >>> > > interrupt through kernel functions pci_enable_msi & request_irq
> >>> >
> >>> > What shows up in the Xen console when you send the 'q' key? Does it
> >>> > show that the vector is assigned to the appropiate guest?
> >>>
> >>> The Xen console q key shows that the domU is assigned:
> >>>
> >>> (XEN) Interrupts { 32, 41-42, 47 }
> >>
> >> Aha!
> >>
> >>>
> >>> but the domU thinks it has:
> >>>
> >>> 124/125/126/127
> >>>
> >>> Is there some mapping that's taking place, or is this plain wrong?
> >>
> >> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
> >> setup as IRQ numbers in the DomU guest. You should have seen
> >>
> >> 32:
> >> 41:
> >> 42:
> >> 47:
> >> in you /proc/interrupts on your DomU guest.
> >>
> >> I wonder what broke - can you use
> >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> >
> >Please forgive the git ignorance.
> >
> >Is this the right syntax?
> >
> >git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32>
> >linux-2.6.32-pv-pcifront
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
> >fatal: The remote end hung up unexpectedly
> >
> >Or:
> >
> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> >remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> >remote: fatal: Failed to traverse parents of commit
> >979e121cb348add17ed8171bf447b27a3a9d1be3
> >remote: aborting due to possible repository corruption on the remote side.
> >fatal: early EOF
> >fatal: index-pack failed
> >
> >>
> >> It has the latest pcifront driver but without the PVonHVM enhancments
> >> so we can try to eliminate the PvONHVM logic out of the picture.
> >>
> >>>
> >>> >
> >>> > > - the interrupt does happen. But the interrupt service routine of
> >>> > > tachyon driver doesn't detect any interrupt status related to this
> >>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
> >>> > > there are high count of tachyon interrupt in /proc/interrupts
> >>> >
> >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
> >>> > in the MMIO BAR?
> >>> >
> >>>
> >>> The driver would check the appropriate register (tachyon registers) in
> >>> the MMIO to determine the source of interrupts.
> >>
> >> OK, so that isn't it. Is there anything at these vectors:
> >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
> >> an inkling what device this is set for.
> >
> >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> >
> >'i' - Note 66 - 69
> >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:127(----),
> >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:126(----),
> >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:125(----),
> >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:124(----)
> >
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> >
> >
> >The same data with pv-ops kernel shows:
> >
> >'i'
> >IRQ numbers stop at 65, no 66 - 69 present:
> >
> >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:289(----),
> >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> >type=PCI-MSI status=00000002 mapped, unbound
> >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:287(----),
> >(XEN) IO-APIC interrupt information:
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47 }
> >
> >>
> >>>
> >>> > >
> >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> >>> > >
> >124: 760415 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >125: 762234 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >126: 764180 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >127: 764164 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> >
> >>> > Can you provide the full dmesg output?
> >>>
> >>> Attached.
> >>>
> >>> Some possibly related messages on dom0 console:
> >>>
> >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
> >>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
> >>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
> >>> [ 1882.269834] xen: --> irq=32
> >>> [ 1882.269841] Already setup the GSI :32
> >>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
> >>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
> >>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>
> >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> >> to find out what is at the configuration space. You could enable
> >> it using the permissive attribute.
> >>
> >>> [ 1882.270465] 1) see permissive attribute in sysfs
> >>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> >>> [ 1882.270625] alloc kstat_irqs on node 0
> >>
> >> So for 478: what do you see? xen-pciback I presume?
> >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
> >>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
> >>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
> >>> [ 1882.348445] xen: --> irq=42
> >>> [ 1882.348472] Already setup the GSI :42
> >>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
> >>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
> >>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>> [ 1882.349066] 1) see permissive attribute in sysfs
> >>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> >>> [ 1882.349215] alloc kstat_irqs on node 0
> >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
> >>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
> >>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
> >>> [ 1882.402916] xen: --> irq=47
> >>> [ 1882.402921] Already setup the GSI :47
> >>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
> >>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
> >>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
> >>> read-only configuration space field at offset 0x62, size 2. This may
> >>> be harmless, but if you have problems with your device:
> >>> [ 1882.403282] 1) see permissive attribute in sysfs
> >>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
> >>> with details of your device obtained from lspci.
> >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> >>> [ 1882.403386] alloc kstat_irqs on node 0
> >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> >>> fault addr e6f80000, iommu reg = ffff82c3fff57000
> >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
> >>> (XEN) root_entry = ffff83019ff70000
> >>> (XEN) root_entry[7] = 19cf52001
> >>> (XEN) context = ffff83019cf52000
> >>> (XEN) context[0] = 102_706dc005
> >>> (XEN) l4 = ffff8300706dc000
> >>> (XEN) l4_index = 0
> >>> (XEN) l4[0] = 706db003
> >>> (XEN) l3 = ffff8300706db000
> >>> (XEN) l3_index = 3
> >>> (XEN) l3[3] = 702b6003
> >>> (XEN) l2 = ffff8300702b6000
> >>> (XEN) l2_index = 137
> >>> (XEN) l2[137] = 0
> >>> (XEN) l2[137] not present
> >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
> >>
> >> That is not good. What changed from your earlier emails that this was triggered?
> >
> >Nothing
> >> Or was it triggered all along?
> >
> >Yes, I just included it for completeness
> >
> >> What happens if you run the system without the iommu enabled?
> >
> >Haven't tried yet. Will check that next.
> >
> >-Bruce
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
> >http://lists.xensource.com/xen-devel
>
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 16:19 ` Konrad Rzeszutek Wilk
@ 2010-09-28 18:35 ` Lin, Ray
2010-09-28 20:14 ` Konrad Rzeszutek Wilk
2010-09-29 0:53 ` Jiang, Yunhong
1 sibling, 1 reply; 42+ messages in thread
From: Lin, Ray @ 2010-09-28 18:35 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, JBeulich@novell.com
Cc: xen-devel@lists.xensource.com, Jiang, Yunhong, Bruce Edge
[-- Attachment #1.1: Type: text/plain, Size: 18690 bytes --]
> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> fault addr c00000, iommu reg = ffff82c3fff57000
The driver gets the physical addr 0xc0049c thru kernel function virt_to_phys() and set the dma address of Tachyon chip with this address. This address translation is also involved with SWIOTLB library. Is there any issue related with SWIOTLB in pvops kernel ?
-Ray
-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
Sent: Tuesday, September 28, 2010 9:19 AM
To: Lin, Ray; JBeulich@novell.com
Cc: Bruce Edge; Jiang, Yunhong; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
> I just checked the "xen dmesg". Look like DMA/iommu is the root cause of this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA write to a dword memory location to indicate the source of interrupt. What iommu option do you recommend to use ?
Lets get Jan involved in this discussion.
Jan, would some of your patches that inhibit the MSI write affect this in a PV guest?
>
> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> fault addr c00000, iommu reg = ffff82c3fff57000
> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
> (XEN) root_entry = ffff83019ff70000
> (XEN) root_entry[7] = 19cf52001
> (XEN) context = ffff83019cf52000
> (XEN) context[0] = 102_706dc005
> (XEN) l4 = ffff8300706dc000
> (XEN) l4_index = 0
> (XEN) l4[0] = 706db003
> (XEN) l3 = ffff8300706db000
> (XEN) l3_index = 0
> (XEN) l3[0] = 706da003
> (XEN) l2 = ffff8300706da000
> (XEN) l2_index = 6
> (XEN) l2[6] = 0
>
>
> -Ray
>
>
> ________________________________
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
> Sent: Monday, September 27, 2010 9:46 PM
> To: Jiang, Yunhong
> Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> on Nehalem
>
> On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> "xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
>
> I looked at the xm dmesg output and there's nothing more than what I already provided, aside from a bunch of commands from me poking at it.
>
> -Bruce
>
>
> Thanks
> --jyh
>
> From: Bruce Edge
> [mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
> Sent: Tuesday, September 28, 2010 11:16 AM
> To: Jiang, Yunhong
> Cc: Konrad Rzeszutek Wilk;
> xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> on Nehalem
>
> On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
>
> Yes, there is 1 quad port card is this sytem:
>
> 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>
>
> Also is it possible to share the xen output?
>
> I attached the dom0 boot output. Let me know if you wanted something else.
>
> Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
>
> [ 1817.684097] ------------[ cut here ]------------ [ 1817.684113]
> WARNING: at kernel/lockdep.c:2323
> trace_hardirqs_on_caller+0x12f/0x190()
> [ 1817.684119] Hardware name: ProLiant DL380 G6 [ 1817.684122] Modules
> linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev fbcon tileblit
> font bitblit softcursor xen_evtchn xen_pciback radeon ttm
> drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1 [ 1817.684195] Call Trace:
> [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
> trace_hardirqs_on_caller+0x12f/0x190
> [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0 [
> 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40 [
> 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20 [
> 1817.684229] [<ffffffff810aa18f>]
> trace_hardirqs_on_caller+0x12f/0x190
> [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10 [
> 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40 [
> 1817.684266] [<ffffffff813c4fc5>]
> add_to_net_schedule_list_tail+0x85/0xd0
> [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160 [
> 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180 [
> 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170 [
> 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
> [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60 [
> 1817.684304] [<ffffffff8101647e>]
> xen_do_hypervisor_callback+0x1e/0x30
> [ 1817.684308] <EOI> [<ffffffff8100940a>] ?
> hypercall_page+0x40a/0x1010 [ 1817.684319] [<ffffffff8100940a>] ?
> hypercall_page+0x40a/0x1010 [ 1817.684325] [<ffffffff813bce54>] ?
> xb_write+0x1e4/0x290 [ 1817.684330] [<ffffffff813bd8ca>] ?
> xs_talkv+0x6a/0x1f0 [ 1817.684336] [<ffffffff813bd8d8>] ?
> xs_talkv+0x78/0x1f0 [ 1817.684341] [<ffffffff813bdbcd>] ?
> xs_single+0x4d/0x60 [ 1817.684346] [<ffffffff813be502>] ?
> xenbus_read+0x52/0x80 [ 1817.684352] [<ffffffff813c87fc>] ?
> frontend_changed+0x48c/0x770 [ 1817.684358] [<ffffffff813bf76d>] ?
> xenbus_otherend_changed+0xdd/0x1b0
> [ 1817.684365] [<ffffffff8101122f>] ?
> xen_restore_fl_direct_end+0x0/0x1 [ 1817.684371] [<ffffffff810ac830>]
> ? lock_release+0xb0/0x230 [ 1817.684376] [<ffffffff813bfae0>] ?
> frontend_changed+0x10/0x20 [ 1817.684382] [<ffffffff813bd4f5>] ?
> xenwatch_thread+0x55/0x160 [ 1817.684389] [<ffffffff81093400>] ?
> autoremove_wake_function+0x0/0x40 [ 1817.684394] [<ffffffff813bd4a0>]
> ? xenwatch_thread+0x0/0x160 [ 1817.684400] [<ffffffff81093086>] ?
> kthread+0x96/0xb0 [ 1817.684405] [<ffffffff8101632a>] ?
> child_rip+0xa/0x20 [ 1817.684410] [<ffffffff81015c90>] ?
> restore_args+0x0/0x30 [ 1817.684415] [<ffffffff81016320>] ?
> child_rip+0x0/0x20
>
> -Bruce
>
>
>
> Thanks
> --jyh
>
> >-----Original Message-----
> >From:
> >xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.
> >xensource.com>
> >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounce
> >s@lists.xensource.com>] On Behalf Of Bruce Edge
> >Sent: Tuesday, September 28, 2010 7:54 AM
> >To: Konrad Rzeszutek Wilk
> >Cc:
> >xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> >Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> >on Nehalem
> >
> >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> >>> >
> >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> >>> > > One of our developers who is working on a tachyon driver is
> >>> > > complaining that the pvops domU kernel is not working for
> >>> > > these MSI interrupts.
> >>> > > This is using the current head of xen/2.6.32.x on both a
> >>> > > single Nahelam 920 and a dual E5540. This behavior is
> >>> > > consistent with Xen 4.0.1, 4.0.2.rc1-pre and 4.1.
> >>> > >
> >>> > > Here are his comments:
> >>> > >
> >>> > > - the driver has no problem to enable msi interrupt and
> >>> > > request the interrupt through kernel functions pci_enable_msi
> >>> > > & request_irq
> >>> >
> >>> > What shows up in the Xen console when you send the 'q' key? Does
> >>> > it show that the vector is assigned to the appropiate guest?
> >>>
> >>> The Xen console q key shows that the domU is assigned:
> >>>
> >>> (XEN) Interrupts { 32, 41-42, 47 }
> >>
> >> Aha!
> >>
> >>>
> >>> but the domU thinks it has:
> >>>
> >>> 124/125/126/127
> >>>
> >>> Is there some mapping that's taking place, or is this plain wrong?
> >>
> >> That looks wrong. The IRQ numbers (even though they are MSI
> >> vectors) are setup as IRQ numbers in the DomU guest. You should
> >> have seen
> >>
> >> 32:
> >> 41:
> >> 42:
> >> 47:
> >> in you /proc/interrupts on your DomU guest.
> >>
> >> I wonder what broke - can you use
> >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://g
> >it.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> >
> >Please forgive the git ignorance.
> >
> >Is this the right syntax?
> >
> >git clone
> >git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.
> >32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-
> >2.6.32>
> >linux-2.6.32-pv-pcifront
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.gi
> >t/
> >fatal: The remote end hung up unexpectedly
> >
> >Or:
> >
> > git clone
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://
> > git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> >
> >Initialized empty Git repository in
> >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> >remote: error: Could not read
> >59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> >remote: fatal: Failed to traverse parents of commit
> >979e121cb348add17ed8171bf447b27a3a9d1be3
> >remote: aborting due to possible repository corruption on the remote side.
> >fatal: early EOF
> >fatal: index-pack failed
> >
> >>
> >> It has the latest pcifront driver but without the PVonHVM
> >> enhancments so we can try to eliminate the PvONHVM logic out of the picture.
> >>
> >>>
> >>> >
> >>> > > - the interrupt does happen. But the interrupt service routine
> >>> > > of tachyon driver doesn't detect any interrupt status related
> >>> > > to this interrupt, which inhibits the tachyon chip from coming
> >>> > > on-line. And there are high count of tachyon interrupt in
> >>> > > /proc/interrupts
> >>> >
> >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate
> >>> > register in the MMIO BAR?
> >>> >
> >>>
> >>> The driver would check the appropriate register (tachyon
> >>> registers) in the MMIO to determine the source of interrupts.
> >>
> >> OK, so that isn't it. Is there anything at these vectors:
> >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it
> >> should give you an inkling what device this is set for.
> >
> >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> >
> >'i' - Note 66 - 69
> >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:127(----),
> >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:126(----),
> >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:125(----),
> >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=10:124(----)
> >
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> >
> >
> >The same data with pv-ops kernel shows:
> >
> >'i'
> >IRQ numbers stop at 65, no 66 - 69 present:
> >
> >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:289(----),
> >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> >type=PCI-MSI status=00000002 mapped, unbound
> >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> >type=PCI-MSI status=00000010 in-flight=0
> >domain-list=0:287(----),
> >(XEN) IO-APIC interrupt information:
> >
> >'q'
> >(XEN) Interrupts { 32, 41-42, 47 }
> >
> >>
> >>>
> >>> > >
> >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> >>> > >
> >124: 760415 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >125: 762234 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >126: 764180 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> > >
> >127: 764164 0 0 0 0
> > 0
> >>> > > 0 0 0 0 0
> > 0
> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> >>> >
> >>> > Can you provide the full dmesg output?
> >>>
> >>> Attached.
> >>>
> >>> Some possibly related messages on dom0 console:
> >>>
> >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 ->
> >>> 0003) [ 1882.269800] xen: registering gsi 32 triggering 0 polarity
> >>> 1 [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32 [
> >>> 1882.269834] xen: --> irq=32 [ 1882.269841] Already setup the GSI
> >>> :32 [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32
> >>> (level, low) -> IRQ 32 [ 1882.269866] pciback 0000:07:00.0:
> >>> setting latency timer to 64 [ 1882.270463] pciback 0000:07:00.0:
> >>> Driver tried to write to a read-only configuration space field at
> >>> offset 0x62, size 2. This may be harmless, but if you have
> >>> problems with your device:
> >>
> >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> >> to find out what is at the configuration space. You could enable it
> >> using the permissive attribute.
> >>
> >>> [ 1882.270465] 1) see permissive attribute in sysfs [ 1882.270467]
> >>> 2) report problems to the xen-devel mailing list along with
> >>> details of your device obtained from lspci.
> >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> >>> [ 1882.270625] alloc kstat_irqs on node 0
> >>
> >> So for 478: what do you see? xen-pciback I presume?
> >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 ->
> >>> 0003) [ 1882.348433] xen: registering gsi 42 triggering 0 polarity
> >>> 1 [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42 [
> >>> 1882.348445] xen: --> irq=42 [ 1882.348472] Already setup the GSI
> >>> :42 [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42
> >>> (level, low) -> IRQ 42 [ 1882.348497] pciback 0000:07:00.1:
> >>> setting latency timer to 64 [ 1882.349063] pciback 0000:07:00.1:
> >>> Driver tried to write to a read-only configuration space field at
> >>> offset 0x62, size 2. This may be harmless, but if you have
> >>> problems with your device:
> >>> [ 1882.349066] 1) see permissive attribute in sysfs [ 1882.349067]
> >>> 2) report problems to the xen-devel mailing list along with
> >>> details of your device obtained from lspci.
> >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> >>> [ 1882.349215] alloc kstat_irqs on node 0
> >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 ->
> >>> 0003) [ 1882.402908] xen: registering gsi 47 triggering 0 polarity
> >>> 1 [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47 [
> >>> 1882.402916] xen: --> irq=47 [ 1882.402921] Already setup the GSI
> >>> :47 [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47
> >>> (level, low) -> IRQ 47 [ 1882.402938] pciback 0000:07:00.2:
> >>> setting latency timer to 64 [ 1882.403280] pciback 0000:07:00.2:
> >>> Driver tried to write to a read-only configuration space field at
> >>> offset 0x62, size 2. This may be harmless, but if you have
> >>> problems with your device:
> >>> [ 1882.403282] 1) see permissive attribute in sysfs [ 1882.403282]
> >>> 2) report problems to the xen-devel mailing list along with
> >>> details of your device obtained from lspci.
> >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> >>> [ 1882.403386] alloc kstat_irqs on node 0
> >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> >>> fault addr e6f80000, iommu reg = ffff82c3fff57000
> >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
> >>> (XEN) root_entry = ffff83019ff70000
> >>> (XEN) root_entry[7] = 19cf52001
> >>> (XEN) context = ffff83019cf52000
> >>> (XEN) context[0] = 102_706dc005
> >>> (XEN) l4 = ffff8300706dc000
> >>> (XEN) l4_index = 0
> >>> (XEN) l4[0] = 706db003
> >>> (XEN) l3 = ffff8300706db000
> >>> (XEN) l3_index = 3
> >>> (XEN) l3[3] = 702b6003
> >>> (XEN) l2 = ffff8300702b6000
> >>> (XEN) l2_index = 137
> >>> (XEN) l2[137] = 0
> >>> (XEN) l2[137] not present
> >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0
> >>> [ec=0000]
> >>
> >> That is not good. What changed from your earlier emails that this was triggered?
> >
> >Nothing
> >> Or was it triggered all along?
> >
> >Yes, I just included it for completeness
> >
> >> What happens if you run the system without the iommu enabled?
> >
> >Haven't tried yet. Will check that next.
> >
> >-Bruce
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
> >http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 28723 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 18:35 ` Lin, Ray
@ 2010-09-28 20:14 ` Konrad Rzeszutek Wilk
2010-09-28 20:38 ` Lin, Ray
0 siblings, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-09-28 20:14 UTC (permalink / raw)
To: Lin, Ray
Cc: xen-devel@lists.xensource.com, Bruce Edge, JBeulich@novell.com,
Jiang, Yunhong
On Tue, Sep 28, 2010 at 12:35:12PM -0600, Lin, Ray wrote:
>
> > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > fault addr c00000, iommu reg = ffff82c3fff57000
>
> The driver gets the physical addr 0xc0049c thru kernel function virt_to_phys() and set the dma address of Tachyon chip with this address. This address translation is also involved with SWIOTLB library. Is there any issue related with SWIOTLB in pvops kernel ?
If the driver is using pci_map_page, which goes through the Xen-SWIOTLB library, then
it works correctly (the Xen-SWIOTLB does a PFN->MFN translation to give you the bus address).
I presume the physical address (0xc0049c) is the BAR of the PCI device, right?
There are no issues with the Xen-SWIOTLB in the pvops kernel.
>
>
>
>
> -Ray
>
>
>
>
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Tuesday, September 28, 2010 9:19 AM
> To: Lin, Ray; JBeulich@novell.com
> Cc: Bruce Edge; Jiang, Yunhong; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
> On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
> > I just checked the "xen dmesg". Look like DMA/iommu is the root cause of this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA write to a dword memory location to indicate the source of interrupt. What iommu option do you recommend to use ?
>
> Lets get Jan involved in this discussion.
>
> Jan, would some of your patches that inhibit the MSI write affect this in a PV guest?
>
> >
> > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > fault addr c00000, iommu reg = ffff82c3fff57000
> > (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
> > (XEN) root_entry = ffff83019ff70000
> > (XEN) root_entry[7] = 19cf52001
> > (XEN) context = ffff83019cf52000
> > (XEN) context[0] = 102_706dc005
> > (XEN) l4 = ffff8300706dc000
> > (XEN) l4_index = 0
> > (XEN) l4[0] = 706db003
> > (XEN) l3 = ffff8300706db000
> > (XEN) l3_index = 0
> > (XEN) l3[0] = 706da003
> > (XEN) l2 = ffff8300706da000
> > (XEN) l2_index = 6
> > (XEN) l2[6] = 0
> >
> >
> > -Ray
> >
> >
> > ________________________________
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
> > Sent: Monday, September 27, 2010 9:46 PM
> > To: Jiang, Yunhong
> > Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
> > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > on Nehalem
> >
> > On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > "xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
> >
> > I looked at the xm dmesg output and there's nothing more than what I already provided, aside from a bunch of commands from me poking at it.
> >
> > -Bruce
> >
> >
> > Thanks
> > --jyh
> >
> > From: Bruce Edge
> > [mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
> > Sent: Tuesday, September 28, 2010 11:16 AM
> > To: Jiang, Yunhong
> > Cc: Konrad Rzeszutek Wilk;
> > xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> >
> > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > on Nehalem
> >
> > On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
> >
> > Yes, there is 1 quad port card is this sytem:
> >
> > 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> >
> >
> > Also is it possible to share the xen output?
> >
> > I attached the dom0 boot output. Let me know if you wanted something else.
> >
> > Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
> >
> > [ 1817.684097] ------------[ cut here ]------------ [ 1817.684113]
> > WARNING: at kernel/lockdep.c:2323
> > trace_hardirqs_on_caller+0x12f/0x190()
> > [ 1817.684119] Hardware name: ProLiant DL380 G6 [ 1817.684122] Modules
> > linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev fbcon tileblit
> > font bitblit softcursor xen_evtchn xen_pciback radeon ttm
> > drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1 [ 1817.684195] Call Trace:
> > [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
> > trace_hardirqs_on_caller+0x12f/0x190
> > [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0 [
> > 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40 [
> > 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20 [
> > 1817.684229] [<ffffffff810aa18f>]
> > trace_hardirqs_on_caller+0x12f/0x190
> > [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10 [
> > 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40 [
> > 1817.684266] [<ffffffff813c4fc5>]
> > add_to_net_schedule_list_tail+0x85/0xd0
> > [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160 [
> > 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180 [
> > 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170 [
> > 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
> > [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60 [
> > 1817.684304] [<ffffffff8101647e>]
> > xen_do_hypervisor_callback+0x1e/0x30
> > [ 1817.684308] <EOI> [<ffffffff8100940a>] ?
> > hypercall_page+0x40a/0x1010 [ 1817.684319] [<ffffffff8100940a>] ?
> > hypercall_page+0x40a/0x1010 [ 1817.684325] [<ffffffff813bce54>] ?
> > xb_write+0x1e4/0x290 [ 1817.684330] [<ffffffff813bd8ca>] ?
> > xs_talkv+0x6a/0x1f0 [ 1817.684336] [<ffffffff813bd8d8>] ?
> > xs_talkv+0x78/0x1f0 [ 1817.684341] [<ffffffff813bdbcd>] ?
> > xs_single+0x4d/0x60 [ 1817.684346] [<ffffffff813be502>] ?
> > xenbus_read+0x52/0x80 [ 1817.684352] [<ffffffff813c87fc>] ?
> > frontend_changed+0x48c/0x770 [ 1817.684358] [<ffffffff813bf76d>] ?
> > xenbus_otherend_changed+0xdd/0x1b0
> > [ 1817.684365] [<ffffffff8101122f>] ?
> > xen_restore_fl_direct_end+0x0/0x1 [ 1817.684371] [<ffffffff810ac830>]
> > ? lock_release+0xb0/0x230 [ 1817.684376] [<ffffffff813bfae0>] ?
> > frontend_changed+0x10/0x20 [ 1817.684382] [<ffffffff813bd4f5>] ?
> > xenwatch_thread+0x55/0x160 [ 1817.684389] [<ffffffff81093400>] ?
> > autoremove_wake_function+0x0/0x40 [ 1817.684394] [<ffffffff813bd4a0>]
> > ? xenwatch_thread+0x0/0x160 [ 1817.684400] [<ffffffff81093086>] ?
> > kthread+0x96/0xb0 [ 1817.684405] [<ffffffff8101632a>] ?
> > child_rip+0xa/0x20 [ 1817.684410] [<ffffffff81015c90>] ?
> > restore_args+0x0/0x30 [ 1817.684415] [<ffffffff81016320>] ?
> > child_rip+0x0/0x20
> >
> > -Bruce
> >
> >
> >
> > Thanks
> > --jyh
> >
> > >-----Original Message-----
> > >From:
> > >xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.
> > >xensource.com>
> > >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounce
> > >s@lists.xensource.com>] On Behalf Of Bruce Edge
> > >Sent: Tuesday, September 28, 2010 7:54 AM
> > >To: Konrad Rzeszutek Wilk
> > >Cc:
> > >xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> > >Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > >on Nehalem
> > >
> > >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> > ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> > >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> > >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > >>> >
> > >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> > >>> > > One of our developers who is working on a tachyon driver is
> > >>> > > complaining that the pvops domU kernel is not working for
> > >>> > > these MSI interrupts.
> > >>> > > This is using the current head of xen/2.6.32.x on both a
> > >>> > > single Nahelam 920 and a dual E5540. This behavior is
> > >>> > > consistent with Xen 4.0.1, 4.0.2.rc1-pre and 4.1.
> > >>> > >
> > >>> > > Here are his comments:
> > >>> > >
> > >>> > > - the driver has no problem to enable msi interrupt and
> > >>> > > request the interrupt through kernel functions pci_enable_msi
> > >>> > > & request_irq
> > >>> >
> > >>> > What shows up in the Xen console when you send the 'q' key? Does
> > >>> > it show that the vector is assigned to the appropiate guest?
> > >>>
> > >>> The Xen console q key shows that the domU is assigned:
> > >>>
> > >>> (XEN) Interrupts { 32, 41-42, 47 }
> > >>
> > >> Aha!
> > >>
> > >>>
> > >>> but the domU thinks it has:
> > >>>
> > >>> 124/125/126/127
> > >>>
> > >>> Is there some mapping that's taking place, or is this plain wrong?
> > >>
> > >> That looks wrong. The IRQ numbers (even though they are MSI
> > >> vectors) are setup as IRQ numbers in the DomU guest. You should
> > >> have seen
> > >>
> > >> 32:
> > >> 41:
> > >> 42:
> > >> 47:
> > >> in you /proc/interrupts on your DomU guest.
> > >>
> > >> I wonder what broke - can you use
> > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://g
> > >it.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> > >
> > >Please forgive the git ignorance.
> > >
> > >Is this the right syntax?
> > >
> > >git clone
> > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.
> > >32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-
> > >2.6.32>
> > >linux-2.6.32-pv-pcifront
> > >
> > >Initialized empty Git repository in
> > >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.gi
> > >t/
> > >fatal: The remote end hung up unexpectedly
> > >
> > >Or:
> > >
> > > git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://
> > > git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > >
> > >Initialized empty Git repository in
> > >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> > >remote: error: Could not read
> > >59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> > >remote: fatal: Failed to traverse parents of commit
> > >979e121cb348add17ed8171bf447b27a3a9d1be3
> > >remote: aborting due to possible repository corruption on the remote side.
> > >fatal: early EOF
> > >fatal: index-pack failed
> > >
> > >>
> > >> It has the latest pcifront driver but without the PVonHVM
> > >> enhancments so we can try to eliminate the PvONHVM logic out of the picture.
> > >>
> > >>>
> > >>> >
> > >>> > > - the interrupt does happen. But the interrupt service routine
> > >>> > > of tachyon driver doesn't detect any interrupt status related
> > >>> > > to this interrupt, which inhibits the tachyon chip from coming
> > >>> > > on-line. And there are high count of tachyon interrupt in
> > >>> > > /proc/interrupts
> > >>> >
> > >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate
> > >>> > register in the MMIO BAR?
> > >>> >
> > >>>
> > >>> The driver would check the appropriate register (tachyon
> > >>> registers) in the MMIO to determine the source of interrupts.
> > >>
> > >> OK, so that isn't it. Is there anything at these vectors:
> > >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it
> > >> should give you an inkling what device this is set for.
> > >
> > >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> > >
> > >'i' - Note 66 - 69
> > >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:127(----),
> > >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:126(----),
> > >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:125(----),
> > >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:124(----)
> > >
> > >
> > >'q'
> > >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> > >
> > >
> > >The same data with pv-ops kernel shows:
> > >
> > >'i'
> > >IRQ numbers stop at 65, no 66 - 69 present:
> > >
> > >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=0:289(----),
> > >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> > >type=PCI-MSI status=00000002 mapped, unbound
> > >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=0:287(----),
> > >(XEN) IO-APIC interrupt information:
> > >
> > >'q'
> > >(XEN) Interrupts { 32, 41-42, 47 }
> > >
> > >>
> > >>>
> > >>> > >
> > >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> > >>> > >
> > >124: 760415 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >125: 762234 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >126: 764180 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >127: 764164 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> >
> > >>> > Can you provide the full dmesg output?
> > >>>
> > >>> Attached.
> > >>>
> > >>> Some possibly related messages on dom0 console:
> > >>>
> > >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 ->
> > >>> 0003) [ 1882.269800] xen: registering gsi 32 triggering 0 polarity
> > >>> 1 [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32 [
> > >>> 1882.269834] xen: --> irq=32 [ 1882.269841] Already setup the GSI
> > >>> :32 [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32
> > >>> (level, low) -> IRQ 32 [ 1882.269866] pciback 0000:07:00.0:
> > >>> setting latency timer to 64 [ 1882.270463] pciback 0000:07:00.0:
> > >>> Driver tried to write to a read-only configuration space field at
> > >>> offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>
> > >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> > >> to find out what is at the configuration space. You could enable it
> > >> using the permissive attribute.
> > >>
> > >>> [ 1882.270465] 1) see permissive attribute in sysfs [ 1882.270467]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> > >>> [ 1882.270625] alloc kstat_irqs on node 0
> > >>
> > >> So for 478: what do you see? xen-pciback I presume?
> > >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 ->
> > >>> 0003) [ 1882.348433] xen: registering gsi 42 triggering 0 polarity
> > >>> 1 [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42 [
> > >>> 1882.348445] xen: --> irq=42 [ 1882.348472] Already setup the GSI
> > >>> :42 [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42
> > >>> (level, low) -> IRQ 42 [ 1882.348497] pciback 0000:07:00.1:
> > >>> setting latency timer to 64 [ 1882.349063] pciback 0000:07:00.1:
> > >>> Driver tried to write to a read-only configuration space field at
> > >>> offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>> [ 1882.349066] 1) see permissive attribute in sysfs [ 1882.349067]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> > >>> [ 1882.349215] alloc kstat_irqs on node 0
> > >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 ->
> > >>> 0003) [ 1882.402908] xen: registering gsi 47 triggering 0 polarity
> > >>> 1 [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47 [
> > >>> 1882.402916] xen: --> irq=47 [ 1882.402921] Already setup the GSI
> > >>> :47 [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47
> > >>> (level, low) -> IRQ 47 [ 1882.402938] pciback 0000:07:00.2:
> > >>> setting latency timer to 64 [ 1882.403280] pciback 0000:07:00.2:
> > >>> Driver tried to write to a read-only configuration space field at
> > >>> offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>> [ 1882.403282] 1) see permissive attribute in sysfs [ 1882.403282]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> > >>> [ 1882.403386] alloc kstat_irqs on node 0
> > >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > >>> fault addr e6f80000, iommu reg = ffff82c3fff57000
> > >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
> > >>> (XEN) root_entry = ffff83019ff70000
> > >>> (XEN) root_entry[7] = 19cf52001
> > >>> (XEN) context = ffff83019cf52000
> > >>> (XEN) context[0] = 102_706dc005
> > >>> (XEN) l4 = ffff8300706dc000
> > >>> (XEN) l4_index = 0
> > >>> (XEN) l4[0] = 706db003
> > >>> (XEN) l3 = ffff8300706db000
> > >>> (XEN) l3_index = 3
> > >>> (XEN) l3[3] = 702b6003
> > >>> (XEN) l2 = ffff8300702b6000
> > >>> (XEN) l2_index = 137
> > >>> (XEN) l2[137] = 0
> > >>> (XEN) l2[137] not present
> > >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0
> > >>> [ec=0000]
> > >>
> > >> That is not good. What changed from your earlier emails that this was triggered?
> > >
> > >Nothing
> > >> Or was it triggered all along?
> > >
> > >Yes, I just included it for completeness
> > >
> > >> What happens if you run the system without the iommu enabled?
> > >
> > >Haven't tried yet. Will check that next.
> > >
> > >-Bruce
> > >
> > >_______________________________________________
> > >Xen-devel mailing list
> > >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
> > >http://lists.xensource.com/xen-devel
> >
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 20:14 ` Konrad Rzeszutek Wilk
@ 2010-09-28 20:38 ` Lin, Ray
0 siblings, 0 replies; 42+ messages in thread
From: Lin, Ray @ 2010-09-28 20:38 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: xen-devel@lists.xensource.com, Bruce Edge, JBeulich@novell.com,
Jiang, Yunhong
The physical address (0xc0049c) is not the BAR of the PCI device. It resides in main memory. Is there any restriction to do the DMA Write to main memory in pvops kernel ?
-Ray
-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
Sent: Tuesday, September 28, 2010 1:15 PM
To: Lin, Ray
Cc: JBeulich@novell.com; xen-devel@lists.xensource.com; Jiang, Yunhong; Bruce Edge
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Tue, Sep 28, 2010 at 12:35:12PM -0600, Lin, Ray wrote:
>
> > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > fault addr c00000, iommu reg = ffff82c3fff57000
>
> The driver gets the physical addr 0xc0049c thru kernel function virt_to_phys() and set the dma address of Tachyon chip with this address. This address translation is also involved with SWIOTLB library. Is there any issue related with SWIOTLB in pvops kernel ?
If the driver is using pci_map_page, which goes through the Xen-SWIOTLB library, then it works correctly (the Xen-SWIOTLB does a PFN->MFN translation to give you the bus address).
I presume the physical address (0xc0049c) is the BAR of the PCI device, right?
There are no issues with the Xen-SWIOTLB in the pvops kernel.
>
>
>
>
> -Ray
>
>
>
>
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Tuesday, September 28, 2010 9:19 AM
> To: Lin, Ray; JBeulich@novell.com
> Cc: Bruce Edge; Jiang, Yunhong; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> on Nehalem
>
> On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
> > I just checked the "xen dmesg". Look like DMA/iommu is the root cause of this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA write to a dword memory location to indicate the source of interrupt. What iommu option do you recommend to use ?
>
> Lets get Jan involved in this discussion.
>
> Jan, would some of your patches that inhibit the MSI write affect this in a PV guest?
>
> >
> > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > fault addr c00000, iommu reg = ffff82c3fff57000
> > (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
> > (XEN) root_entry = ffff83019ff70000
> > (XEN) root_entry[7] = 19cf52001
> > (XEN) context = ffff83019cf52000
> > (XEN) context[0] = 102_706dc005
> > (XEN) l4 = ffff8300706dc000
> > (XEN) l4_index = 0
> > (XEN) l4[0] = 706db003
> > (XEN) l3 = ffff8300706db000
> > (XEN) l3_index = 0
> > (XEN) l3[0] = 706da003
> > (XEN) l2 = ffff8300706da000
> > (XEN) l2_index = 6
> > (XEN) l2[6] = 0
> >
> >
> > -Ray
> >
> >
> > ________________________________
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce
> > Edge
> > Sent: Monday, September 27, 2010 9:46 PM
> > To: Jiang, Yunhong
> > Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
> > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > on Nehalem
> >
> > On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > "xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
> >
> > I looked at the xm dmesg output and there's nothing more than what I already provided, aside from a bunch of commands from me poking at it.
> >
> > -Bruce
> >
> >
> > Thanks
> > --jyh
> >
> > From: Bruce Edge
> > [mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
> > Sent: Tuesday, September 28, 2010 11:16 AM
> > To: Jiang, Yunhong
> > Cc: Konrad Rzeszutek Wilk;
> > xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> >
> > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > on Nehalem
> >
> > On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
> >
> > Yes, there is 1 quad port card is this sytem:
> >
> > 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> >
> >
> > Also is it possible to share the xen output?
> >
> > I attached the dom0 boot output. Let me know if you wanted something else.
> >
> > Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
> >
> > [ 1817.684097] ------------[ cut here ]------------ [ 1817.684113]
> > WARNING: at kernel/lockdep.c:2323
> > trace_hardirqs_on_caller+0x12f/0x190()
> > [ 1817.684119] Hardware name: ProLiant DL380 G6 [ 1817.684122]
> > Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev
> > fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon
> > ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1 [ 1817.684195] Call Trace:
> > [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
> > trace_hardirqs_on_caller+0x12f/0x190
> > [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
> > [ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40 [
> > 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20 [
> > 1817.684229] [<ffffffff810aa18f>]
> > trace_hardirqs_on_caller+0x12f/0x190
> > [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10 [
> > 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40 [
> > 1817.684266] [<ffffffff813c4fc5>]
> > add_to_net_schedule_list_tail+0x85/0xd0
> > [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160 [
> > 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180 [
> > 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170 [
> > 1817.684291] [<ffffffff813b8d7f>]
> > __xen_evtchn_do_upcall+0x1bf/0x1f0
> > [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
> > [ 1817.684304] [<ffffffff8101647e>]
> > xen_do_hypervisor_callback+0x1e/0x30
> > [ 1817.684308] <EOI> [<ffffffff8100940a>] ?
> > hypercall_page+0x40a/0x1010 [ 1817.684319] [<ffffffff8100940a>] ?
> > hypercall_page+0x40a/0x1010 [ 1817.684325] [<ffffffff813bce54>] ?
> > xb_write+0x1e4/0x290 [ 1817.684330] [<ffffffff813bd8ca>] ?
> > xs_talkv+0x6a/0x1f0 [ 1817.684336] [<ffffffff813bd8d8>] ?
> > xs_talkv+0x78/0x1f0 [ 1817.684341] [<ffffffff813bdbcd>] ?
> > xs_single+0x4d/0x60 [ 1817.684346] [<ffffffff813be502>] ?
> > xenbus_read+0x52/0x80 [ 1817.684352] [<ffffffff813c87fc>] ?
> > frontend_changed+0x48c/0x770 [ 1817.684358] [<ffffffff813bf76d>] ?
> > xenbus_otherend_changed+0xdd/0x1b0
> > [ 1817.684365] [<ffffffff8101122f>] ?
> > xen_restore_fl_direct_end+0x0/0x1 [ 1817.684371]
> > [<ffffffff810ac830>] ? lock_release+0xb0/0x230 [ 1817.684376] [<ffffffff813bfae0>] ?
> > frontend_changed+0x10/0x20 [ 1817.684382] [<ffffffff813bd4f5>] ?
> > xenwatch_thread+0x55/0x160 [ 1817.684389] [<ffffffff81093400>] ?
> > autoremove_wake_function+0x0/0x40 [ 1817.684394]
> > [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160 [ 1817.684400] [<ffffffff81093086>] ?
> > kthread+0x96/0xb0 [ 1817.684405] [<ffffffff8101632a>] ?
> > child_rip+0xa/0x20 [ 1817.684410] [<ffffffff81015c90>] ?
> > restore_args+0x0/0x30 [ 1817.684415] [<ffffffff81016320>] ?
> > child_rip+0x0/0x20
> >
> > -Bruce
> >
> >
> >
> > Thanks
> > --jyh
> >
> > >-----Original Message-----
> > >From:
> > >xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.
> > >xensource.com>
> > >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-boun
> > >ce s@lists.xensource.com>] On Behalf Of Bruce Edge
> > >Sent: Tuesday, September 28, 2010 7:54 AM
> > >To: Konrad Rzeszutek Wilk
> > >Cc:
> > >xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> > >Subject: Re: [Xen-devel] pv-ops domU not working with MSI
> > >interrupts on Nehalem
> > >
> > >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> > ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> > >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> > >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > >>> >
> > >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> > >>> > > One of our developers who is working on a tachyon driver is
> > >>> > > complaining that the pvops domU kernel is not working for
> > >>> > > these MSI interrupts.
> > >>> > > This is using the current head of xen/2.6.32.x on both a
> > >>> > > single Nahelam 920 and a dual E5540. This behavior is
> > >>> > > consistent with Xen 4.0.1, 4.0.2.rc1-pre and 4.1.
> > >>> > >
> > >>> > > Here are his comments:
> > >>> > >
> > >>> > > - the driver has no problem to enable msi interrupt and
> > >>> > > request the interrupt through kernel functions
> > >>> > > pci_enable_msi & request_irq
> > >>> >
> > >>> > What shows up in the Xen console when you send the 'q' key?
> > >>> > Does it show that the vector is assigned to the appropiate guest?
> > >>>
> > >>> The Xen console q key shows that the domU is assigned:
> > >>>
> > >>> (XEN) Interrupts { 32, 41-42, 47 }
> > >>
> > >> Aha!
> > >>
> > >>>
> > >>> but the domU thinks it has:
> > >>>
> > >>> 124/125/126/127
> > >>>
> > >>> Is there some mapping that's taking place, or is this plain wrong?
> > >>
> > >> That looks wrong. The IRQ numbers (even though they are MSI
> > >> vectors) are setup as IRQ numbers in the DomU guest. You should
> > >> have seen
> > >>
> > >> 32:
> > >> 41:
> > >> 42:
> > >> 47:
> > >> in you /proc/interrupts on your DomU guest.
> > >>
> > >> I wonder what broke - can you use
> > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http:/
> > >/g it.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> > >
> > >Please forgive the git ignorance.
> > >
> > >Is this the right syntax?
> > >
> > >git clone
> > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.
> > >32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifron
> > >t-
> > >2.6.32>
> > >linux-2.6.32-pv-pcifront
> > >
> > >Initialized empty Git repository in
> > >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.
> > >gi
> > >t/
> > >fatal: The remote end hung up unexpectedly
> > >
> > >Or:
> > >
> > > git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http:
> > > // git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > >
> > >Initialized empty Git repository in
> > >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> > >remote: error: Could not read
> > >59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> > >remote: fatal: Failed to traverse parents of commit
> > >979e121cb348add17ed8171bf447b27a3a9d1be3
> > >remote: aborting due to possible repository corruption on the remote side.
> > >fatal: early EOF
> > >fatal: index-pack failed
> > >
> > >>
> > >> It has the latest pcifront driver but without the PVonHVM
> > >> enhancments so we can try to eliminate the PvONHVM logic out of the picture.
> > >>
> > >>>
> > >>> >
> > >>> > > - the interrupt does happen. But the interrupt service
> > >>> > > routine of tachyon driver doesn't detect any interrupt
> > >>> > > status related to this interrupt, which inhibits the tachyon
> > >>> > > chip from coming on-line. And there are high count of
> > >>> > > tachyon interrupt in /proc/interrupts
> > >>> >
> > >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate
> > >>> > register in the MMIO BAR?
> > >>> >
> > >>>
> > >>> The driver would check the appropriate register (tachyon
> > >>> registers) in the MMIO to determine the source of interrupts.
> > >>
> > >> OK, so that isn't it. Is there anything at these vectors:
> > >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it
> > >> should give you an inkling what device this is set for.
> > >
> > >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> > >
> > >'i' - Note 66 - 69
> > >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:127(----),
> > >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:126(----),
> > >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:125(----),
> > >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:124(----)
> > >
> > >
> > >'q'
> > >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> > >
> > >
> > >The same data with pv-ops kernel shows:
> > >
> > >'i'
> > >IRQ numbers stop at 65, no 66 - 69 present:
> > >
> > >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=0:289(----),
> > >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> > >type=PCI-MSI status=00000002 mapped, unbound
> > >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=0:287(----),
> > >(XEN) IO-APIC interrupt information:
> > >
> > >'q'
> > >(XEN) Interrupts { 32, 41-42, 47 }
> > >
> > >>
> > >>>
> > >>> > >
> > >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> > >>> > >
> > >124: 760415 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >125: 762234 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >126: 764180 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >127: 764164 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> >
> > >>> > Can you provide the full dmesg output?
> > >>>
> > >>> Attached.
> > >>>
> > >>> Some possibly related messages on dom0 console:
> > >>>
> > >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 ->
> > >>> 0003) [ 1882.269800] xen: registering gsi 32 triggering 0
> > >>> polarity
> > >>> 1 [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
> > >>> [ 1882.269834] xen: --> irq=32 [ 1882.269841] Already setup the
> > >>> GSI
> > >>> :32 [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32
> > >>> (level, low) -> IRQ 32 [ 1882.269866] pciback 0000:07:00.0:
> > >>> setting latency timer to 64 [ 1882.270463] pciback 0000:07:00.0:
> > >>> Driver tried to write to a read-only configuration space field
> > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>
> > >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> > >> to find out what is at the configuration space. You could enable
> > >> it using the permissive attribute.
> > >>
> > >>> [ 1882.270465] 1) see permissive attribute in sysfs [
> > >>> 1882.270467]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> > >>> [ 1882.270625] alloc kstat_irqs on node 0
> > >>
> > >> So for 478: what do you see? xen-pciback I presume?
> > >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 ->
> > >>> 0003) [ 1882.348433] xen: registering gsi 42 triggering 0
> > >>> polarity
> > >>> 1 [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
> > >>> [ 1882.348445] xen: --> irq=42 [ 1882.348472] Already setup the
> > >>> GSI
> > >>> :42 [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42
> > >>> (level, low) -> IRQ 42 [ 1882.348497] pciback 0000:07:00.1:
> > >>> setting latency timer to 64 [ 1882.349063] pciback 0000:07:00.1:
> > >>> Driver tried to write to a read-only configuration space field
> > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>> [ 1882.349066] 1) see permissive attribute in sysfs [
> > >>> 1882.349067]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> > >>> [ 1882.349215] alloc kstat_irqs on node 0
> > >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 ->
> > >>> 0003) [ 1882.402908] xen: registering gsi 47 triggering 0
> > >>> polarity
> > >>> 1 [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
> > >>> [ 1882.402916] xen: --> irq=47 [ 1882.402921] Already setup the
> > >>> GSI
> > >>> :47 [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47
> > >>> (level, low) -> IRQ 47 [ 1882.402938] pciback 0000:07:00.2:
> > >>> setting latency timer to 64 [ 1882.403280] pciback 0000:07:00.2:
> > >>> Driver tried to write to a read-only configuration space field
> > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>> [ 1882.403282] 1) see permissive attribute in sysfs [
> > >>> 1882.403282]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> > >>> [ 1882.403386] alloc kstat_irqs on node 0
> > >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending
> > >>> Fault
> > >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device
> > >>> [07:00.0] fault addr e6f80000, iommu reg = ffff82c3fff57000
> > >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
> > >>> (XEN) root_entry = ffff83019ff70000
> > >>> (XEN) root_entry[7] = 19cf52001
> > >>> (XEN) context = ffff83019cf52000
> > >>> (XEN) context[0] = 102_706dc005
> > >>> (XEN) l4 = ffff8300706dc000
> > >>> (XEN) l4_index = 0
> > >>> (XEN) l4[0] = 706db003
> > >>> (XEN) l3 = ffff8300706db000
> > >>> (XEN) l3_index = 3
> > >>> (XEN) l3[3] = 702b6003
> > >>> (XEN) l2 = ffff8300702b6000
> > >>> (XEN) l2_index = 137
> > >>> (XEN) l2[137] = 0
> > >>> (XEN) l2[137] not present
> > >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0
> > >>> [ec=0000]
> > >>
> > >> That is not good. What changed from your earlier emails that this was triggered?
> > >
> > >Nothing
> > >> Or was it triggered all along?
> > >
> > >Yes, I just included it for completeness
> > >
> > >> What happens if you run the system without the iommu enabled?
> > >
> > >Haven't tried yet. Will check that next.
> > >
> > >-Bruce
> > >
> > >_______________________________________________
> > >Xen-devel mailing list
> > >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
> > >http://lists.xensource.com/xen-devel
> >
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
@ 2010-09-28 23:25 Lin, Ray
2010-09-28 23:57 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 42+ messages in thread
From: Lin, Ray @ 2010-09-28 23:25 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: xen-devel@lists.xensource.com, Bruce Edge, JBeulich@novell.com,
Jiang, Yunhong
Here is how the memory is allocated for the DMA address in domU,
Non-NUMA:
get_free_pages((in_interrupt() ? GFP_ATOMIC : GFP_KERNEL)|GFP_DMA32, order))
NUMA:
alloc_pages_node(region->node, (in_interrupt() ? GFP_ATOMIC : GFP_KERNEL)|GFP_DMA32, order)
Does this way work for pvops kernel ?
-Ray
-----Original Message-----
From: Lin, Ray
Sent: Tuesday, September 28, 2010 1:38 PM
To: 'Konrad Rzeszutek Wilk'
Cc: JBeulich@novell.com; xen-devel@lists.xensource.com; Jiang, Yunhong; Bruce Edge
Subject: RE: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
The physical address (0xc0049c) is not the BAR of the PCI device. It resides in main memory. Is there any restriction to do the DMA Write to main memory in pvops kernel ?
-Ray
-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
Sent: Tuesday, September 28, 2010 1:15 PM
To: Lin, Ray
Cc: JBeulich@novell.com; xen-devel@lists.xensource.com; Jiang, Yunhong; Bruce Edge
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Tue, Sep 28, 2010 at 12:35:12PM -0600, Lin, Ray wrote:
>
> > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > fault addr c00000, iommu reg = ffff82c3fff57000
>
> The driver gets the physical addr 0xc0049c thru kernel function virt_to_phys() and set the dma address of Tachyon chip with this address. This address translation is also involved with SWIOTLB library. Is there any issue related with SWIOTLB in pvops kernel ?
If the driver is using pci_map_page, which goes through the Xen-SWIOTLB library, then it works correctly (the Xen-SWIOTLB does a PFN->MFN translation to give you the bus address).
I presume the physical address (0xc0049c) is the BAR of the PCI device, right?
There are no issues with the Xen-SWIOTLB in the pvops kernel.
>
>
>
>
> -Ray
>
>
>
>
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Tuesday, September 28, 2010 9:19 AM
> To: Lin, Ray; JBeulich@novell.com
> Cc: Bruce Edge; Jiang, Yunhong; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> on Nehalem
>
> On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
> > I just checked the "xen dmesg". Look like DMA/iommu is the root cause of this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA write to a dword memory location to indicate the source of interrupt. What iommu option do you recommend to use ?
>
> Lets get Jan involved in this discussion.
>
> Jan, would some of your patches that inhibit the MSI write affect this in a PV guest?
>
> >
> > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > fault addr c00000, iommu reg = ffff82c3fff57000
> > (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
> > (XEN) root_entry = ffff83019ff70000
> > (XEN) root_entry[7] = 19cf52001
> > (XEN) context = ffff83019cf52000
> > (XEN) context[0] = 102_706dc005
> > (XEN) l4 = ffff8300706dc000
> > (XEN) l4_index = 0
> > (XEN) l4[0] = 706db003
> > (XEN) l3 = ffff8300706db000
> > (XEN) l3_index = 0
> > (XEN) l3[0] = 706da003
> > (XEN) l2 = ffff8300706da000
> > (XEN) l2_index = 6
> > (XEN) l2[6] = 0
> >
> >
> > -Ray
> >
> >
> > ________________________________
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce
> > Edge
> > Sent: Monday, September 27, 2010 9:46 PM
> > To: Jiang, Yunhong
> > Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
> > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > on Nehalem
> >
> > On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > "xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
> >
> > I looked at the xm dmesg output and there's nothing more than what I already provided, aside from a bunch of commands from me poking at it.
> >
> > -Bruce
> >
> >
> > Thanks
> > --jyh
> >
> > From: Bruce Edge
> > [mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
> > Sent: Tuesday, September 28, 2010 11:16 AM
> > To: Jiang, Yunhong
> > Cc: Konrad Rzeszutek Wilk;
> > xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> >
> > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > on Nehalem
> >
> > On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
> >
> > Yes, there is 1 quad port card is this sytem:
> >
> > 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> >
> >
> > Also is it possible to share the xen output?
> >
> > I attached the dom0 boot output. Let me know if you wanted something else.
> >
> > Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
> >
> > [ 1817.684097] ------------[ cut here ]------------ [ 1817.684113]
> > WARNING: at kernel/lockdep.c:2323
> > trace_hardirqs_on_caller+0x12f/0x190()
> > [ 1817.684119] Hardware name: ProLiant DL380 G6 [ 1817.684122]
> > Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev
> > fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon
> > ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1 [ 1817.684195] Call Trace:
> > [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
> > trace_hardirqs_on_caller+0x12f/0x190
> > [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
> > [ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40 [
> > 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20 [
> > 1817.684229] [<ffffffff810aa18f>]
> > trace_hardirqs_on_caller+0x12f/0x190
> > [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10 [
> > 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40 [
> > 1817.684266] [<ffffffff813c4fc5>]
> > add_to_net_schedule_list_tail+0x85/0xd0
> > [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160 [
> > 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180 [
> > 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170 [
> > 1817.684291] [<ffffffff813b8d7f>]
> > __xen_evtchn_do_upcall+0x1bf/0x1f0
> > [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
> > [ 1817.684304] [<ffffffff8101647e>]
> > xen_do_hypervisor_callback+0x1e/0x30
> > [ 1817.684308] <EOI> [<ffffffff8100940a>] ?
> > hypercall_page+0x40a/0x1010 [ 1817.684319] [<ffffffff8100940a>] ?
> > hypercall_page+0x40a/0x1010 [ 1817.684325] [<ffffffff813bce54>] ?
> > xb_write+0x1e4/0x290 [ 1817.684330] [<ffffffff813bd8ca>] ?
> > xs_talkv+0x6a/0x1f0 [ 1817.684336] [<ffffffff813bd8d8>] ?
> > xs_talkv+0x78/0x1f0 [ 1817.684341] [<ffffffff813bdbcd>] ?
> > xs_single+0x4d/0x60 [ 1817.684346] [<ffffffff813be502>] ?
> > xenbus_read+0x52/0x80 [ 1817.684352] [<ffffffff813c87fc>] ?
> > frontend_changed+0x48c/0x770 [ 1817.684358] [<ffffffff813bf76d>] ?
> > xenbus_otherend_changed+0xdd/0x1b0
> > [ 1817.684365] [<ffffffff8101122f>] ?
> > xen_restore_fl_direct_end+0x0/0x1 [ 1817.684371]
> > [<ffffffff810ac830>] ? lock_release+0xb0/0x230 [ 1817.684376] [<ffffffff813bfae0>] ?
> > frontend_changed+0x10/0x20 [ 1817.684382] [<ffffffff813bd4f5>] ?
> > xenwatch_thread+0x55/0x160 [ 1817.684389] [<ffffffff81093400>] ?
> > autoremove_wake_function+0x0/0x40 [ 1817.684394]
> > [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160 [ 1817.684400] [<ffffffff81093086>] ?
> > kthread+0x96/0xb0 [ 1817.684405] [<ffffffff8101632a>] ?
> > child_rip+0xa/0x20 [ 1817.684410] [<ffffffff81015c90>] ?
> > restore_args+0x0/0x30 [ 1817.684415] [<ffffffff81016320>] ?
> > child_rip+0x0/0x20
> >
> > -Bruce
> >
> >
> >
> > Thanks
> > --jyh
> >
> > >-----Original Message-----
> > >From:
> > >xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.
> > >xensource.com>
> > >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-boun
> > >ce s@lists.xensource.com>] On Behalf Of Bruce Edge
> > >Sent: Tuesday, September 28, 2010 7:54 AM
> > >To: Konrad Rzeszutek Wilk
> > >Cc:
> > >xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> > >Subject: Re: [Xen-devel] pv-ops domU not working with MSI
> > >interrupts on Nehalem
> > >
> > >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> > ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> > >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> > >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > >>> >
> > >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> > >>> > > One of our developers who is working on a tachyon driver is
> > >>> > > complaining that the pvops domU kernel is not working for
> > >>> > > these MSI interrupts.
> > >>> > > This is using the current head of xen/2.6.32.x on both a
> > >>> > > single Nahelam 920 and a dual E5540. This behavior is
> > >>> > > consistent with Xen 4.0.1, 4.0.2.rc1-pre and 4.1.
> > >>> > >
> > >>> > > Here are his comments:
> > >>> > >
> > >>> > > - the driver has no problem to enable msi interrupt and
> > >>> > > request the interrupt through kernel functions
> > >>> > > pci_enable_msi & request_irq
> > >>> >
> > >>> > What shows up in the Xen console when you send the 'q' key?
> > >>> > Does it show that the vector is assigned to the appropiate guest?
> > >>>
> > >>> The Xen console q key shows that the domU is assigned:
> > >>>
> > >>> (XEN) Interrupts { 32, 41-42, 47 }
> > >>
> > >> Aha!
> > >>
> > >>>
> > >>> but the domU thinks it has:
> > >>>
> > >>> 124/125/126/127
> > >>>
> > >>> Is there some mapping that's taking place, or is this plain wrong?
> > >>
> > >> That looks wrong. The IRQ numbers (even though they are MSI
> > >> vectors) are setup as IRQ numbers in the DomU guest. You should
> > >> have seen
> > >>
> > >> 32:
> > >> 41:
> > >> 42:
> > >> 47:
> > >> in you /proc/interrupts on your DomU guest.
> > >>
> > >> I wonder what broke - can you use
> > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http:/
> > >/g it.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> > >
> > >Please forgive the git ignorance.
> > >
> > >Is this the right syntax?
> > >
> > >git clone
> > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.
> > >32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifron
> > >t-
> > >2.6.32>
> > >linux-2.6.32-pv-pcifront
> > >
> > >Initialized empty Git repository in
> > >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.
> > >gi
> > >t/
> > >fatal: The remote end hung up unexpectedly
> > >
> > >Or:
> > >
> > > git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http:
> > > // git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > >
> > >Initialized empty Git repository in
> > >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> > >remote: error: Could not read
> > >59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> > >remote: fatal: Failed to traverse parents of commit
> > >979e121cb348add17ed8171bf447b27a3a9d1be3
> > >remote: aborting due to possible repository corruption on the remote side.
> > >fatal: early EOF
> > >fatal: index-pack failed
> > >
> > >>
> > >> It has the latest pcifront driver but without the PVonHVM
> > >> enhancments so we can try to eliminate the PvONHVM logic out of the picture.
> > >>
> > >>>
> > >>> >
> > >>> > > - the interrupt does happen. But the interrupt service
> > >>> > > routine of tachyon driver doesn't detect any interrupt
> > >>> > > status related to this interrupt, which inhibits the tachyon
> > >>> > > chip from coming on-line. And there are high count of
> > >>> > > tachyon interrupt in /proc/interrupts
> > >>> >
> > >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate
> > >>> > register in the MMIO BAR?
> > >>> >
> > >>>
> > >>> The driver would check the appropriate register (tachyon
> > >>> registers) in the MMIO to determine the source of interrupts.
> > >>
> > >> OK, so that isn't it. Is there anything at these vectors:
> > >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it
> > >> should give you an inkling what device this is set for.
> > >
> > >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> > >
> > >'i' - Note 66 - 69
> > >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:127(----),
> > >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:126(----),
> > >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:125(----),
> > >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=10:124(----)
> > >
> > >
> > >'q'
> > >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> > >
> > >
> > >The same data with pv-ops kernel shows:
> > >
> > >'i'
> > >IRQ numbers stop at 65, no 66 - 69 present:
> > >
> > >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=0:289(----),
> > >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> > >type=PCI-MSI status=00000002 mapped, unbound
> > >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> > >type=PCI-MSI status=00000010 in-flight=0
> > >domain-list=0:287(----),
> > >(XEN) IO-APIC interrupt information:
> > >
> > >'q'
> > >(XEN) Interrupts { 32, 41-42, 47 }
> > >
> > >>
> > >>>
> > >>> > >
> > >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> > >>> > >
> > >124: 760415 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >125: 762234 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >126: 764180 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> > >
> > >127: 764164 0 0 0 0
> > > 0
> > >>> > > 0 0 0 0 0
> > > 0
> > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > >>> >
> > >>> > Can you provide the full dmesg output?
> > >>>
> > >>> Attached.
> > >>>
> > >>> Some possibly related messages on dom0 console:
> > >>>
> > >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 ->
> > >>> 0003) [ 1882.269800] xen: registering gsi 32 triggering 0
> > >>> polarity
> > >>> 1 [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
> > >>> [ 1882.269834] xen: --> irq=32 [ 1882.269841] Already setup the
> > >>> GSI
> > >>> :32 [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32
> > >>> (level, low) -> IRQ 32 [ 1882.269866] pciback 0000:07:00.0:
> > >>> setting latency timer to 64 [ 1882.270463] pciback 0000:07:00.0:
> > >>> Driver tried to write to a read-only configuration space field
> > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>
> > >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> > >> to find out what is at the configuration space. You could enable
> > >> it using the permissive attribute.
> > >>
> > >>> [ 1882.270465] 1) see permissive attribute in sysfs [
> > >>> 1882.270467]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> > >>> [ 1882.270625] alloc kstat_irqs on node 0
> > >>
> > >> So for 478: what do you see? xen-pciback I presume?
> > >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 ->
> > >>> 0003) [ 1882.348433] xen: registering gsi 42 triggering 0
> > >>> polarity
> > >>> 1 [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
> > >>> [ 1882.348445] xen: --> irq=42 [ 1882.348472] Already setup the
> > >>> GSI
> > >>> :42 [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42
> > >>> (level, low) -> IRQ 42 [ 1882.348497] pciback 0000:07:00.1:
> > >>> setting latency timer to 64 [ 1882.349063] pciback 0000:07:00.1:
> > >>> Driver tried to write to a read-only configuration space field
> > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>> [ 1882.349066] 1) see permissive attribute in sysfs [
> > >>> 1882.349067]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> > >>> [ 1882.349215] alloc kstat_irqs on node 0
> > >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 ->
> > >>> 0003) [ 1882.402908] xen: registering gsi 47 triggering 0
> > >>> polarity
> > >>> 1 [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
> > >>> [ 1882.402916] xen: --> irq=47 [ 1882.402921] Already setup the
> > >>> GSI
> > >>> :47 [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47
> > >>> (level, low) -> IRQ 47 [ 1882.402938] pciback 0000:07:00.2:
> > >>> setting latency timer to 64 [ 1882.403280] pciback 0000:07:00.2:
> > >>> Driver tried to write to a read-only configuration space field
> > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > >>> problems with your device:
> > >>> [ 1882.403282] 1) see permissive attribute in sysfs [
> > >>> 1882.403282]
> > >>> 2) report problems to the xen-devel mailing list along with
> > >>> details of your device obtained from lspci.
> > >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> > >>> [ 1882.403386] alloc kstat_irqs on node 0
> > >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending
> > >>> Fault
> > >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device
> > >>> [07:00.0] fault addr e6f80000, iommu reg = ffff82c3fff57000
> > >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
> > >>> (XEN) root_entry = ffff83019ff70000
> > >>> (XEN) root_entry[7] = 19cf52001
> > >>> (XEN) context = ffff83019cf52000
> > >>> (XEN) context[0] = 102_706dc005
> > >>> (XEN) l4 = ffff8300706dc000
> > >>> (XEN) l4_index = 0
> > >>> (XEN) l4[0] = 706db003
> > >>> (XEN) l3 = ffff8300706db000
> > >>> (XEN) l3_index = 3
> > >>> (XEN) l3[3] = 702b6003
> > >>> (XEN) l2 = ffff8300702b6000
> > >>> (XEN) l2_index = 137
> > >>> (XEN) l2[137] = 0
> > >>> (XEN) l2[137] not present
> > >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0
> > >>> [ec=0000]
> > >>
> > >> That is not good. What changed from your earlier emails that this was triggered?
> > >
> > >Nothing
> > >> Or was it triggered all along?
> > >
> > >Yes, I just included it for completeness
> > >
> > >> What happens if you run the system without the iommu enabled?
> > >
> > >Haven't tried yet. Will check that next.
> > >
> > >-Bruce
> > >
> > >_______________________________________________
> > >Xen-devel mailing list
> > >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
> > >http://lists.xensource.com/xen-devel
> >
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 23:25 Lin, Ray
@ 2010-09-28 23:57 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-09-28 23:57 UTC (permalink / raw)
To: Lin, Ray
Cc: xen-devel@lists.xensource.com, Bruce Edge, JBeulich@novell.com,
Jiang, Yunhong
On Tue, Sep 28, 2010 at 05:25:48PM -0600, Lin, Ray wrote:
>
>
> Here is how the memory is allocated for the DMA address in domU,
>
> Non-NUMA:
> get_free_pages((in_interrupt() ? GFP_ATOMIC : GFP_KERNEL)|GFP_DMA32, order))
>
> NUMA:
> alloc_pages_node(region->node, (in_interrupt() ? GFP_ATOMIC : GFP_KERNEL)|GFP_DMA32, order)
>
>
> Does this way work for pvops kernel ?
Sure, as long as you physical address you provide to the device for DMA has
gone through the PCI API - meaning you did pci_map_page or pci_map_<whatever>
>
>
> -Ray
>
>
> -----Original Message-----
> From: Lin, Ray
> Sent: Tuesday, September 28, 2010 1:38 PM
> To: 'Konrad Rzeszutek Wilk'
> Cc: JBeulich@novell.com; xen-devel@lists.xensource.com; Jiang, Yunhong; Bruce Edge
> Subject: RE: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
>
> The physical address (0xc0049c) is not the BAR of the PCI device. It resides in main memory. Is there any restriction to do the DMA Write to main memory in pvops kernel ?
>
>
> -Ray
>
>
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Tuesday, September 28, 2010 1:15 PM
> To: Lin, Ray
> Cc: JBeulich@novell.com; xen-devel@lists.xensource.com; Jiang, Yunhong; Bruce Edge
> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
> On Tue, Sep 28, 2010 at 12:35:12PM -0600, Lin, Ray wrote:
> >
> > > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > > fault addr c00000, iommu reg = ffff82c3fff57000
> >
> > The driver gets the physical addr 0xc0049c thru kernel function virt_to_phys() and set the dma address of Tachyon chip with this address. This address translation is also involved with SWIOTLB library. Is there any issue related with SWIOTLB in pvops kernel ?
>
> If the driver is using pci_map_page, which goes through the Xen-SWIOTLB library, then it works correctly (the Xen-SWIOTLB does a PFN->MFN translation to give you the bus address).
>
> I presume the physical address (0xc0049c) is the BAR of the PCI device, right?
>
> There are no issues with the Xen-SWIOTLB in the pvops kernel.
>
> >
> >
> >
> >
> > -Ray
> >
> >
> >
> >
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > Sent: Tuesday, September 28, 2010 9:19 AM
> > To: Lin, Ray; JBeulich@novell.com
> > Cc: Bruce Edge; Jiang, Yunhong; xen-devel@lists.xensource.com
> > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > on Nehalem
> >
> > On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
> > > I just checked the "xen dmesg". Look like DMA/iommu is the root cause of this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA write to a dword memory location to indicate the source of interrupt. What iommu option do you recommend to use ?
> >
> > Lets get Jan involved in this discussion.
> >
> > Jan, would some of your patches that inhibit the MSI write affect this in a PV guest?
> >
> > >
> > > (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
> > > (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
> > > fault addr c00000, iommu reg = ffff82c3fff57000
> > > (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > > (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
> > > (XEN) root_entry = ffff83019ff70000
> > > (XEN) root_entry[7] = 19cf52001
> > > (XEN) context = ffff83019cf52000
> > > (XEN) context[0] = 102_706dc005
> > > (XEN) l4 = ffff8300706dc000
> > > (XEN) l4_index = 0
> > > (XEN) l4[0] = 706db003
> > > (XEN) l3 = ffff8300706db000
> > > (XEN) l3_index = 0
> > > (XEN) l3[0] = 706da003
> > > (XEN) l2 = ffff8300706da000
> > > (XEN) l2_index = 6
> > > (XEN) l2[6] = 0
> > >
> > >
> > > -Ray
> > >
> > >
> > > ________________________________
> > > From: xen-devel-bounces@lists.xensource.com
> > > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce
> > > Edge
> > > Sent: Monday, September 27, 2010 9:46 PM
> > > To: Jiang, Yunhong
> > > Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
> > > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > > on Nehalem
> > >
> > > On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > > "xm dmesg" should gives xen's boot log, and sometimes it contain some helpful information, I think, especially loglvl and guest_loglvl is set to all.
> > >
> > > I looked at the xm dmesg output and there's nothing more than what I already provided, aside from a bunch of commands from me poking at it.
> > >
> > > -Bruce
> > >
> > >
> > > Thanks
> > > --jyh
> > >
> > > From: Bruce Edge
> > > [mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
> > > Sent: Tuesday, September 28, 2010 11:16 AM
> > > To: Jiang, Yunhong
> > > Cc: Konrad Rzeszutek Wilk;
> > > xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> > >
> > > Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
> > > on Nehalem
> > >
> > > On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong <yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
> > > Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
> > >
> > > Yes, there is 1 quad port card is this sytem:
> > >
> > > 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > > 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > > 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > > 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
> > >
> > >
> > > Also is it possible to share the xen output?
> > >
> > > I attached the dom0 boot output. Let me know if you wanted something else.
> > >
> > > Also, here's the dom0 console output upon starting the VM: This lockdep error started with the release of 2.6.32.21. Note that I'm running the same kernel for the domU and dom0.
> > >
> > > [ 1817.684097] ------------[ cut here ]------------ [ 1817.684113]
> > > WARNING: at kernel/lockdep.c:2323
> > > trace_hardirqs_on_caller+0x12f/0x190()
> > > [ 1817.684119] Hardware name: ProLiant DL380 G6 [ 1817.684122]
> > > Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev
> > > fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon
> > > ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1 [ 1817.684195] Call Trace:
> > > [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
> > > trace_hardirqs_on_caller+0x12f/0x190
> > > [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
> > > [ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40 [
> > > 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20 [
> > > 1817.684229] [<ffffffff810aa18f>]
> > > trace_hardirqs_on_caller+0x12f/0x190
> > > [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10 [
> > > 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40 [
> > > 1817.684266] [<ffffffff813c4fc5>]
> > > add_to_net_schedule_list_tail+0x85/0xd0
> > > [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160 [
> > > 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180 [
> > > 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170 [
> > > 1817.684291] [<ffffffff813b8d7f>]
> > > __xen_evtchn_do_upcall+0x1bf/0x1f0
> > > [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
> > > [ 1817.684304] [<ffffffff8101647e>]
> > > xen_do_hypervisor_callback+0x1e/0x30
> > > [ 1817.684308] <EOI> [<ffffffff8100940a>] ?
> > > hypercall_page+0x40a/0x1010 [ 1817.684319] [<ffffffff8100940a>] ?
> > > hypercall_page+0x40a/0x1010 [ 1817.684325] [<ffffffff813bce54>] ?
> > > xb_write+0x1e4/0x290 [ 1817.684330] [<ffffffff813bd8ca>] ?
> > > xs_talkv+0x6a/0x1f0 [ 1817.684336] [<ffffffff813bd8d8>] ?
> > > xs_talkv+0x78/0x1f0 [ 1817.684341] [<ffffffff813bdbcd>] ?
> > > xs_single+0x4d/0x60 [ 1817.684346] [<ffffffff813be502>] ?
> > > xenbus_read+0x52/0x80 [ 1817.684352] [<ffffffff813c87fc>] ?
> > > frontend_changed+0x48c/0x770 [ 1817.684358] [<ffffffff813bf76d>] ?
> > > xenbus_otherend_changed+0xdd/0x1b0
> > > [ 1817.684365] [<ffffffff8101122f>] ?
> > > xen_restore_fl_direct_end+0x0/0x1 [ 1817.684371]
> > > [<ffffffff810ac830>] ? lock_release+0xb0/0x230 [ 1817.684376] [<ffffffff813bfae0>] ?
> > > frontend_changed+0x10/0x20 [ 1817.684382] [<ffffffff813bd4f5>] ?
> > > xenwatch_thread+0x55/0x160 [ 1817.684389] [<ffffffff81093400>] ?
> > > autoremove_wake_function+0x0/0x40 [ 1817.684394]
> > > [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160 [ 1817.684400] [<ffffffff81093086>] ?
> > > kthread+0x96/0xb0 [ 1817.684405] [<ffffffff8101632a>] ?
> > > child_rip+0xa/0x20 [ 1817.684410] [<ffffffff81015c90>] ?
> > > restore_args+0x0/0x30 [ 1817.684415] [<ffffffff81016320>] ?
> > > child_rip+0x0/0x20
> > >
> > > -Bruce
> > >
> > >
> > >
> > > Thanks
> > > --jyh
> > >
> > > >-----Original Message-----
> > > >From:
> > > >xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.
> > > >xensource.com>
> > > >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-boun
> > > >ce s@lists.xensource.com>] On Behalf Of Bruce Edge
> > > >Sent: Tuesday, September 28, 2010 7:54 AM
> > > >To: Konrad Rzeszutek Wilk
> > > >Cc:
> > > >xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
> > > >Subject: Re: [Xen-devel] pv-ops domU not working with MSI
> > > >interrupts on Nehalem
> > > >
> > > >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
> > > ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > > >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
> > > >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
> > > >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
> > > >>> >
> > > >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> > > >>> > > One of our developers who is working on a tachyon driver is
> > > >>> > > complaining that the pvops domU kernel is not working for
> > > >>> > > these MSI interrupts.
> > > >>> > > This is using the current head of xen/2.6.32.x on both a
> > > >>> > > single Nahelam 920 and a dual E5540. This behavior is
> > > >>> > > consistent with Xen 4.0.1, 4.0.2.rc1-pre and 4.1.
> > > >>> > >
> > > >>> > > Here are his comments:
> > > >>> > >
> > > >>> > > - the driver has no problem to enable msi interrupt and
> > > >>> > > request the interrupt through kernel functions
> > > >>> > > pci_enable_msi & request_irq
> > > >>> >
> > > >>> > What shows up in the Xen console when you send the 'q' key?
> > > >>> > Does it show that the vector is assigned to the appropiate guest?
> > > >>>
> > > >>> The Xen console q key shows that the domU is assigned:
> > > >>>
> > > >>> (XEN) Interrupts { 32, 41-42, 47 }
> > > >>
> > > >> Aha!
> > > >>
> > > >>>
> > > >>> but the domU thinks it has:
> > > >>>
> > > >>> 124/125/126/127
> > > >>>
> > > >>> Is there some mapping that's taking place, or is this plain wrong?
> > > >>
> > > >> That looks wrong. The IRQ numbers (even though they are MSI
> > > >> vectors) are setup as IRQ numbers in the DomU guest. You should
> > > >> have seen
> > > >>
> > > >> 32:
> > > >> 41:
> > > >> 42:
> > > >> 47:
> > > >> in you /proc/interrupts on your DomU guest.
> > > >>
> > > >> I wonder what broke - can you use
> > > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http:/
> > > >/g it.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > > >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
> > > >
> > > >Please forgive the git ignorance.
> > > >
> > > >Is this the right syntax?
> > > >
> > > >git clone
> > > >git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.
> > > >32<http://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifron
> > > >t-
> > > >2.6.32>
> > > >linux-2.6.32-pv-pcifront
> > > >
> > > >Initialized empty Git repository in
> > > >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.
> > > >gi
> > > >t/
> > > >fatal: The remote end hung up unexpectedly
> > > >
> > > >Or:
> > > >
> > > > git clone
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http:
> > > > // git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git>
> > > >
> > > >Initialized empty Git repository in
> > > >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> > > >remote: error: Could not read
> > > >59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> > > >remote: fatal: Failed to traverse parents of commit
> > > >979e121cb348add17ed8171bf447b27a3a9d1be3
> > > >remote: aborting due to possible repository corruption on the remote side.
> > > >fatal: early EOF
> > > >fatal: index-pack failed
> > > >
> > > >>
> > > >> It has the latest pcifront driver but without the PVonHVM
> > > >> enhancments so we can try to eliminate the PvONHVM logic out of the picture.
> > > >>
> > > >>>
> > > >>> >
> > > >>> > > - the interrupt does happen. But the interrupt service
> > > >>> > > routine of tachyon driver doesn't detect any interrupt
> > > >>> > > status related to this interrupt, which inhibits the tachyon
> > > >>> > > chip from coming on-line. And there are high count of
> > > >>> > > tachyon interrupt in /proc/interrupts
> > > >>> >
> > > >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate
> > > >>> > register in the MMIO BAR?
> > > >>> >
> > > >>>
> > > >>> The driver would check the appropriate register (tachyon
> > > >>> registers) in the MMIO to determine the source of interrupts.
> > > >>
> > > >> OK, so that isn't it. Is there anything at these vectors:
> > > >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it
> > > >> should give you an inkling what device this is set for.
> > > >
> > > >When I run a distro kernel in hvm mode, I get the expected irq mappings:
> > > >
> > > >'i' - Note 66 - 69
> > > >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> > > >type=PCI-MSI status=00000010 in-flight=0
> > > >domain-list=10:127(----),
> > > >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> > > >type=PCI-MSI status=00000010 in-flight=0
> > > >domain-list=10:126(----),
> > > >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> > > >type=PCI-MSI status=00000010 in-flight=0
> > > >domain-list=10:125(----),
> > > >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> > > >type=PCI-MSI status=00000010 in-flight=0
> > > >domain-list=10:124(----)
> > > >
> > > >
> > > >'q'
> > > >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
> > > >
> > > >
> > > >The same data with pv-ops kernel shows:
> > > >
> > > >'i'
> > > >IRQ numbers stop at 65, no 66 - 69 present:
> > > >
> > > >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
> > > >type=PCI-MSI status=00000010 in-flight=0
> > > >domain-list=0:289(----),
> > > >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
> > > >type=PCI-MSI status=00000002 mapped, unbound
> > > >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
> > > >type=PCI-MSI status=00000010 in-flight=0
> > > >domain-list=0:287(----),
> > > >(XEN) IO-APIC interrupt information:
> > > >
> > > >'q'
> > > >(XEN) Interrupts { 32, 41-42, 47 }
> > > >
> > > >>
> > > >>>
> > > >>> > >
> > > >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> > > >>> > >
> > > >124: 760415 0 0 0 0
> > > > 0
> > > >>> > > 0 0 0 0 0
> > > > 0
> > > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > > >>> > >
> > > >125: 762234 0 0 0 0
> > > > 0
> > > >>> > > 0 0 0 0 0
> > > > 0
> > > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > > >>> > >
> > > >126: 764180 0 0 0 0
> > > > 0
> > > >>> > > 0 0 0 0 0
> > > > 0
> > > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > > >>> > >
> > > >127: 764164 0 0 0 0
> > > > 0
> > > >>> > > 0 0 0 0 0
> > > > 0
> > > >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
> > > >>> >
> > > >>> > Can you provide the full dmesg output?
> > > >>>
> > > >>> Attached.
> > > >>>
> > > >>> Some possibly related messages on dom0 console:
> > > >>>
> > > >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 ->
> > > >>> 0003) [ 1882.269800] xen: registering gsi 32 triggering 0
> > > >>> polarity
> > > >>> 1 [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
> > > >>> [ 1882.269834] xen: --> irq=32 [ 1882.269841] Already setup the
> > > >>> GSI
> > > >>> :32 [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32
> > > >>> (level, low) -> IRQ 32 [ 1882.269866] pciback 0000:07:00.0:
> > > >>> setting latency timer to 64 [ 1882.270463] pciback 0000:07:00.0:
> > > >>> Driver tried to write to a read-only configuration space field
> > > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > > >>> problems with your device:
> > > >>
> > > >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
> > > >> to find out what is at the configuration space. You could enable
> > > >> it using the permissive attribute.
> > > >>
> > > >>> [ 1882.270465] 1) see permissive attribute in sysfs [
> > > >>> 1882.270467]
> > > >>> 2) report problems to the xen-devel mailing list along with
> > > >>> details of your device obtained from lspci.
> > > >>> [ 1882.270615] alloc irq_desc for 478 on node 0
> > > >>> [ 1882.270625] alloc kstat_irqs on node 0
> > > >>
> > > >> So for 478: what do you see? xen-pciback I presume?
> > > >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 ->
> > > >>> 0003) [ 1882.348433] xen: registering gsi 42 triggering 0
> > > >>> polarity
> > > >>> 1 [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
> > > >>> [ 1882.348445] xen: --> irq=42 [ 1882.348472] Already setup the
> > > >>> GSI
> > > >>> :42 [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42
> > > >>> (level, low) -> IRQ 42 [ 1882.348497] pciback 0000:07:00.1:
> > > >>> setting latency timer to 64 [ 1882.349063] pciback 0000:07:00.1:
> > > >>> Driver tried to write to a read-only configuration space field
> > > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > > >>> problems with your device:
> > > >>> [ 1882.349066] 1) see permissive attribute in sysfs [
> > > >>> 1882.349067]
> > > >>> 2) report problems to the xen-devel mailing list along with
> > > >>> details of your device obtained from lspci.
> > > >>> [ 1882.349205] alloc irq_desc for 477 on node 0
> > > >>> [ 1882.349215] alloc kstat_irqs on node 0
> > > >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 ->
> > > >>> 0003) [ 1882.402908] xen: registering gsi 47 triggering 0
> > > >>> polarity
> > > >>> 1 [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
> > > >>> [ 1882.402916] xen: --> irq=47 [ 1882.402921] Already setup the
> > > >>> GSI
> > > >>> :47 [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47
> > > >>> (level, low) -> IRQ 47 [ 1882.402938] pciback 0000:07:00.2:
> > > >>> setting latency timer to 64 [ 1882.403280] pciback 0000:07:00.2:
> > > >>> Driver tried to write to a read-only configuration space field
> > > >>> at offset 0x62, size 2. This may be harmless, but if you have
> > > >>> problems with your device:
> > > >>> [ 1882.403282] 1) see permissive attribute in sysfs [
> > > >>> 1882.403282]
> > > >>> 2) report problems to the xen-devel mailing list along with
> > > >>> details of your device obtained from lspci.
> > > >>> [ 1882.403380] alloc irq_desc for 476 on node 0
> > > >>> [ 1882.403386] alloc kstat_irqs on node 0
> > > >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending
> > > >>> Fault
> > > >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device
> > > >>> [07:00.0] fault addr e6f80000, iommu reg = ffff82c3fff57000
> > > >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
> > > >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
> > > >>> (XEN) root_entry = ffff83019ff70000
> > > >>> (XEN) root_entry[7] = 19cf52001
> > > >>> (XEN) context = ffff83019cf52000
> > > >>> (XEN) context[0] = 102_706dc005
> > > >>> (XEN) l4 = ffff8300706dc000
> > > >>> (XEN) l4_index = 0
> > > >>> (XEN) l4[0] = 706db003
> > > >>> (XEN) l3 = ffff8300706db000
> > > >>> (XEN) l3_index = 3
> > > >>> (XEN) l3[3] = 702b6003
> > > >>> (XEN) l2 = ffff8300702b6000
> > > >>> (XEN) l2_index = 137
> > > >>> (XEN) l2[137] = 0
> > > >>> (XEN) l2[137] not present
> > > >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0
> > > >>> [ec=0000]
> > > >>
> > > >> That is not good. What changed from your earlier emails that this was triggered?
> > > >
> > > >Nothing
> > > >> Or was it triggered all along?
> > > >
> > > >Yes, I just included it for completeness
> > > >
> > > >> What happens if you run the system without the iommu enabled?
> > > >
> > > >Haven't tried yet. Will check that next.
> > > >
> > > >-Bruce
> > > >
> > > >_______________________________________________
> > > >Xen-devel mailing list
> > > >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
> > > >http://lists.xensource.com/xen-devel
> > >
> > >
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 16:19 ` Konrad Rzeszutek Wilk
2010-09-28 18:35 ` Lin, Ray
@ 2010-09-29 0:53 ` Jiang, Yunhong
2010-09-30 16:30 ` Lin, Ray
1 sibling, 1 reply; 42+ messages in thread
From: Jiang, Yunhong @ 2010-09-29 0:53 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, Lin, Ray, JBeulich@novell.com
Cc: xen-devel@lists.xensource.com, Bruce Edge
>-----Original Message-----
>From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
>Sent: Wednesday, September 29, 2010 12:19 AM
>To: Lin, Ray; JBeulich@novell.com
>Cc: Bruce Edge; Jiang, Yunhong; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>
>On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
>> I just checked the "xen dmesg". Look like DMA/iommu is the root cause of
>this issue. In order to tell the source of interrupt, Tachyon chip needs to do the DMA
>write to a dword memory location to indicate the source of interrupt. What iommu
>option do you recommend to use ?
>
>Lets get Jan involved in this discussion.
>
>Jan, would some of your patches that inhibit the MSI write affect this
>in a PV guest?
As far as I can tell, this patch should not cause issue to VT-d side, instead, it's more about access from CPU.
Can you try to pass a option to xen as "iommu=off", and check the result?
Thanks
--jyh
>
>>
>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0] fault addr
>c00000, iommu reg = ffff82c3fff57000
>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
>> (XEN) root_entry = ffff83019ff70000
>> (XEN) root_entry[7] = 19cf52001
>> (XEN) context = ffff83019cf52000
>> (XEN) context[0] = 102_706dc005
>> (XEN) l4 = ffff8300706dc000
>> (XEN) l4_index = 0
>> (XEN) l4[0] = 706db003
>> (XEN) l3 = ffff8300706db000
>> (XEN) l3_index = 0
>> (XEN) l3[0] = 706da003
>> (XEN) l2 = ffff8300706da000
>> (XEN) l2_index = 6
>> (XEN) l2[6] = 0
>>
>>
>> -Ray
>>
>>
>> ________________________________
>> From: xen-devel-bounces@lists.xensource.com
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
>> Sent: Monday, September 27, 2010 9:46 PM
>> To: Jiang, Yunhong
>> Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
>> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>>
>> On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong
><yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
>> "xm dmesg" should gives xen's boot log, and sometimes it contain some helpful
>information, I think, especially loglvl and guest_loglvl is set to all.
>>
>> I looked at the xm dmesg output and there's nothing more than what I already
>provided, aside from a bunch of commands from me poking at it.
>>
>> -Bruce
>>
>>
>> Thanks
>> --jyh
>>
>> From: Bruce Edge
>[mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
>> Sent: Tuesday, September 28, 2010 11:16 AM
>> To: Jiang, Yunhong
>> Cc: Konrad Rzeszutek Wilk;
>xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>>
>> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>>
>> On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong
><yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
>> Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
>>
>> Yes, there is 1 quad port card is this sytem:
>>
>> 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>> 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>> 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>> 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>>
>>
>> Also is it possible to share the xen output?
>>
>> I attached the dom0 boot output. Let me know if you wanted something else.
>>
>> Also, here's the dom0 console output upon starting the VM: This lockdep error
>started with the release of 2.6.32.21. Note that I'm running the same kernel for
>the domU and dom0.
>>
>> [ 1817.684097] ------------[ cut here ]------------
>> [ 1817.684113] WARNING: at kernel/lockdep.c:2323
>trace_hardirqs_on_caller+0x12f/0x190()
>> [ 1817.684119] Hardware name: ProLiant DL380 G6
>> [ 1817.684122] Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev
>fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon ttm
>drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core ipmi_msghandler joydev
>serio_raw hpwdt hpilo bridge stp llc usbhid hid cciss usb_storage
>> [ 1817.684190] Pid: 11, comm: xenwatch Not tainted 2.6.32.21-xenoprof-1 #1
>> [ 1817.684195] Call Trace:
>> [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
>trace_hardirqs_on_caller+0x12f/0x190
>> [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0
>> [ 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40
>> [ 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20
>> [ 1817.684229] [<ffffffff810aa18f>] trace_hardirqs_on_caller+0x12f/0x190
>> [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10
>> [ 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40
>> [ 1817.684266] [<ffffffff813c4fc5>] add_to_net_schedule_list_tail+0x85/0xd0
>> [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160
>> [ 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180
>> [ 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170
>> [ 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
>> [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60
>> [ 1817.684304] [<ffffffff8101647e>] xen_do_hypervisor_callback+0x1e/0x30
>> [ 1817.684308] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
>> [ 1817.684319] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
>> [ 1817.684325] [<ffffffff813bce54>] ? xb_write+0x1e4/0x290
>> [ 1817.684330] [<ffffffff813bd8ca>] ? xs_talkv+0x6a/0x1f0
>> [ 1817.684336] [<ffffffff813bd8d8>] ? xs_talkv+0x78/0x1f0
>> [ 1817.684341] [<ffffffff813bdbcd>] ? xs_single+0x4d/0x60
>> [ 1817.684346] [<ffffffff813be502>] ? xenbus_read+0x52/0x80
>> [ 1817.684352] [<ffffffff813c87fc>] ? frontend_changed+0x48c/0x770
>> [ 1817.684358] [<ffffffff813bf76d>] ? xenbus_otherend_changed+0xdd/0x1b0
>> [ 1817.684365] [<ffffffff8101122f>] ? xen_restore_fl_direct_end+0x0/0x1
>> [ 1817.684371] [<ffffffff810ac830>] ? lock_release+0xb0/0x230
>> [ 1817.684376] [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20
>> [ 1817.684382] [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160
>> [ 1817.684389] [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40
>> [ 1817.684394] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160
>> [ 1817.684400] [<ffffffff81093086>] ? kthread+0x96/0xb0
>> [ 1817.684405] [<ffffffff8101632a>] ? child_rip+0xa/0x20
>> [ 1817.684410] [<ffffffff81015c90>] ? restore_args+0x0/0x30
>> [ 1817.684415] [<ffffffff81016320>] ? child_rip+0x0/0x20
>>
>> -Bruce
>>
>>
>>
>> Thanks
>> --jyh
>>
>> >-----Original Message-----
>> >From:
>xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xensourc
>e.com>
>> >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@list
>s.xensource.com>] On Behalf Of Bruce Edge
>> >Sent: Tuesday, September 28, 2010 7:54 AM
>> >To: Konrad Rzeszutek Wilk
>> >Cc: xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>> >Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on
>Nehalem
>> >
>> >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
>> ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>> >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
>> >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
>> >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>> >>> >
>> >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> >>> > > One of our developers who is working on a tachyon driver is
>> >>> > > complaining that the pvops domU kernel is not working for these MSI
>> >>> > > interrupts.
>> >>> > > This is using the current head of xen/2.6.32.x on both a single
>> >>> > > Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> >>> > > 4.0.1, 4.0.2.rc1-pre and 4.1.
>> >>> > >
>> >>> > > Here are his comments:
>> >>> > >
>> >>> > > - the driver has no problem to enable msi interrupt and request the
>> >>> > > interrupt through kernel functions pci_enable_msi & request_irq
>> >>> >
>> >>> > What shows up in the Xen console when you send the 'q' key? Does it
>> >>> > show that the vector is assigned to the appropiate guest?
>> >>>
>> >>> The Xen console q key shows that the domU is assigned:
>> >>>
>> >>> (XEN) Interrupts { 32, 41-42, 47 }
>> >>
>> >> Aha!
>> >>
>> >>>
>> >>> but the domU thinks it has:
>> >>>
>> >>> 124/125/126/127
>> >>>
>> >>> Is there some mapping that's taking place, or is this plain wrong?
>> >>
>> >> That looks wrong. The IRQ numbers (even though they are MSI vectors) are
>> >> setup as IRQ numbers in the DomU guest. You should have seen
>> >>
>> >> 32:
>> >> 41:
>> >> 42:
>> >> 47:
>> >> in you /proc/interrupts on your DomU guest.
>> >>
>> >> I wonder what broke - can you use
>> >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org
>/pub/scm/linux/kernel/git/konrad/xen.git>
>> >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
>> >
>> >Please forgive the git ignorance.
>> >
>> >Is this the right syntax?
>> >
>> >git clone
>git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32<http://git.ke
>rnel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32>
>> >linux-2.6.32-pv-pcifront
>> >
>> >Initialized empty Git repository in
>> >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.git/
>> >fatal: The remote end hung up unexpectedly
>> >
>> >Or:
>> >
>> > git clone
>git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git.kernel.org/p
>ub/scm/linux/kernel/git/konrad/xen.git>
>> >
>> >Initialized empty Git repository in
>> >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
>> >remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
>> >remote: fatal: Failed to traverse parents of commit
>> >979e121cb348add17ed8171bf447b27a3a9d1be3
>> >remote: aborting due to possible repository corruption on the remote side.
>> >fatal: early EOF
>> >fatal: index-pack failed
>> >
>> >>
>> >> It has the latest pcifront driver but without the PVonHVM enhancments
>> >> so we can try to eliminate the PvONHVM logic out of the picture.
>> >>
>> >>>
>> >>> >
>> >>> > > - the interrupt does happen. But the interrupt service routine of
>> >>> > > tachyon driver doesn't detect any interrupt status related to this
>> >>> > > interrupt, which inhibits the tachyon chip from coming on-line. And
>> >>> > > there are high count of tachyon interrupt in /proc/interrupts
>> >>> >
>> >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
>> >>> > in the MMIO BAR?
>> >>> >
>> >>>
>> >>> The driver would check the appropriate register (tachyon registers) in
>> >>> the MMIO to determine the source of interrupts.
>> >>
>> >> OK, so that isn't it. Is there anything at these vectors:
>> >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
>> >> an inkling what device this is set for.
>> >
>> >When I run a distro kernel in hvm mode, I get the expected irq mappings:
>> >
>> >'i' - Note 66 - 69
>> >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:127(----),
>> >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:126(----),
>> >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:125(----),
>> >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:124(----)
>> >
>> >
>> >'q'
>> >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
>> >
>> >
>> >The same data with pv-ops kernel shows:
>> >
>> >'i'
>> >IRQ numbers stop at 65, no 66 - 69 present:
>> >
>> >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=0:289(----),
>> >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
>> >type=PCI-MSI status=00000002 mapped, unbound
>> >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=0:287(----),
>> >(XEN) IO-APIC interrupt information:
>> >
>> >'q'
>> >(XEN) Interrupts { 32, 41-42, 47 }
>> >
>> >>
>> >>>
>> >>> > >
>> >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
>> >>> > >
>> >124: 760415 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> > >
>> >125: 762234 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> > >
>> >126: 764180 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> > >
>> >127: 764164 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> >
>> >>> > Can you provide the full dmesg output?
>> >>>
>> >>> Attached.
>> >>>
>> >>> Some possibly related messages on dom0 console:
>> >>>
>> >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 -> 0003)
>> >>> [ 1882.269800] xen: registering gsi 32 triggering 0 polarity 1
>> >>> [ 1882.269827] xen_allocate_pirq: returning irq 32 for gsi 32
>> >>> [ 1882.269834] xen: --> irq=32
>> >>> [ 1882.269841] Already setup the GSI :32
>> >>> [ 1882.269847] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
>> >>> [ 1882.269866] pciback 0000:07:00.0: setting latency timer to 64
>> >>> [ 1882.270463] pciback 0000:07:00.0: Driver tried to write to a
>> >>> read-only configuration space field at offset 0x62, size 2. This may
>> >>> be harmless, but if you have problems with your device:
>> >>
>> >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
>> >> to find out what is at the configuration space. You could enable
>> >> it using the permissive attribute.
>> >>
>> >>> [ 1882.270465] 1) see permissive attribute in sysfs
>> >>> [ 1882.270467] 2) report problems to the xen-devel mailing list along
>> >>> with details of your device obtained from lspci.
>> >>> [ 1882.270615] alloc irq_desc for 478 on node 0
>> >>> [ 1882.270625] alloc kstat_irqs on node 0
>> >>
>> >> So for 478: what do you see? xen-pciback I presume?
>> >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 -> 0003)
>> >>> [ 1882.348433] xen: registering gsi 42 triggering 0 polarity 1
>> >>> [ 1882.348440] xen_allocate_pirq: returning irq 42 for gsi 42
>> >>> [ 1882.348445] xen: --> irq=42
>> >>> [ 1882.348472] Already setup the GSI :42
>> >>> [ 1882.348479] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
>> >>> [ 1882.348497] pciback 0000:07:00.1: setting latency timer to 64
>> >>> [ 1882.349063] pciback 0000:07:00.1: Driver tried to write to a
>> >>> read-only configuration space field at offset 0x62, size 2. This may
>> >>> be harmless, but if you have problems with your device:
>> >>> [ 1882.349066] 1) see permissive attribute in sysfs
>> >>> [ 1882.349067] 2) report problems to the xen-devel mailing list along
>> >>> with details of your device obtained from lspci.
>> >>> [ 1882.349205] alloc irq_desc for 477 on node 0
>> >>> [ 1882.349215] alloc kstat_irqs on node 0
>> >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 -> 0003)
>> >>> [ 1882.402908] xen: registering gsi 47 triggering 0 polarity 1
>> >>> [ 1882.402913] xen_allocate_pirq: returning irq 47 for gsi 47
>> >>> [ 1882.402916] xen: --> irq=47
>> >>> [ 1882.402921] Already setup the GSI :47
>> >>> [ 1882.402925] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
>> >>> [ 1882.402938] pciback 0000:07:00.2: setting latency timer to 64
>> >>> [ 1882.403280] pciback 0000:07:00.2: Driver tried to write to a
>> >>> read-only configuration space field at offset 0x62, size 2. This may
>> >>> be harmless, but if you have problems with your device:
>> >>> [ 1882.403282] 1) see permissive attribute in sysfs
>> >>> [ 1882.403282] 2) report problems to the xen-devel mailing list along
>> >>> with details of your device obtained from lspci.
>> >>> [ 1882.403380] alloc irq_desc for 476 on node 0
>> >>> [ 1882.403386] alloc kstat_irqs on node 0
>> >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
>> >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
>> >>> fault addr e6f80000, iommu reg = ffff82c3fff57000
>> >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>> >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
>> >>> (XEN) root_entry = ffff83019ff70000
>> >>> (XEN) root_entry[7] = 19cf52001
>> >>> (XEN) context = ffff83019cf52000
>> >>> (XEN) context[0] = 102_706dc005
>> >>> (XEN) l4 = ffff8300706dc000
>> >>> (XEN) l4_index = 0
>> >>> (XEN) l4[0] = 706db003
>> >>> (XEN) l3 = ffff8300706db000
>> >>> (XEN) l3_index = 3
>> >>> (XEN) l3[3] = 702b6003
>> >>> (XEN) l2 = ffff8300702b6000
>> >>> (XEN) l2_index = 137
>> >>> (XEN) l2[137] = 0
>> >>> (XEN) l2[137] not present
>> >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0 [ec=0000]
>> >>
>> >> That is not good. What changed from your earlier emails that this was
>triggered?
>> >
>> >Nothing
>> >> Or was it triggered all along?
>> >
>> >Yes, I just included it for completeness
>> >
>> >> What happens if you run the system without the iommu enabled?
>> >
>> >Haven't tried yet. Will check that next.
>> >
>> >-Bruce
>> >
>> >_______________________________________________
>> >Xen-devel mailing list
>> >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
>> >http://lists.xensource.com/xen-devel
>>
>>
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-29 0:53 ` Jiang, Yunhong
@ 2010-09-30 16:30 ` Lin, Ray
0 siblings, 0 replies; 42+ messages in thread
From: Lin, Ray @ 2010-09-30 16:30 UTC (permalink / raw)
To: Jiang, Yunhong, Konrad Rzeszutek Wilk, JBeulich@novell.com
Cc: xen-devel@lists.xensource.com, Bruce Edge
It doesn't help with "iommu=off". Here is the kernel command line I set.
(XEN) Command line: dummy=dummy dom0_mem=1024M dom0_max_vcpus=1 dom0_vcpus_pin=true iommu=off,passthrough,no-intremap loglvl=all loglvl_guest=all loglevl=10 debug apic=on apic_verbosity=verbose extra_guest_irqs=80 com1=115200,8n1 console=com1 console_to_ring noirqbalance xen-pciback.permissive acpi=force numa=on
-Ray
-----Original Message-----
From: Jiang, Yunhong [mailto:yunhong.jiang@intel.com]
Sent: Tuesday, September 28, 2010 5:54 PM
To: Konrad Rzeszutek Wilk; Lin, Ray; JBeulich@novell.com
Cc: Bruce Edge; xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
>-----Original Message-----
>From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
>Sent: Wednesday, September 29, 2010 12:19 AM
>To: Lin, Ray; JBeulich@novell.com
>Cc: Bruce Edge; Jiang, Yunhong; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on
>Nehalem
>
>On Tue, Sep 28, 2010 at 10:08:57AM -0600, Lin, Ray wrote:
>> I just checked the "xen dmesg". Look like DMA/iommu is the root
>> cause of
>this issue. In order to tell the source of interrupt, Tachyon chip
>needs to do the DMA write to a dword memory location to indicate the
>source of interrupt. What iommu option do you recommend to use ?
>
>Lets get Jan involved in this discussion.
>
>Jan, would some of your patches that inhibit the MSI write affect this
>in a PV guest?
As far as I can tell, this patch should not cause issue to VT-d side, instead, it's more about access from CPU.
Can you try to pass a option to xen as "iommu=off", and check the result?
Thanks
--jyh
>
>>
>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending Fault
>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device [07:00.0]
>> fault addr
>c00000, iommu reg = ffff82c3fff57000
>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = c00
>> (XEN) root_entry = ffff83019ff70000
>> (XEN) root_entry[7] = 19cf52001
>> (XEN) context = ffff83019cf52000
>> (XEN) context[0] = 102_706dc005
>> (XEN) l4 = ffff8300706dc000
>> (XEN) l4_index = 0
>> (XEN) l4[0] = 706db003
>> (XEN) l3 = ffff8300706db000
>> (XEN) l3_index = 0
>> (XEN) l3[0] = 706da003
>> (XEN) l2 = ffff8300706da000
>> (XEN) l2_index = 6
>> (XEN) l2[6] = 0
>>
>>
>> -Ray
>>
>>
>> ________________________________
>> From: xen-devel-bounces@lists.xensource.com
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
>> Sent: Monday, September 27, 2010 9:46 PM
>> To: Jiang, Yunhong
>> Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk
>> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
>> on Nehalem
>>
>> On Mon, Sep 27, 2010 at 8:26 PM, Jiang, Yunhong
><yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
>> "xm dmesg" should gives xen's boot log, and sometimes it contain some
>> helpful
>information, I think, especially loglvl and guest_loglvl is set to all.
>>
>> I looked at the xm dmesg output and there's nothing more than what I
>> already
>provided, aside from a bunch of commands from me poking at it.
>>
>> -Bruce
>>
>>
>> Thanks
>> --jyh
>>
>> From: Bruce Edge
>[mailto:bruce.edge@gmail.com<mailto:bruce.edge@gmail.com>]
>> Sent: Tuesday, September 28, 2010 11:16 AM
>> To: Jiang, Yunhong
>> Cc: Konrad Rzeszutek Wilk;
>xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>>
>> Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
>> on Nehalem
>>
>> On Mon, Sep 27, 2010 at 6:15 PM, Jiang, Yunhong
><yunhong.jiang@intel.com<mailto:yunhong.jiang@intel.com>> wrote:
>> Is the 07:0.0 your tachyon device? The VT-d fault is suspcious.
>>
>> Yes, there is 1 quad port card is this sytem:
>>
>> 07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>> 07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>> 07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>> 07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
>>
>>
>> Also is it possible to share the xen output?
>>
>> I attached the dom0 boot output. Let me know if you wanted something else.
>>
>> Also, here's the dom0 console output upon starting the VM: This
>> lockdep error
>started with the release of 2.6.32.21. Note that I'm running the same
>kernel for the domU and dom0.
>>
>> [ 1817.684097] ------------[ cut here ]------------ [ 1817.684113]
>> WARNING: at kernel/lockdep.c:2323
>trace_hardirqs_on_caller+0x12f/0x190()
>> [ 1817.684119] Hardware name: ProLiant DL380 G6 [ 1817.684122]
>> Modules linked in: xt_physdev ipv6 osa_mfgdom0 xenfs xen_gntdev
>fbcon tileblit font bitblit softcursor xen_evtchn xen_pciback radeon
>ttm drm_kms_helper tun drm i2c_algo_bit ipmi_si i2c_core
>ipmi_msghandler joydev serio_raw hpwdt hpilo bridge stp llc usbhid hid
>cciss usb_storage
>> [ 1817.684190] Pid: 11, comm: xenwatch Not tainted
>> 2.6.32.21-xenoprof-1 #1 [ 1817.684195] Call Trace:
>> [ 1817.684197] <IRQ> [<ffffffff810aa18f>] ?
>trace_hardirqs_on_caller+0x12f/0x190
>> [ 1817.684209] [<ffffffff8106bed0>] warn_slowpath_common+0x80/0xd0 [
>> 1817.684217] [<ffffffff815f2b80>] ? _spin_unlock_irq+0x30/0x40 [
>> 1817.684223] [<ffffffff8106bf34>] warn_slowpath_null+0x14/0x20 [
>> 1817.684229] [<ffffffff810aa18f>]
>> trace_hardirqs_on_caller+0x12f/0x190
>> [ 1817.684234] [<ffffffff810aa1fd>] trace_hardirqs_on+0xd/0x10 [
>> 1817.684240] [<ffffffff815f2b80>] _spin_unlock_irq+0x30/0x40 [
>> 1817.684266] [<ffffffff813c4fc5>]
>> add_to_net_schedule_list_tail+0x85/0xd0
>> [ 1817.684271] [<ffffffff813c6216>] netif_be_int+0x36/0x160 [
>> 1817.684278] [<ffffffff810e10d0>] handle_IRQ_event+0x70/0x180 [
>> 1817.684284] [<ffffffff810e36e9>] handle_edge_irq+0xc9/0x170 [
>> 1817.684291] [<ffffffff813b8d7f>] __xen_evtchn_do_upcall+0x1bf/0x1f0
>> [ 1817.684297] [<ffffffff813b92fd>] xen_evtchn_do_upcall+0x3d/0x60 [
>> 1817.684304] [<ffffffff8101647e>]
>> xen_do_hypervisor_callback+0x1e/0x30
>> [ 1817.684308] <EOI> [<ffffffff8100940a>] ?
>> hypercall_page+0x40a/0x1010 [ 1817.684319] [<ffffffff8100940a>] ?
>> hypercall_page+0x40a/0x1010 [ 1817.684325] [<ffffffff813bce54>] ?
>> xb_write+0x1e4/0x290 [ 1817.684330] [<ffffffff813bd8ca>] ?
>> xs_talkv+0x6a/0x1f0 [ 1817.684336] [<ffffffff813bd8d8>] ?
>> xs_talkv+0x78/0x1f0 [ 1817.684341] [<ffffffff813bdbcd>] ?
>> xs_single+0x4d/0x60 [ 1817.684346] [<ffffffff813be502>] ?
>> xenbus_read+0x52/0x80 [ 1817.684352] [<ffffffff813c87fc>] ?
>> frontend_changed+0x48c/0x770 [ 1817.684358] [<ffffffff813bf76d>] ?
>> xenbus_otherend_changed+0xdd/0x1b0
>> [ 1817.684365] [<ffffffff8101122f>] ?
>> xen_restore_fl_direct_end+0x0/0x1 [ 1817.684371]
>> [<ffffffff810ac830>] ? lock_release+0xb0/0x230 [ 1817.684376]
>> [<ffffffff813bfae0>] ? frontend_changed+0x10/0x20 [ 1817.684382]
>> [<ffffffff813bd4f5>] ? xenwatch_thread+0x55/0x160 [ 1817.684389]
>> [<ffffffff81093400>] ? autoremove_wake_function+0x0/0x40 [
>> 1817.684394] [<ffffffff813bd4a0>] ? xenwatch_thread+0x0/0x160 [
>> 1817.684400] [<ffffffff81093086>] ? kthread+0x96/0xb0 [ 1817.684405]
>> [<ffffffff8101632a>] ? child_rip+0xa/0x20 [ 1817.684410]
>> [<ffffffff81015c90>] ? restore_args+0x0/0x30 [ 1817.684415]
>> [<ffffffff81016320>] ? child_rip+0x0/0x20
>>
>> -Bruce
>>
>>
>>
>> Thanks
>> --jyh
>>
>> >-----Original Message-----
>> >From:
>xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounces@lists.xe
>nsourc
>e.com>
>> >[mailto:xen-devel-bounces@lists.xensource.com<mailto:xen-devel-bounc
>> >es@list
>s.xensource.com>] On Behalf Of Bruce Edge
>> >Sent: Tuesday, September 28, 2010 7:54 AM
>> >To: Konrad Rzeszutek Wilk
>> >Cc:
>> >xen-devel@lists.xensource.com<mailto:xen-devel@lists.xensource.com>
>> >Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts
>> >on
>Nehalem
>> >
>> >On Mon, Sep 27, 2010 at 12:54 PM, Konrad Rzeszutek Wilk
>> ><konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>> >> On Mon, Sep 27, 2010 at 12:16:50PM -0700, Bruce Edge wrote:
>> >>> On Mon, Sep 27, 2010 at 10:24 AM, Konrad Rzeszutek Wilk
>> >>> <konrad.wilk@oracle.com<mailto:konrad.wilk@oracle.com>> wrote:
>> >>> >
>> >>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> >>> > > One of our developers who is working on a tachyon driver is
>> >>> > > complaining that the pvops domU kernel is not working for
>> >>> > > these MSI interrupts.
>> >>> > > This is using the current head of xen/2.6.32.x on both a
>> >>> > > single Nahelam 920 and a dual E5540. This behavior is
>> >>> > > consistent with Xen 4.0.1, 4.0.2.rc1-pre and 4.1.
>> >>> > >
>> >>> > > Here are his comments:
>> >>> > >
>> >>> > > - the driver has no problem to enable msi interrupt and
>> >>> > > request the interrupt through kernel functions pci_enable_msi
>> >>> > > & request_irq
>> >>> >
>> >>> > What shows up in the Xen console when you send the 'q' key?
>> >>> > Does it show that the vector is assigned to the appropiate guest?
>> >>>
>> >>> The Xen console q key shows that the domU is assigned:
>> >>>
>> >>> (XEN) Interrupts { 32, 41-42, 47 }
>> >>
>> >> Aha!
>> >>
>> >>>
>> >>> but the domU thinks it has:
>> >>>
>> >>> 124/125/126/127
>> >>>
>> >>> Is there some mapping that's taking place, or is this plain wrong?
>> >>
>> >> That looks wrong. The IRQ numbers (even though they are MSI
>> >> vectors) are setup as IRQ numbers in the DomU guest. You should
>> >> have seen
>> >>
>> >> 32:
>> >> 41:
>> >> 42:
>> >> 47:
>> >> in you /proc/interrupts on your DomU guest.
>> >>
>> >> I wonder what broke - can you use
>> >git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://
>> >git.kernel.org
>/pub/scm/linux/kernel/git/konrad/xen.git>
>> >> devel/xen-pcifront-0.5 (or pv/pcifront-2.6.32)?
>> >
>> >Please forgive the git ignorance.
>> >
>> >Is this the right syntax?
>> >
>> >git clone
>git://git.kernel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32
><http://git.ke
>rnel.org/pub/scm/linux/kernel/git/konrad:pv/pcifront-2.6.32>
>> >linux-2.6.32-pv-pcifront
>> >
>> >Initialized empty Git repository in
>> >/import/kaan/bedge/src/xen/kernel/pv-ops/linux-2.6.32-pv-pcifront/.g
>> >it/
>> >fatal: The remote end hung up unexpectedly
>> >
>> >Or:
>> >
>> > git clone
>git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git<http://git
>.kernel.org/p ub/scm/linux/kernel/git/konrad/xen.git>
>> >
>> >Initialized empty Git repository in
>> >/import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
>> >remote: error: Could not read
>> >59eab2f8f04147c5aadc99f2034ca7e5b81e890f
>> >remote: fatal: Failed to traverse parents of commit
>> >979e121cb348add17ed8171bf447b27a3a9d1be3
>> >remote: aborting due to possible repository corruption on the remote side.
>> >fatal: early EOF
>> >fatal: index-pack failed
>> >
>> >>
>> >> It has the latest pcifront driver but without the PVonHVM
>> >> enhancments so we can try to eliminate the PvONHVM logic out of the picture.
>> >>
>> >>>
>> >>> >
>> >>> > > - the interrupt does happen. But the interrupt service
>> >>> > > routine of tachyon driver doesn't detect any interrupt status
>> >>> > > related to this interrupt, which inhibits the tachyon chip
>> >>> > > from coming on-line. And there are high count of tachyon
>> >>> > > interrupt in /proc/interrupts
>> >>> >
>> >>> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate
>> >>> > register in the MMIO BAR?
>> >>> >
>> >>>
>> >>> The driver would check the appropriate register (tachyon
>> >>> registers) in the MMIO to determine the source of interrupts.
>> >>
>> >> OK, so that isn't it. Is there anything at these vectors:
>> >> 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it
>> >> should give you an inkling what device this is set for.
>> >
>> >When I run a distro kernel in hvm mode, I get the expected irq mappings:
>> >
>> >'i' - Note 66 - 69
>> >(XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:127(----),
>> >(XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:126(----),
>> >(XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:125(----),
>> >(XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=10:124(----)
>> >
>> >
>> >'q'
>> >(XEN) Interrupts { 32, 41-42, 47, 124-127 }
>> >
>> >
>> >The same data with pv-ops kernel shows:
>> >
>> >'i'
>> >IRQ numbers stop at 65, no 66 - 69 present:
>> >
>> >(XEN) IRQ: 63 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:91
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=0:289(----),
>> >(XEN) IRQ: 64 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:99
>> >type=PCI-MSI status=00000002 mapped, unbound
>> >(XEN) IRQ: 65 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:b1
>> >type=PCI-MSI status=00000010 in-flight=0
>> >domain-list=0:287(----),
>> >(XEN) IO-APIC interrupt information:
>> >
>> >'q'
>> >(XEN) Interrupts { 32, 41-42, 47 }
>> >
>> >>
>> >>>
>> >>> > >
>> >>> > > kaan-18-dpm:~# cat /proc/interrupts | grep TACH
>> >>> > >
>> >124: 760415 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> > >
>> >125: 762234 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> > >
>> >126: 764180 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> > >
>> >127: 764164 0 0 0 0
>> > 0
>> >>> > > 0 0 0 0 0
>> > 0
>> >>> > > 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> >>> >
>> >>> > Can you provide the full dmesg output?
>> >>>
>> >>> Attached.
>> >>>
>> >>> Some possibly related messages on dom0 console:
>> >>>
>> >>> [ 1882.269778] pciback 0000:07:00.0: enabling device (0000 ->
>> >>> 0003) [ 1882.269800] xen: registering gsi 32 triggering 0
>> >>> polarity 1 [ 1882.269827] xen_allocate_pirq: returning irq 32 for
>> >>> gsi 32 [ 1882.269834] xen: --> irq=32 [ 1882.269841] Already
>> >>> setup the GSI :32 [ 1882.269847] pciback 0000:07:00.0: PCI INT A
>> >>> -> GSI 32 (level, low) -> IRQ 32 [ 1882.269866] pciback
>> >>> 0000:07:00.0: setting latency timer to 64 [ 1882.270463] pciback
>> >>> 0000:07:00.0: Driver tried to write to a read-only configuration
>> >>> space field at offset 0x62, size 2. This may be harmless, but if
>> >>> you have problems with your device:
>> >>
>> >> Uhhh, for that I think you need to do 'lspci -vvv -xxx -s 07:00.00'
>> >> to find out what is at the configuration space. You could enable
>> >> it using the permissive attribute.
>> >>
>> >>> [ 1882.270465] 1) see permissive attribute in sysfs [
>> >>> 1882.270467] 2) report problems to the xen-devel mailing list
>> >>> along with details of your device obtained from lspci.
>> >>> [ 1882.270615] alloc irq_desc for 478 on node 0
>> >>> [ 1882.270625] alloc kstat_irqs on node 0
>> >>
>> >> So for 478: what do you see? xen-pciback I presume?
>> >>> [ 1882.348411] pciback 0000:07:00.1: enabling device (0000 ->
>> >>> 0003) [ 1882.348433] xen: registering gsi 42 triggering 0
>> >>> polarity 1 [ 1882.348440] xen_allocate_pirq: returning irq 42 for
>> >>> gsi 42 [ 1882.348445] xen: --> irq=42 [ 1882.348472] Already
>> >>> setup the GSI :42 [ 1882.348479] pciback 0000:07:00.1: PCI INT B
>> >>> -> GSI 42 (level, low) -> IRQ 42 [ 1882.348497] pciback
>> >>> 0000:07:00.1: setting latency timer to 64 [ 1882.349063] pciback
>> >>> 0000:07:00.1: Driver tried to write to a read-only configuration
>> >>> space field at offset 0x62, size 2. This may be harmless, but if
>> >>> you have problems with your device:
>> >>> [ 1882.349066] 1) see permissive attribute in sysfs [
>> >>> 1882.349067] 2) report problems to the xen-devel mailing list
>> >>> along with details of your device obtained from lspci.
>> >>> [ 1882.349205] alloc irq_desc for 477 on node 0
>> >>> [ 1882.349215] alloc kstat_irqs on node 0
>> >>> [ 1882.402893] pciback 0000:07:00.2: enabling device (0000 ->
>> >>> 0003) [ 1882.402908] xen: registering gsi 47 triggering 0
>> >>> polarity 1 [ 1882.402913] xen_allocate_pirq: returning irq 47 for
>> >>> gsi 47 [ 1882.402916] xen: --> irq=47 [ 1882.402921] Already
>> >>> setup the GSI :47 [ 1882.402925] pciback 0000:07:00.2: PCI INT C
>> >>> -> GSI 47 (level, low) -> IRQ 47 [ 1882.402938] pciback
>> >>> 0000:07:00.2: setting latency timer to 64 [ 1882.403280] pciback
>> >>> 0000:07:00.2: Driver tried to write to a read-only configuration
>> >>> space field at offset 0x62, size 2. This may be harmless, but if
>> >>> you have problems with your device:
>> >>> [ 1882.403282] 1) see permissive attribute in sysfs [
>> >>> 1882.403282] 2) report problems to the xen-devel mailing list
>> >>> along with details of your device obtained from lspci.
>> >>> [ 1882.403380] alloc irq_desc for 476 on node 0
>> >>> [ 1882.403386] alloc kstat_irqs on node 0
>> >>> (XEN) [VT-D]iommu.c:824: iommu_fault_status: Primary Pending
>> >>> Fault
>> >>> (XEN) [VT-D]iommu.c:799: DMAR:[DMA Write] Request device
>> >>> [07:00.0] fault addr e6f80000, iommu reg = ffff82c3fff57000
>> >>> (XEN) DMAR:[fault reason 05h] PTE Write access is not set
>> >>> (XEN) print_vtd_entries: iommu = ffff83019fffa370 bdf = 7:0.0 gmfn = e6f80
>> >>> (XEN) root_entry = ffff83019ff70000
>> >>> (XEN) root_entry[7] = 19cf52001
>> >>> (XEN) context = ffff83019cf52000
>> >>> (XEN) context[0] = 102_706dc005
>> >>> (XEN) l4 = ffff8300706dc000
>> >>> (XEN) l4_index = 0
>> >>> (XEN) l4[0] = 706db003
>> >>> (XEN) l3 = ffff8300706db000
>> >>> (XEN) l3_index = 3
>> >>> (XEN) l3[3] = 702b6003
>> >>> (XEN) l2 = ffff8300702b6000
>> >>> (XEN) l2_index = 137
>> >>> (XEN) l2[137] = 0
>> >>> (XEN) l2[137] not present
>> >>> (XEN) traps.c:466:d0 Unhandled nmi fault/trap [#2] on VCPU 0
>> >>> [ec=0000]
>> >>
>> >> That is not good. What changed from your earlier emails that this
>> >> was
>triggered?
>> >
>> >Nothing
>> >> Or was it triggered all along?
>> >
>> >Yes, I just included it for completeness
>> >
>> >> What happens if you run the system without the iommu enabled?
>> >
>> >Haven't tried yet. Will check that next.
>> >
>> >-Bruce
>> >
>> >_______________________________________________
>> >Xen-devel mailing list
>> >Xen-devel@lists.xensource.com<mailto:Xen-devel@lists.xensource.com>
>> >http://lists.xensource.com/xen-devel
>>
>>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-28 14:56 ` Konrad Rzeszutek Wilk
@ 2010-09-30 18:55 ` Bruce Edge
0 siblings, 0 replies; 42+ messages in thread
From: Bruce Edge @ 2010-09-30 18:55 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Tue, Sep 28, 2010 at 7:56 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
>> git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
>>
>> Initialized empty Git repository in
>> /import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
>> remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
>> remote: fatal: Failed to traverse parents of commit
>> 979e121cb348add17ed8171bf447b27a3a9d1be3
>> remote: aborting due to possible repository corruption on the remote side.
>> fatal: early EOF
>> fatal: index-pack failed
>
> That should have worked, but it looks as my git repo is busted. Let me fix that
> and once it done you should be able to do
>
> cd xen
> git checkout origin/pv/pcifront-2.6.32
That's working now, will test today.
>
>>
>> >
>> > It has the latest pcifront driver but without the PVonHVM enhancments
>> > so we can try to eliminate the PvONHVM logic out of the picture.
>> >
>> >>
>> >> >
>> >> > > - the interrupt does happen. But the interrupt service routine of
>> >> > > tachyon driver doesn't detect any interrupt status related to this
>> >> > > interrupt, which inhibits the tachyon chip from coming on-line. And
>> >> > > there are high count of tachyon interrupt in /proc/interrupts
>> >> >
>> >> > Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
>> >> > in the MMIO BAR?
>> >> >
>> >>
>> >> The driver would check the appropriate register (tachyon registers) in
>> >> the MMIO to determine the source of interrupts.
>> >
>> > OK, so that isn't it. Is there anything at these vectors:
>> > 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
>> > an inkling what device this is set for.
>>
>> When I run a distro kernel in hvm mode, I get the expected irq mappings:
>>
>> 'i' - Note 66 - 69
>> (XEN) IRQ: 66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
>> type=PCI-MSI status=00000010 in-flight=0
>> domain-list=10:127(----),
>> (XEN) IRQ: 67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
>> type=PCI-MSI status=00000010 in-flight=0
>> domain-list=10:126(----),
>> (XEN) IRQ: 68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
>> type=PCI-MSI status=00000010 in-flight=0
>> domain-list=10:125(----),
>> (XEN) IRQ: 69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
>> type=PCI-MSI status=00000010 in-flight=0
>> domain-list=10:124(----)
>>
>
> What does cat /proc/interrupts (don't do the grep) for this HVM guest?
Here's what's reported for the domU in hvm mode:
~ # cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
0: 28 0 0 0 0 0
IO-APIC-edge timer
1: 18 0 0 0 0 0
IO-APIC-edge i8042
6: 2 0 0 0 0 0
IO-APIC-edge floppy
7: 0 0 0 0 0 0
IO-APIC-edge parport0
8: 0 0 0 0 0 0
IO-APIC-edge rtc0
9: 0 0 0 0 0 0
IO-APIC-fasteoi acpi
12: 2 0 0 0 0 0
IO-APIC-edge i8042
14: 67771 0 0 0 0 0
IO-APIC-edge ata_piix
15: 3044 0 0 0 0 0
IO-APIC-edge ata_piix
23: 22 0 0 0 0 0
IO-APIC-fasteoi uhci_hcd:usb1
32: 953 0 0 0 0 0
IO-APIC-fasteoi eth0
NMI: 0 0 0 0 0 0
Non-maskable interrupts
LOC: 26320 15814 13000 13825 11125 10458
Local timer interrupts
SPU: 0 0 0 0 0 0
Spurious interrupts
PMI: 0 0 0 0 0 0
Performance monitoring interrupts
PND: 0 0 0 0 0 0
Performance pending work
RES: 78730 21174 25236 34071 25122 26924
Rescheduling interrupts
CAL: 90 806 808 488 587 392
Function call interrupts
TLB: 3429 2358 3475 2522 3986 2684
TLB shootdowns
TRM: 0 0 0 0 0 0
Thermal event interrupts
THR: 0 0 0 0 0 0
Threshold APIC interrupts
MCE: 0 0 0 0 0 0
Machine check exceptions
MCP: 2 2 2 2 2 2
Machine check polls
ERR: 0
MIS: 0
~ # lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.2 USB Controller: Intel Corporation 82371SB PIIX3 USB
[Natoma/Triton II] (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01)
00:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 20)
00:10.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 05)
00:11.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 05)
00:12.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 05)
00:13.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 05)
>>
>> 'q'
>> (XEN) Interrupts { 32, 41-42, 47, 124-127 }
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-09-27 15:52 pv-ops domU not working with MSI interrupts on Nehalem Bruce Edge
2010-09-27 17:24 ` Konrad Rzeszutek Wilk
@ 2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19 ` Bruce Edge
` (3 more replies)
1 sibling, 4 replies; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-10-01 21:11 UTC (permalink / raw)
To: Bruce Edge, Ray.Lin; +Cc: xen-devel
On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> One of our developers who is working on a tachyon driver is
> complaining that the pvops domU kernel is not working for these MSI
> interrupts.
> This is using the current head of xen/2.6.32.x on both a single
> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> 4.0.1, 4.0.2.rc1-pre and 4.1.
I just checked on my SuperMicro X8DTN, this combination
- For Dom0, git commit fe999249 (2.6.32.18)
- For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
- For Hypervisor I used cs 21976, but found that the latest (22155) works too
with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
worked just fine (either defining pci=["..."] or just using pci-attach).
But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
that happy :-(
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
@ 2010-10-01 21:19 ` Bruce Edge
2010-10-01 23:30 ` Bruce Edge
` (2 subsequent siblings)
3 siblings, 0 replies; 42+ messages in thread
From: Bruce Edge @ 2010-10-01 21:19 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel, Ray.Lin
On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> One of our developers who is working on a tachyon driver is
>> complaining that the pvops domU kernel is not working for these MSI
>> interrupts.
>> This is using the current head of xen/2.6.32.x on both a single
>> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> 4.0.1, 4.0.2.rc1-pre and 4.1.
>
>
> I just checked on my SuperMicro X8DTN, this combination
> - For Dom0, git commit fe999249 (2.6.32.18)
> - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
> - For Hypervisor I used cs 21976, but found that the latest (22155) works too
Perfect! That's all I need - a recipe that works. Thank you very much.
-Bruce
>
> with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
> a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>
> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
> 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
> 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>
> worked just fine (either defining pci=["..."] or just using pci-attach).
>
> But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
> that happy :-(
>
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19 ` Bruce Edge
@ 2010-10-01 23:30 ` Bruce Edge
2010-10-03 5:46 ` Bruce Edge
2010-10-04 14:48 ` Konrad Rzeszutek Wilk
2010-10-08 17:56 ` Bruce Edge
2010-10-11 21:12 ` Bruce Edge
3 siblings, 2 replies; 42+ messages in thread
From: Bruce Edge @ 2010-10-01 23:30 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> One of our developers who is working on a tachyon driver is
>> complaining that the pvops domU kernel is not working for these MSI
>> interrupts.
>> This is using the current head of xen/2.6.32.x on both a single
>> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> 4.0.1, 4.0.2.rc1-pre and 4.1.
>
>
> I just checked on my SuperMicro X8DTN, this combination
> - For Dom0, git commit fe999249 (2.6.32.18)
> - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
Konrad,
Apologies in advance for the rookie git questions.
I'm assuming the git repos you mentioned are based on
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
Your devel/xen-pcifront-0.7 isn't visible:
%> git branch -r | grep devel/xen-pcifront
origin/devel/xen-pcifront-0.1
origin/devel/xen-pcifront-0.2
origin/devel/xen-pcifront-0.3
origin/devel/xen-pcifront-0.4
origin/devel/xen-pcifront-0.5
origin/devel/xen-pcifront-0.6
and your devel/xen-pcifront-0.6 forces a config restart:
0 %> make oldconfig
scripts/kconfig/conf --oldconfig arch/x86/Kconfig
*
* Restart config...
*
*
* General setup
*
Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
Cross-compiler tool prefix (CROSS_COMPILE) [] (NEW) ^Cmake[1]: ***
[oldconfig] Interrupt
make: *** [oldconfig] Interrupt
Is there a trick to avoiding the config restart?
-Bruce
> - For Hypervisor I used cs 21976, but found that the latest (22155) works too
>
> with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
> a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>
> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
> 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
> 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>
> worked just fine (either defining pci=["..."] or just using pci-attach).
>
> But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
> that happy :-(
>
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-01 23:30 ` Bruce Edge
@ 2010-10-03 5:46 ` Bruce Edge
2010-10-03 12:08 ` Pasi Kärkkäinen
2010-10-04 14:48 ` Konrad Rzeszutek Wilk
1 sibling, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-03 5:46 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Fri, Oct 1, 2010 at 4:30 PM, Bruce Edge <bruce.edge@gmail.com> wrote:
> On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
>> On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>>> One of our developers who is working on a tachyon driver is
>>> complaining that the pvops domU kernel is not working for these MSI
>>> interrupts.
>>> This is using the current head of xen/2.6.32.x on both a single
>>> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>>> 4.0.1, 4.0.2.rc1-pre and 4.1.
>>
>>
>> I just checked on my SuperMicro X8DTN, this combination
>> - For Dom0, git commit fe999249 (2.6.32.18)
>> - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
>
> Konrad,
>
> Apologies in advance for the rookie git questions.
>
> I'm assuming the git repos you mentioned are based on
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
>
> Your devel/xen-pcifront-0.7 isn't visible:
>
> %> git branch -r | grep devel/xen-pcifront
>
> origin/devel/xen-pcifront-0.1
> origin/devel/xen-pcifront-0.2
> origin/devel/xen-pcifront-0.3
> origin/devel/xen-pcifront-0.4
> origin/devel/xen-pcifront-0.5
> origin/devel/xen-pcifront-0.6
>
>
> and your devel/xen-pcifront-0.6 forces a config restart:
>
> 0 %> make oldconfig
> scripts/kconfig/conf --oldconfig arch/x86/Kconfig
> *
> * Restart config...
> *
> *
> * General setup
> *
> Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
> Cross-compiler tool prefix (CROSS_COMPILE) [] (NEW) ^Cmake[1]: ***
> [oldconfig] Interrupt
> make: *** [oldconfig] Interrupt
>
> Is there a trick to avoiding the config restart?
Found the problem here - I was using a .config from a 2.6.32 kernel.
There's something in the 2.6.36 config parsing that declares it
invalid and starts over.
Starting with a clean 'make defconfig' and editing that works fine.
I had never see this behavior in kernel builds before. I thought the
.config files were always compatible between versions.
-Bruce
>
> -Bruce
>
>> - For Hypervisor I used cs 21976, but found that the latest (22155) works too
>>
>> with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
>> a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>>
>> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
>> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
>> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
>> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
>> 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
>> 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>>
>> worked just fine (either defining pci=["..."] or just using pci-attach).
>>
>> But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
>> that happy :-(
>>
>>
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-03 5:46 ` Bruce Edge
@ 2010-10-03 12:08 ` Pasi Kärkkäinen
0 siblings, 0 replies; 42+ messages in thread
From: Pasi Kärkkäinen @ 2010-10-03 12:08 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel, Konrad Rzeszutek Wilk
On Sat, Oct 02, 2010 at 10:46:45PM -0700, Bruce Edge wrote:
> >
> > and your devel/xen-pcifront-0.6 forces a config restart:
> >
> > 0 %> make oldconfig
> > scripts/kconfig/conf --oldconfig arch/x86/Kconfig
> > *
> > * Restart config...
> > *
> > *
> > * General setup
> > *
> > Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
> > Cross-compiler tool prefix (CROSS_COMPILE) [] (NEW) ^Cmake[1]: ***
> > [oldconfig] Interrupt
> > make: *** [oldconfig] Interrupt
> >
> > Is there a trick to avoiding the config restart?
>
> Found the problem here - I was using a .config from a 2.6.32 kernel.
> There's something in the 2.6.36 config parsing that declares it
> invalid and starts over.
> Starting with a clean 'make defconfig' and editing that works fine.
>
> I had never see this behavior in kernel builds before. I thought the
> .config files were always compatible between versions.
>
You need to do "make oldconfig" to adapt/merge the 2.6.32 config to 2.6.36.
-- Pasi
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-01 23:30 ` Bruce Edge
2010-10-03 5:46 ` Bruce Edge
@ 2010-10-04 14:48 ` Konrad Rzeszutek Wilk
2010-10-05 18:21 ` Bruce Edge
1 sibling, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-10-04 14:48 UTC (permalink / raw)
To: Bruce Edge, '; +Cc: xen-devel
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
>
> Your devel/xen-pcifront-0.7 isn't visible:
It should be now. I pushed it late on Friday and repushed it today since it had
some commits with the wrong committer field.
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-04 14:48 ` Konrad Rzeszutek Wilk
@ 2010-10-05 18:21 ` Bruce Edge
2010-10-06 14:21 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-05 18:21 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
>> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
>>
>> Your devel/xen-pcifront-0.7 isn't visible:
>
> It should be now. I pushed it late on Friday and repushed it today since it had
> some commits with the wrong committer field.
>
Is there anything special one needs to do when building this kernel?
The bzImage target err's out with undef'd syms:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o: In function `notify_remote_via_evtchn':
xen-pcifront.c:(.text+0x15b79): undefined reference to `hypercall_page'
xen-pcifront.c:(.text+0x15b9d): undefined reference to `hypercall_page'
drivers/built-in.o: In function `do_pci_op':
xen-pcifront.c:(.text+0x15cce): undefined reference to `xen_clear_irq_pending'
xen-pcifront.c:(.text+0x15ce6): undefined reference to `xen_poll_irq_timeout'
xen-pcifront.c:(.text+0x15cee): undefined reference to `xen_clear_irq_pending'
drivers/built-in.o: In function `pcifront_xenbus_probe':
xen-pcifront.c:(.text+0x161db): undefined reference to `xen_features'
xen-pcifront.c:(.text+0x161fc): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.text+0x16209): undefined reference to `get_phys_to_machine'
xen-pcifront.c:(.text+0x16221): undefined reference to `xenbus_grant_ring'
xen-pcifront.c:(.text+0x1623b): undefined reference to `xenbus_alloc_evtchn'
xen-pcifront.c:(.text+0x16261): undefined reference to
`bind_evtchn_to_irqhandler'
xen-pcifront.c:(.text+0x16273): undefined reference to `xenbus_free_evtchn'
xen-pcifront.c:(.text+0x1628b): undefined reference to
`xenbus_transaction_start'
xen-pcifront.c:(.text+0x162a6): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.text+0x162ce): undefined reference to `xenbus_printf'
xen-pcifront.c:(.text+0x162f8): undefined reference to `xenbus_printf'
xen-pcifront.c:(.text+0x1631e): undefined reference to `xenbus_printf'
xen-pcifront.c:(.text+0x16332): undefined reference to `xenbus_transaction_end'
xen-pcifront.c:(.text+0x16348): undefined reference to `xenbus_transaction_end'
xen-pcifront.c:(.text+0x16370): undefined reference to `xenbus_switch_state'
drivers/built-in.o: In function `pcifront_xenbus_remove':
xen-pcifront.c:(.text+0x16861): undefined reference to `unbind_from_irqhandler'
xen-pcifront.c:(.text+0x16871): undefined reference to `xenbus_free_evtchn'
xen-pcifront.c:(.text+0x16883): undefined reference to
`gnttab_end_foreign_access'
drivers/built-in.o: In function `pcifront_backend_changed':
xen-pcifront.c:(.ref.text+0xcca): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xd0c): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xd24): undefined reference to `xenbus_dev_error'
xen-pcifront.c:(.ref.text+0xd6e): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.ref.text+0xdb5): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xe07): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xe38): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xe63): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xed7): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xf39): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0xfc9): undefined reference to
`xenbus_read_driver_state'
xen-pcifront.c:(.ref.text+0xff4): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0x100c): undefined reference to `xenbus_dev_error'
xen-pcifront.c:(.ref.text+0x1083): undefined reference to `xenbus_scanf'
xen-pcifront.c:(.ref.text+0x10a8): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.ref.text+0x10d6): undefined reference to `xenbus_dev_fatal'
xen-pcifront.c:(.ref.text+0x10f2): undefined reference to `xenbus_switch_state'
drivers/built-in.o: In function `pcifront_cleanup':
xen-pcifront.c:(.exit.text+0x36): undefined reference to
`xenbus_unregister_driver'
make: *** [.tmp_vmlinux1] Error 1
I noticed the defconfig target had a couple of warnings too:
%> make defconfig
*** Default configuration is based on 'x86_64_defconfig'
warning: (XEN_PCIDEV_FRONTEND && X86) selects PCI_XEN which has unmet
direct dependencies (XEN)
warning: (XEN_PCIDEV_FRONTEND && X86) selects PCI_XEN which has unmet
direct dependencies (XEN)
#
# configuration written to .config
#
-Bruce
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-05 18:21 ` Bruce Edge
@ 2010-10-06 14:21 ` Konrad Rzeszutek Wilk
2010-10-06 18:21 ` Bruce Edge
0 siblings, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-10-06 14:21 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel
On Tue, Oct 05, 2010 at 11:21:38AM -0700, Bruce Edge wrote:
> On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
> >>
> >> Your devel/xen-pcifront-0.7 isn't visible:
> >
> > It should be now. I pushed it late on Friday and repushed it today since it had
> > some commits with the wrong committer field.
> >
>
> Is there anything special one needs to do when building this kernel?
Wow. I've never seen those errors before. Can you send me your .config file
so I can make sure this does not happend
For me, I've these options defined:
[konrad@tst002 bootstrap]$ cat linux-build/.config|grep XEN
CONFIG_XEN=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=8
CONFIG_XEN_SAVE_RESTORE=y
CONFIG_XEN_DEBUG_FS=y
CONFIG_PCI_XEN=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_XEN_BLKDEV_FRONTEND=m
# CONFIG_NETXEN_NIC is not set
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_XEN_KBDDEV_FRONTEND=m
CONFIG_HVC_XEN=y
CONFIG_XEN_FBDEV_FRONTEND=m
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_PLATFORM_PCI=m
CONFIG_SWIOTLB_XEN=y
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-06 14:21 ` Konrad Rzeszutek Wilk
@ 2010-10-06 18:21 ` Bruce Edge
2010-10-08 16:48 ` Lin, Ray
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-06 18:21 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Wed, Oct 6, 2010 at 7:21 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, Oct 05, 2010 at 11:21:38AM -0700, Bruce Edge wrote:
>> On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> >> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
>> >>
>> >> Your devel/xen-pcifront-0.7 isn't visible:
>> >
>> > It should be now. I pushed it late on Friday and repushed it today since it had
>> > some commits with the wrong committer field.
>> >
>>
>> Is there anything special one needs to do when building this kernel?
>
> Wow. I've never seen those errors before. Can you send me your .config file
> so I can make sure this does not happend
Those errors were from after a 'make defconfig'. I assumed my config
was broken and that I should try the default .config to confirm that
that built before digging thought mine.
Adding the config entries below to the defconfig output does result in
a buildable kernel.
Testing out my PCI drivers with your recommended config now. Thanks.
-Bruce
>
> For me, I've these options defined:
>
> [konrad@tst002 bootstrap]$ cat linux-build/.config|grep XEN
> CONFIG_XEN=y
> CONFIG_XEN_PVHVM=y
> CONFIG_XEN_MAX_DOMAIN_MEMORY=8
> CONFIG_XEN_SAVE_RESTORE=y
> CONFIG_XEN_DEBUG_FS=y
> CONFIG_PCI_XEN=y
> CONFIG_XEN_PCIDEV_FRONTEND=y
> CONFIG_XEN_BLKDEV_FRONTEND=m
> # CONFIG_NETXEN_NIC is not set
> CONFIG_XEN_NETDEV_FRONTEND=m
> CONFIG_XEN_KBDDEV_FRONTEND=m
> CONFIG_HVC_XEN=y
> CONFIG_XEN_FBDEV_FRONTEND=m
> CONFIG_XEN_BALLOON=y
> CONFIG_XEN_SCRUB_PAGES=y
> CONFIG_XEN_DEV_EVTCHN=m
> CONFIG_XENFS=m
> CONFIG_XEN_COMPAT_XENFS=y
> CONFIG_XEN_SYS_HYPERVISOR=y
> CONFIG_XEN_PLATFORM_PCI=m
> CONFIG_SWIOTLB_XEN=y
>
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-06 18:21 ` Bruce Edge
@ 2010-10-08 16:48 ` Lin, Ray
2010-10-08 17:30 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 42+ messages in thread
From: Lin, Ray @ 2010-10-08 16:48 UTC (permalink / raw)
To: Bruce Edge, Konrad Rzeszutek Wilk; +Cc: xen-devel@lists.xensource.com
I just tried Bruce's latest kernel build based on Konrad's devel/xen-pcifront-0.7. It doesn't help the issue we have. The driver still doesn't recognize the source of interrupt, even though the interrupts happen.
124: 87792 0 0 0 0 0 12208 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
125: 89692 0 0 0 10308 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
126: 90979 0 9021 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
127: 100000 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
-Ray
-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Bruce Edge
Sent: Wednesday, October 06, 2010 11:21 AM
To: Konrad Rzeszutek Wilk
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Wed, Oct 6, 2010 at 7:21 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Tue, Oct 05, 2010 at 11:21:38AM -0700, Bruce Edge wrote:
>> On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> >> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
>> >>
>> >> Your devel/xen-pcifront-0.7 isn't visible:
>> >
>> > It should be now. I pushed it late on Friday and repushed it today
>> > since it had some commits with the wrong committer field.
>> >
>>
>> Is there anything special one needs to do when building this kernel?
>
> Wow. I've never seen those errors before. Can you send me your .config
> file so I can make sure this does not happend
Those errors were from after a 'make defconfig'. I assumed my config was broken and that I should try the default .config to confirm that that built before digging thought mine.
Adding the config entries below to the defconfig output does result in a buildable kernel.
Testing out my PCI drivers with your recommended config now. Thanks.
-Bruce
>
> For me, I've these options defined:
>
> [konrad@tst002 bootstrap]$ cat linux-build/.config|grep XEN
> CONFIG_XEN=y CONFIG_XEN_PVHVM=y
> CONFIG_XEN_MAX_DOMAIN_MEMORY=8
> CONFIG_XEN_SAVE_RESTORE=y
> CONFIG_XEN_DEBUG_FS=y
> CONFIG_PCI_XEN=y
> CONFIG_XEN_PCIDEV_FRONTEND=y
> CONFIG_XEN_BLKDEV_FRONTEND=m
> # CONFIG_NETXEN_NIC is not set
> CONFIG_XEN_NETDEV_FRONTEND=m
> CONFIG_XEN_KBDDEV_FRONTEND=m
> CONFIG_HVC_XEN=y
> CONFIG_XEN_FBDEV_FRONTEND=m
> CONFIG_XEN_BALLOON=y
> CONFIG_XEN_SCRUB_PAGES=y
> CONFIG_XEN_DEV_EVTCHN=m
> CONFIG_XENFS=m
> CONFIG_XEN_COMPAT_XENFS=y
> CONFIG_XEN_SYS_HYPERVISOR=y
> CONFIG_XEN_PLATFORM_PCI=m
> CONFIG_SWIOTLB_XEN=y
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-08 16:48 ` Lin, Ray
@ 2010-10-08 17:30 ` Konrad Rzeszutek Wilk
2010-10-08 17:40 ` Lin, Ray
2010-10-08 17:52 ` Bruce Edge
0 siblings, 2 replies; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-10-08 17:30 UTC (permalink / raw)
To: Lin, Ray; +Cc: xen-devel@lists.xensource.com, Bruce Edge
On Fri, Oct 08, 2010 at 10:48:01AM -0600, Lin, Ray wrote:
>
> I just tried Bruce's latest kernel build based on Konrad's devel/xen-pcifront-0.7. It doesn't help the issue we have. The driver still doesn't recognize the source of interrupt, even though the interrupts happen.
>
>
> 124: 87792 0 0 0 0 0 12208 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 125: 89692 0 0 0 10308 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 126: 90979 0 9021 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 127: 100000 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
>
And you still get on the Xen hypervisor side the DMAR failure of reading the memory?
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-08 17:30 ` Konrad Rzeszutek Wilk
@ 2010-10-08 17:40 ` Lin, Ray
2010-10-08 17:52 ` Bruce Edge
1 sibling, 0 replies; 42+ messages in thread
From: Lin, Ray @ 2010-10-08 17:40 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel@lists.xensource.com, Bruce Edge
I got this from dom0 when I brought up domU. There is no complaint from iommu.
-Ray
about to get started...
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d2 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
[ 5171.932037] vif2.0: no IPv6 routers present
[ 5178.026355] blkback: ring-ref 8, event-channel 87, protocol 1 (x86_64-abi)
[ 5221.204637] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[ 5221.204696] xen: registering gsi 32 triggering 0 polarity 1
[ 5221.204716] xen_allocate_pirq: returning irq 32 for gsi 32
[ 5221.204735] xen: --> irq=32
[ 5221.204749] Already setup the GSI :32
[ 5221.204764] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[ 5221.204819] pciback 0000:07:00.0: setting latency timer to 64
[ 5221.205376] alloc irq_desc for 474 on node 0
[ 5221.205400] alloc kstat_irqs on node 0
[ 5221.270496] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[ 5221.270536] xen: registering gsi 42 triggering 0 polarity 1
[ 5221.270576] xen_allocate_pirq: returning irq 42 for gsi 42
[ 5221.270595] xen: --> irq=42
[ 5221.270608] Already setup the GSI :42
[ 5221.270624] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[ 5221.270660] pciback 0000:07:00.1: setting latency timer to 64
[ 5221.271210] alloc irq_desc for 473 on node 0
[ 5221.271234] alloc kstat_irqs on node 0
[ 5221.333809] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[ 5221.333849] xen: registering gsi 47 triggering 0 polarity 1
[ 5221.333888] xen_allocate_pirq: returning irq 47 for gsi 47
[ 5221.333907] xen: --> irq=47
[ 5221.333921] Already setup the GSI :47
[ 5221.333936] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[ 5221.333972] pciback 0000:07:00.2: setting latency timer to 64
[ 5221.334523] alloc irq_desc for 472 on node 0
[ 5221.334546] alloc kstat_irqs on node 0
[ 5221.595255] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[ 5221.595340] xen: registering gsi 41 triggering 0 polarity 1
[ 5221.595373] xen_allocate_pirq: returning irq 41 for gsi 41
[ 5221.595422] xen: --> irq=41
[ 5221.595445] Already setup the GSI :41
[ 5221.595474] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[ 5221.595530] pciback 0000:07:00.3: setting latency timer to 64
[ 5221.596417] alloc irq_desc for 471 on node 0
[ 5221.596457] alloc kstat_irqs on node 0
-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
Sent: Friday, October 08, 2010 10:31 AM
To: Lin, Ray
Cc: Bruce Edge; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Fri, Oct 08, 2010 at 10:48:01AM -0600, Lin, Ray wrote:
>
> I just tried Bruce's latest kernel build based on Konrad's devel/xen-pcifront-0.7. It doesn't help the issue we have. The driver still doesn't recognize the source of interrupt, even though the interrupts happen.
>
>
> 124: 87792 0 0 0 0 0 12208 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 125: 89692 0 0 0 10308 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 126: 90979 0 9021 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
> 127: 100000 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
>
And you still get on the Xen hypervisor side the DMAR failure of reading the memory?
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-08 17:30 ` Konrad Rzeszutek Wilk
2010-10-08 17:40 ` Lin, Ray
@ 2010-10-08 17:52 ` Bruce Edge
2010-10-08 21:01 ` Lin, Ray
1 sibling, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-08 17:52 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel@lists.xensource.com, Lin, Ray
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
On Fri, Oct 8, 2010 at 10:30 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Fri, Oct 08, 2010 at 10:48:01AM -0600, Lin, Ray wrote:
>>
>> I just tried Bruce's latest kernel build based on Konrad's devel/xen-pcifront-0.7. It doesn't help the issue we have. The driver still doesn't recognize the source of interrupt, even though the interrupts happen.
>>
>>
>> 124: 87792 0 0 0 0 0 12208 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> 125: 89692 0 0 0 10308 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> 126: 90979 0 9021 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> 127: 100000 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>
>
The above was from xen-testing, I just switched Ray over to
xen-unstable. He's re-running now with the later hypervisor.
-Bruce
> And you still get on the Xen hypervisor side the DMAR failure of reading the memory?
>
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19 ` Bruce Edge
2010-10-01 23:30 ` Bruce Edge
@ 2010-10-08 17:56 ` Bruce Edge
2010-10-11 21:12 ` Bruce Edge
3 siblings, 0 replies; 42+ messages in thread
From: Bruce Edge @ 2010-10-08 17:56 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> One of our developers who is working on a tachyon driver is
>> complaining that the pvops domU kernel is not working for these MSI
>> interrupts.
>> This is using the current head of xen/2.6.32.x on both a single
>> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> 4.0.1, 4.0.2.rc1-pre and 4.1.
>
>
> I just checked on my SuperMicro X8DTN, this combination
> - For Dom0, git commit fe999249 (2.6.32.18)
> - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
> - For Hypervisor I used cs 21976, but found that the latest (22155) works too
>
Booting the above combination of xen/dom0/dpmU logs the following
messages on the dom0 console as soon as domU starts (no custom drivers
loaded yet):
(XEN) tmem: all pools frozen for all domains
(XEN) tmem: all pools thawed for all domains
(XEN) tmem: all pools frozen for all domains
(XEN) tmem: all pools thawed for all domains
mapping kernel into physical memory
about to get started...
(XEN) traps.c:2310:d1 Domain attempted WRMSR 000000000000008b from
0x0000000a00000000 to 0x0000000000000000.
(XEN) traps.c:2310:d1 Domain attempted WRMSR 000000000000008b from
0x0000000a00000000 to 0x0000000000000000.
(XEN) traps.c:2310:d1 Domain attempted WRMSR 000000000000008b from
0x0000000a00000000 to 0x0000000000000000.
(XEN) traps.c:2310:d1 Domain attempted WRMSR 000000000000008b from
0x0000000a00000000 to 0x0000000000000000.
(XEN) traps.c:2310:d1 Domain attempted WRMSR 000000000000008b from
0x0000000a00000000 to 0x0000000000000000.
(XEN) traps.c:2310:d1 Domain attempted WRMSR 000000000000008b from
0x0000000a00000000 to 0x0000000000000000.
[ 1784.608283] ------------[ cut here ]------------
[ 1784.608336] WARNING: at kernel/lockdep.c:2323
trace_hardirqs_on_caller+0x131/0x190()
[ 1784.608418] Hardware name: X8ST3
[ 1784.608445] Modules linked in: xt_physdev ipmi_msghandler ipv6
xenfs xen_gntdev xen_evtchn xen_pciback tun serio_raw joydev bridge
stp llc ioatdma dca usb_storage usbhid hid e1000e
[ 1784.608669] Pid: 11, comm: xenwatch Not tainted
2.6.32.18-pv-ops-stable-debug #1
[ 1784.608725] Call Trace:
[ 1784.608744] <IRQ> [<ffffffff81069fbb>] warn_slowpath_common+0x7b/0xc0
[ 1784.608807] [<ffffffff815de490>] ? _spin_unlock_irq+0x30/0x40
[ 1784.608853] [<ffffffff8106a014>] warn_slowpath_null+0x14/0x20
[ 1784.608899] [<ffffffff810a74b1>] trace_hardirqs_on_caller+0x131/0x190
[ 1784.608945] [<ffffffff810a751d>] trace_hardirqs_on+0xd/0x10
[ 1784.608991] [<ffffffff815de490>] _spin_unlock_irq+0x30/0x40
[ 1784.609039] [<ffffffff813b9736>] add_to_net_schedule_list_tail+0x86/0xd0
[ 1784.609085] [<ffffffff813ba948>] netif_be_int+0x38/0x160
[ 1784.609123] [<ffffffff810dd750>] handle_IRQ_event+0x50/0x160
[ 1784.609170] [<ffffffff810e05d9>] handle_level_irq+0x99/0x140
[ 1784.609217] [<ffffffff813adc09>] __xen_evtchn_do_upcall+0x1b9/0x1f0
[ 1784.609263] [<ffffffff813ae06d>] xen_evtchn_do_upcall+0x3d/0x60
[ 1784.609311] [<ffffffff8101537e>] xen_do_hypervisor_callback+0x1e/0x30
[ 1784.609356] <EOI> [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1784.609416] [<ffffffff8100940a>] ? hypercall_page+0x40a/0x1010
[ 1784.609461] [<ffffffff813b1a13>] ? xb_write+0x103/0x240
[ 1784.609499] [<ffffffff813b21c0>] ? xs_talkv+0x80/0x1f0
[ 1784.609537] [<ffffffff813b249b>] ? xs_single+0x4b/0x60
[ 1784.609575] [<ffffffff813b2b28>] ? xenbus_read+0x48/0x70
[ 1784.609613] [<ffffffff813bcf6e>] ? frontend_changed+0x47e/0x760
[ 1784.609659] [<ffffffff813b3e32>] ? xenbus_otherend_changed+0xd2/0x190
[ 1784.609736] [<ffffffff81010aff>] ? xen_restore_fl_direct_end+0x0/0x1
[ 1784.609782] [<ffffffff810a991d>] ? lock_release+0xed/0x230
[ 1784.609820] [<ffffffff813b4540>] ? frontend_changed+0x10/0x20
[ 1784.609866] [<ffffffff813b1df6>] ? xenwatch_thread+0x56/0x160
[ 1784.609912] [<ffffffff81090e70>] ? autoremove_wake_function+0x0/0x40
[ 1784.609958] [<ffffffff813b1da0>] ? xenwatch_thread+0x0/0x160
[ 1784.610004] [<ffffffff81090b36>] ? kthread+0x96/0xa0
[ 1784.610041] [<ffffffff8101522a>] ? child_rip+0xa/0x20
[ 1784.610077] [<ffffffff81014b90>] ? restore_args+0x0/0x30
[ 1784.610114] [<ffffffff81015220>] ? child_rip+0x0/0x20
[ 1784.610149] ---[ end trace db9e4f4f3b76b033 ]---
-Bruce
> with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
> a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>
> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
> 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
> 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>
> worked just fine (either defining pci=["..."] or just using pci-attach).
>
> But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
> that happy :-(
>
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* RE: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-08 17:52 ` Bruce Edge
@ 2010-10-08 21:01 ` Lin, Ray
0 siblings, 0 replies; 42+ messages in thread
From: Lin, Ray @ 2010-10-08 21:01 UTC (permalink / raw)
To: Bruce Edge, Konrad Rzeszutek Wilk; +Cc: xen-devel@lists.xensource.com
It doesn't make much difference with xen-unstable. Here is I got from dom0 after domU was brought up.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
(XEN) traps.c:2310:d8 Domain attempted WRMSR 000000000000008b from 0x0000001500000000 to 0x0000000000000000.
[11194.801585] vif8.0: no IPv6 routers present
[11200.947972] blkback: ring-ref 8, event-channel 87, protocol 1 (x86_64-abi)
[11201.106519] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[11201.106578] xen: registering gsi 32 triggering 0 polarity 1
[11201.106598] xen_allocate_pirq: returning irq 32 for gsi 32
[11201.106617] xen: --> irq=32
[11201.106629] Already setup the GSI :32
[11201.106645] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[11201.106880] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[11201.106909] xen: registering gsi 32 triggering 0 polarity 1
[11201.106928] xen_allocate_pirq: returning irq 32 for gsi 32
[11201.106947] xen: --> irq=32
[11201.106958] Already setup the GSI :32
[11201.106973] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[11201.107083] pciback 0000:07:00.0: PCI INT A disabled
[11201.107244] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[11201.107272] xen: registering gsi 32 triggering 0 polarity 1
[11201.107294] xen_allocate_pirq: returning irq 32 for gsi 32
[11201.107312] xen: --> irq=32
[11201.107353] Already setup the GSI :32
[11201.107370] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[11201.107481] pciback 0000:07:00.0: PCI INT A disabled
[11201.107637] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[11201.107665] xen: registering gsi 32 triggering 0 polarity 1
[11201.107684] xen_allocate_pirq: returning irq 32 for gsi 32
[11201.107703] xen: --> irq=32
[11201.107714] Already setup the GSI :32
[11201.107729] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[11201.107841] pciback 0000:07:00.0: PCI INT A disabled
[11201.108000] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[11201.108029] xen: registering gsi 32 triggering 0 polarity 1
[11201.108048] xen_allocate_pirq: returning irq 32 for gsi 32
[11201.108066] xen: --> irq=32
[11201.108077] Already setup the GSI :32
[11201.108092] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[11201.108292] pciback 0000:07:00.0: PCI INT A disabled
[11201.108471] pciback 0000:07:00.0: enabling device (0000 -> 0003)
[11201.108499] xen: registering gsi 32 triggering 0 polarity 1
[11201.108518] xen_allocate_pirq: returning irq 32 for gsi 32
[11201.108537] xen: --> irq=32
[11201.108548] Already setup the GSI :32
[11201.108563] pciback 0000:07:00.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32
[11201.109990] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[11201.110020] xen: registering gsi 42 triggering 0 polarity 1
[11201.110040] xen_allocate_pirq: returning irq 42 for gsi 42
[11201.110059] xen: --> irq=42
[11201.110070] Already setup the GSI :42
[11201.110085] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[11201.110298] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[11201.110326] xen: registering gsi 42 triggering 0 polarity 1
[11201.110345] xen_allocate_pirq: returning irq 42 for gsi 42
[11201.110364] xen: --> irq=42
[11201.110375] Already setup the GSI :42
[11201.110391] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[11201.110492] pciback 0000:07:00.1: PCI INT B disabled
[11201.110636] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[11201.110664] xen: registering gsi 42 triggering 0 polarity 1
[11201.110683] xen_allocate_pirq: returning irq 42 for gsi 42
[11201.110702] xen: --> irq=42
[11201.110713] Already setup the GSI :42
[11201.110728] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[11201.110833] pciback 0000:07:00.1: PCI INT B disabled
[11201.111079] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[11201.111109] xen: registering gsi 42 triggering 0 polarity 1
[11201.111128] xen_allocate_pirq: returning irq 42 for gsi 42
[11201.111146] xen: --> irq=42
[11201.111158] Already setup the GSI :42
[11201.111173] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[11201.111332] pciback 0000:07:00.1: PCI INT B disabled
[11201.113788] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[11201.113822] xen: registering gsi 42 triggering 0 polarity 1
[11201.113842] xen_allocate_pirq: returning irq 42 for gsi 42
[11201.113860] xen: --> irq=42
[11201.113885] Already setup the GSI :42
[11201.113901] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[11201.115796] pciback 0000:07:00.1: PCI INT B disabled
[11201.116421] pciback 0000:07:00.1: enabling device (0000 -> 0003)
[11201.116451] xen: registering gsi 42 triggering 0 polarity 1
[11201.116470] xen_allocate_pirq: returning irq 42 for gsi 42
[11201.116489] xen: --> irq=42
[11201.116532] Already setup the GSI :42
[11201.116548] pciback 0000:07:00.1: PCI INT B -> GSI 42 (level, low) -> IRQ 42
[11201.121218] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[11201.121251] xen: registering gsi 47 triggering 0 polarity 1
[11201.121270] xen_allocate_pirq: returning irq 47 for gsi 47
[11201.121290] xen: --> irq=47
[11201.121314] Already setup the GSI :47
[11201.121330] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[11201.122079] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[11201.122111] xen: registering gsi 47 triggering 0 polarity 1
[11201.122130] xen_allocate_pirq: returning irq 47 for gsi 47
[11201.122149] xen: --> irq=47
[11201.122167] Already setup the GSI :47
[11201.122182] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[11201.122305] pciback 0000:07:00.2: PCI INT C disabled
[11201.123677] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[11201.123709] xen: registering gsi 47 triggering 0 polarity 1
[11201.123729] xen_allocate_pirq: returning irq 47 for gsi 47
[11201.123749] xen: --> irq=47
[11201.123774] Already setup the GSI :47
[11201.123790] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[11201.123921] pciback 0000:07:00.2: PCI INT C disabled
[11201.124420] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[11201.124451] xen: registering gsi 47 triggering 0 polarity 1
[11201.124470] xen_allocate_pirq: returning irq 47 for gsi 47
[11201.124489] xen: --> irq=47
[11201.124501] Already setup the GSI :47
[11201.124515] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[11201.124737] pciback 0000:07:00.2: PCI INT C disabled
[11201.125484] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[11201.125515] xen: registering gsi 47 triggering 0 polarity 1
[11201.125535] xen_allocate_pirq: returning irq 47 for gsi 47
[11201.125555] xen: --> irq=47
[11201.125579] Already setup the GSI :47
[11201.125596] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[11201.126228] pciback 0000:07:00.2: PCI INT C disabled
[11201.126448] pciback 0000:07:00.2: enabling device (0000 -> 0003)
[11201.126478] xen: registering gsi 47 triggering 0 polarity 1
[11201.126497] xen_allocate_pirq: returning irq 47 for gsi 47
[11201.126515] xen: --> irq=47
[11201.126527] Already setup the GSI :47
[11201.126542] pciback 0000:07:00.2: PCI INT C -> GSI 47 (level, low) -> IRQ 47
[11201.129460] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[11201.129492] xen: registering gsi 41 triggering 0 polarity 1
[11201.129511] xen_allocate_pirq: returning irq 41 for gsi 41
[11201.129530] xen: --> irq=41
[11201.129541] Already setup the GSI :41
[11201.129556] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[11201.129856] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[11201.129886] xen: registering gsi 41 triggering 0 polarity 1
[11201.129906] xen_allocate_pirq: returning irq 41 for gsi 41
[11201.129924] xen: --> irq=41
[11201.129936] Already setup the GSI :41
[11201.129951] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[11201.130277] pciback 0000:07:00.3: PCI INT D disabled
[11201.130449] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[11201.130478] xen: registering gsi 41 triggering 0 polarity 1
[11201.130497] xen_allocate_pirq: returning irq 41 for gsi 41
[11201.130516] xen: --> irq=41
[11201.130528] Already setup the GSI :41
[11201.130543] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[11201.130871] pciback 0000:07:00.3: PCI INT D disabled
[11201.131025] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[11201.131054] xen: registering gsi 41 triggering 0 polarity 1
[11201.131073] xen_allocate_pirq: returning irq 41 for gsi 41
[11201.131092] xen: --> irq=41
[11201.131103] Already setup the GSI :41
[11201.131119] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[11201.131465] pciback 0000:07:00.3: PCI INT D disabled
[11201.132493] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[11201.132524] xen: registering gsi 41 triggering 0 polarity 1
[11201.132543] xen_allocate_pirq: returning irq 41 for gsi 41
[11201.132562] xen: --> irq=41
[11201.132574] Already setup the GSI :41
[11201.132591] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[11201.132992] pciback 0000:07:00.3: PCI INT D disabled
[11201.133155] pciback 0000:07:00.3: enabling device (0000 -> 0003)
[11201.133185] xen: registering gsi 41 triggering 0 polarity 1
[11201.133204] xen_allocate_pirq: returning irq 41 for gsi 41
[11201.133223] xen: --> irq=41
[11201.133234] Already setup the GSI :41
[11201.133249] pciback 0000:07:00.3: PCI INT D -> GSI 41 (level, low) -> IRQ 41
[11248.058409] pciback 0000:07:00.0: setting latency timer to 64
[11248.059095] alloc irq_desc for 458 on node 0
[11248.059120] alloc kstat_irqs on node 0
[11248.164759] pciback 0000:07:00.1: setting latency timer to 64
[11248.165337] alloc irq_desc for 457 on node 0
[11248.165362] alloc kstat_irqs on node 0
[11248.263380] pciback 0000:07:00.2: setting latency timer to 64
[11248.263993] alloc irq_desc for 456 on node 0
[11248.264018] alloc kstat_irqs on node 0
[11248.527645] pciback 0000:07:00.3: setting latency timer to 64
[11248.528260] alloc irq_desc for 455 on node 0
[11248.528287] alloc kstat_irqs on node 0
-----Original Message-----
From: Bruce Edge [mailto:bruce.edge@gmail.com]
Sent: Friday, October 08, 2010 10:52 AM
To: Konrad Rzeszutek Wilk
Cc: Lin, Ray; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
On Fri, Oct 8, 2010 at 10:30 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Fri, Oct 08, 2010 at 10:48:01AM -0600, Lin, Ray wrote:
>>
>> I just tried Bruce's latest kernel build based on Konrad's devel/xen-pcifront-0.7. It doesn't help the issue we have. The driver still doesn't recognize the source of interrupt, even though the interrupts happen.
>>
>>
>> 124: 87792 0 0 0 0
>> 0 12208 0 0 0 0 0
>> 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> 125: 89692 0 0 0 10308
>> 0 0 0 0 0 0 0
>> 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> 126: 90979 0 9021 0 0
>> 0 0 0 0 0 0 0
>> 0 0 xen-pirq-pcifront-msi HW_TACHYON
>> 127: 100000 0 0 0 0
>> 0 0 0 0 0 0 0
>> 0 0 xen-pirq-pcifront-msi HW_TACHYON
>>
>
The above was from xen-testing, I just switched Ray over to xen-unstable. He's re-running now with the later hypervisor.
-Bruce
> And you still get on the Xen hypervisor side the DMAR failure of reading the memory?
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
` (2 preceding siblings ...)
2010-10-08 17:56 ` Bruce Edge
@ 2010-10-11 21:12 ` Bruce Edge
2010-10-11 21:46 ` Konrad Rzeszutek Wilk
3 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-11 21:12 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> One of our developers who is working on a tachyon driver is
>> complaining that the pvops domU kernel is not working for these MSI
>> interrupts.
>> This is using the current head of xen/2.6.32.x on both a single
>> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> 4.0.1, 4.0.2.rc1-pre and 4.1.
>
>
> I just checked on my SuperMicro X8DTN, this combination
> - For Dom0, git commit fe999249 (2.6.32.18)
> - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
> - For Hypervisor I used cs 21976, but found that the latest (22155) works too
>
> with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
> a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>
> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
> 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
> 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>
> worked just fine (either defining pci=["..."] or just using pci-attach).
>
> But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
> that happy :-(
>
>
Konrad,
To try eliminate the remaining differences here, could you post your
dom0/domU config files?
I'd like to build the same kernels to get an apples->apples comparison.
Also, could you include your grub info and domU cfg file?
These may eliminate some of the remaining diffs in the configs and
show why your's works while mine does not.
Thanks
-Bruce
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-11 21:12 ` Bruce Edge
@ 2010-10-11 21:46 ` Konrad Rzeszutek Wilk
2010-10-13 21:36 ` Bruce Edge
0 siblings, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-10-11 21:46 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel
[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]
On Mon, Oct 11, 2010 at 02:12:22PM -0700, Bruce Edge wrote:
> On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> >> One of our developers who is working on a tachyon driver is
> >> complaining that the pvops domU kernel is not working for these MSI
> >> interrupts.
> >> This is using the current head of xen/2.6.32.x on both a single
> >> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> >> 4.0.1, 4.0.2.rc1-pre and 4.1.
> >
> >
> > I just checked on my SuperMicro X8DTN, this combination
> > - For Dom0, git commit fe999249 (2.6.32.18)
> > - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
> > - For Hypervisor I used cs 21976, but found that the latest (22155) works too
> >
> > with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
> > a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
> >
> > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
> > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
> > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
> > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
> > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
> > 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
> >
> > worked just fine (either defining pci=["..."] or just using pci-attach).
> >
> > But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
> > that happy :-(
> >
> >
>
> Konrad,
> To try eliminate the remaining differences here, could you post your
> dom0/domU config files?
Sure. See attached
> I'd like to build the same kernels to get an apples->apples comparison.
>
> Also, could you include your grub info and domU cfg file?
>
> These may eliminate some of the remaining diffs in the configs and
> show why your's works while mine does not.
>
> Thanks
>
> -Bruce
[-- Attachment #2: dom0-config --]
[-- Type: text/plain, Size: 97939 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.18
# Mon Oct 11 17:41:32 2010
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
# CONFIG_KTIME_SCALAR is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION="-stable"
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_TREE_PREEMPT_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=64
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
# CONFIG_USER_SCHED is not set
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
CONFIG_MM_OWNER=y
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
CONFIG_PERF_COUNTERS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_OPROFILE_IBS=y
CONFIG_OPROFILE_EVENT_MULTIPLEX=y
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_DMA_API_DEBUG=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_SLOW_WORK=y
CONFIG_SLOW_WORK_DEBUG=y
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_FREEZER=y
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_X2APIC=y
CONFIG_SPARSE_IRQ=y
CONFIG_NUMA_IRQ_DESC=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_VSMP is not set
# CONFIG_X86_UV is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=128
CONFIG_XEN_SAVE_RESTORE=y
CONFIG_XEN_DEBUG_FS=y
CONFIG_SWIOTLB_XEN=y
CONFIG_MICROCODE_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_DOM0_PCI=y
CONFIG_XEN_PCI_PASSTHROUGH=y
CONFIG_KVM_CLOCK=y
CONFIG_KVM_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
# CONFIG_MEMTEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
# CONFIG_X86_DS is not set
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
CONFIG_CALGARY_IOMMU=y
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
CONFIG_IOMMU_API=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=256
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
CONFIG_I8K=m
CONFIG_MICROCODE=m
CONFIG_MICROCODE_INTEL=y
CONFIG_MICROCODE_AMD=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
CONFIG_K8_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=9
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_MEMORY_PROBE=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_HAVE_MLOCK=y
CONFIG_HAVE_MLOCKED_PAGE_BIT=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
# CONFIG_HWPOISON_INJECT is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW_64K=y
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_EFI=y
CONFIG_SECCOMP=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_KEXEC_JUMP=y
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_PM=y
CONFIG_PM_DEBUG=y
CONFIG_PM_VERBOSE=y
CONFIG_CAN_PM_TRACE=y
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND=y
CONFIG_PM_TEST_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION_NVS=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_PM_RUNTIME=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_POWER_METER=m
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_PROCESSOR_AGGREGATOR=m
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_DEBUG_FUNC_TRACE=y
CONFIG_ACPI_PCI_SLOT=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_HOTPLUG_MEMORY=m
CONFIG_ACPI_SBS=m
CONFIG_SFI=y
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=m
CONFIG_CPU_FREQ_DEBUG=y
CONFIG_CPU_FREQ_STAT=m
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_POWERNOW_K8=m
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
CONFIG_X86_P4_CLOCKMOD=m
#
# shared options
#
CONFIG_X86_SPEEDSTEP_LIB=m
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
#
# Memory power savings
#
CONFIG_I7300_IDLE_IOAT_CHANNEL=y
CONFIG_I7300_IDLE=m
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_XEN=y
CONFIG_PCI_DOMAINS=y
CONFIG_DMAR=y
CONFIG_DMAR_DEFAULT_ON=y
CONFIG_DMAR_FLOPPY_WA=y
CONFIG_INTR_REMAP=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEAER=y
CONFIG_PCIE_ECRC=y
CONFIG_PCIEAER_INJECT=m
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
CONFIG_PCI_STUB=y
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_HT_IRQ=y
CONFIG_PCI_IOV=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
CONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=m
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=m
CONFIG_I82092=m
CONFIG_PCCARD_NONSTATIC=m
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_ACPI=y
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
# CONFIG_HOTPLUG_PCI_CPCI is not set
CONFIG_HOTPLUG_PCI_SHPC=m
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
CONFIG_XFRM_IPCOMP=m
CONFIG_NET_KEY=m
CONFIG_NET_KEY_MIGRATE=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_ARPD=y
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_PIMSM_V2=y
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_DCCP=m
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_TPROXY=m
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
CONFIG_NETFILTER_XT_TARGET_LED=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
CONFIG_NETFILTER_XT_MATCH_CLUSTER=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_RECENT=m
# CONFIG_NETFILTER_XT_MATCH_RECENT_PROC_COMPAT is not set
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=m
CONFIG_NETFILTER_XT_MATCH_STATE=y
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_NETFILTER_XT_MATCH_OSF=m
CONFIG_IP_VS=m
# CONFIG_IP_VS_IPV6 is not set
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m
#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=y
CONFIG_NF_CONNTRACK_IPV4=y
# CONFIG_NF_CONNTRACK_PROC_COMPAT is not set
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_DCCP=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_PROTO_UDPLITE=m
CONFIG_NF_NAT_PROTO_SCTP=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_SECURITY=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
#
# IPv6: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP6_NF_SECURITY=m
#
# DECnet: Netfilter Configuration
#
# CONFIG_DECNET_NF_GRABULATOR is not set
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_IP6=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100
CONFIG_IP_DCCP_TFRC_LIB=y
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
# CONFIG_NET_DCCPPROBE is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
CONFIG_SCTP_HMAC_SHA1=y
# CONFIG_SCTP_HMAC_MD5 is not set
CONFIG_RDS=m
CONFIG_RDS_RDMA=m
CONFIG_RDS_TCP=m
# CONFIG_RDS_DEBUG is not set
# CONFIG_TIPC is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_STP=m
CONFIG_GARP=m
CONFIG_BRIDGE=m
CONFIG_NET_DSA=y
CONFIG_NET_DSA_TAG_DSA=y
CONFIG_NET_DSA_TAG_EDSA=y
CONFIG_NET_DSA_TAG_TRAILER=y
CONFIG_NET_DSA_MV88E6XXX=y
CONFIG_NET_DSA_MV88E6060=y
CONFIG_NET_DSA_MV88E6XXX_NEED_PPU=y
CONFIG_NET_DSA_MV88E6131=y
CONFIG_NET_DSA_MV88E6123_61_65=y
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
CONFIG_DECNET=m
CONFIG_DECNET_ROUTER=y
CONFIG_LLC=m
# CONFIG_LLC2 is not set
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m
CONFIG_PHONET=m
CONFIG_IEEE802154=m
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_MULTIQ=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_DRR=m
CONFIG_NET_SCH_INGRESS=m
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
CONFIG_NET_CLS_CGROUP=y
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_ACT_SKBEDIT=m
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_NET_TCPPROBE is not set
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
CONFIG_AX25=m
CONFIG_AX25_DAMA_SLAVE=y
CONFIG_NETROM=m
CONFIG_ROSE=m
#
# AX.25 network device drivers
#
CONFIG_MKISS=m
CONFIG_6PACK=m
CONFIG_BPQETHER=m
CONFIG_BAYCOM_SER_FDX=m
CONFIG_BAYCOM_SER_HDX=m
CONFIG_BAYCOM_PAR=m
CONFIG_YAM=m
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
CONFIG_CAN_DEV=m
CONFIG_CAN_CALC_BITTIMING=y
CONFIG_CAN_SJA1000=m
CONFIG_CAN_SJA1000_PLATFORM=m
CONFIG_CAN_EMS_PCI=m
CONFIG_CAN_KVASER_PCI=m
#
# CAN USB interfaces
#
CONFIG_CAN_EMS_USB=m
# CONFIG_CAN_DEBUG_DEVICES is not set
CONFIG_IRDA=m
#
# IrDA protocols
#
CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
# CONFIG_IRDA_ULTRA is not set
#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
# CONFIG_IRDA_DEBUG is not set
#
# Infrared-port device drivers
#
#
# SIR device drivers
#
CONFIG_IRTTY_SIR=m
#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=m
CONFIG_ACTISYS_DONGLE=m
CONFIG_TEKRAM_DONGLE=m
CONFIG_TOIM3232_DONGLE=m
CONFIG_LITELINK_DONGLE=m
CONFIG_MA600_DONGLE=m
CONFIG_GIRBIL_DONGLE=m
CONFIG_MCP2120_DONGLE=m
CONFIG_OLD_BELKIN_DONGLE=m
CONFIG_ACT200L_DONGLE=m
CONFIG_KINGSUN_DONGLE=m
CONFIG_KSDAZZLE_DONGLE=m
CONFIG_KS959_DONGLE=m
#
# FIR device drivers
#
CONFIG_USB_IRDA=m
CONFIG_SIGMATEL_FIR=m
CONFIG_NSC_FIR=m
CONFIG_WINBOND_FIR=m
CONFIG_SMC_IRCC_FIR=m
CONFIG_ALI_FIR=m
CONFIG_VLSI_FIR=m
CONFIG_VIA_FIR=m
CONFIG_MCS_FIR=m
CONFIG_BT=m
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_CMTP=m
CONFIG_BT_HIDP=m
#
# Bluetooth device drivers
#
CONFIG_BT_HCIBTUSB=m
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m
CONFIG_BT_MRVL=m
CONFIG_BT_MRVL_SDIO=m
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
CONFIG_CFG80211_DEFAULT_PS=y
CONFIG_CFG80211_DEFAULT_PS_VALUE=1
CONFIG_CFG80211_DEBUGFS=y
# CONFIG_WIRELESS_OLD_REGULATORY is not set
CONFIG_WIRELESS_EXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_LIB80211=m
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
CONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_DEBUG_MENU is not set
CONFIG_WIMAX=m
CONFIG_WIMAX_DEBUG_LEVEL=8
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
CONFIG_NET_9P=m
CONFIG_NET_9P_VIRTIO=m
CONFIG_NET_9P_RDMA=m
# CONFIG_NET_9P_DEBUG is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
CONFIG_SYS_HYPERVISOR=y
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_TESTS is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set
CONFIG_MTD_AR7_PARTS=m
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m
CONFIG_MTD_OOPS=m
#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m
#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
# CONFIG_MTD_PHYSMAP is not set
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
CONFIG_MTD_ESB2ROM=m
CONFIG_MTD_CK804XROM=m
CONFIG_MTD_SCB2_FLASH=m
# CONFIG_MTD_NETtel is not set
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set
#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_ECC_SMC=y
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
# CONFIG_MTD_NAND_CAFE is not set
CONFIG_MTD_NAND_NANDSIM=m
# CONFIG_MTD_NAND_PLATFORM is not set
CONFIG_MTD_ALAUDA=m
# CONFIG_MTD_ONENAND is not set
#
# LPDDR flash memory drivers
#
CONFIG_MTD_LPDDR=m
CONFIG_MTD_QINFO_PROBE=m
#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
# CONFIG_MTD_UBI_GLUEBI is not set
#
# UBI debugging options
#
# CONFIG_MTD_UBI_DEBUG is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
CONFIG_PARIDE=m
#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=m
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPATC8=y
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRIQ=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m
CONFIG_BLK_CPQ_DA=m
CONFIG_BLK_CPQ_CISS_DA=m
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=m
CONFIG_BLK_DEV_UMEM=m
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_OSD=m
CONFIG_BLK_DEV_SX8=m
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_ATA_OVER_ETH=m
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_VIRTIO_BLK=m
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
CONFIG_SGI_IOC4=m
CONFIG_TIFM_CORE=m
CONFIG_TIFM_7XX1=m
CONFIG_ICS932S401=m
CONFIG_ENCLOSURE_SERVICES=m
# CONFIG_HP_ILO is not set
CONFIG_DELL_LAPTOP=m
CONFIG_ISL29003=m
# CONFIG_C2PORT is not set
#
# EEPROM support
#
CONFIG_EEPROM_AT24=m
CONFIG_EEPROM_LEGACY=m
CONFIG_EEPROM_MAX6875=m
CONFIG_EEPROM_93CX6=m
CONFIG_CB710_CORE=m
# CONFIG_CB710_DEBUG is not set
CONFIG_CB710_DEBUG_ASSUMPTIONS=y
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_ENCLOSURE=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
CONFIG_SCSI_SRP_TGT_ATTRS=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=m
CONFIG_SCSI_CXGB3_ISCSI=m
CONFIG_SCSI_BNX2_ISCSI=m
CONFIG_BE2ISCSI=m
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=4
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=4
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_MVSAS=m
# CONFIG_SCSI_MVSAS_DEBUG is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
CONFIG_SCSI_ARCMSR=m
CONFIG_SCSI_ARCMSR_AER=y
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_MPT2SAS=m
CONFIG_SCSI_MPT2SAS_MAX_SGE=128
CONFIG_SCSI_MPT2SAS_LOGGING=y
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
CONFIG_LIBFC=m
CONFIG_LIBFCOE=m
CONFIG_FCOE=m
CONFIG_FCOE_FNIC=m
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
# CONFIG_SCSI_IPR is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
CONFIG_SCSI_QLA_ISCSI=m
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_LPFC_DEBUG_FS is not set
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_DEBUG=m
CONFIG_SCSI_PMCRAID=m
CONFIG_SCSI_SRP=m
CONFIG_SCSI_BFA_FC=m
CONFIG_SCSI_LOWLEVEL_PCMCIA=y
# CONFIG_PCMCIA_FDOMAIN is not set
CONFIG_PCMCIA_QLOGIC=m
CONFIG_PCMCIA_SYM53C500=m
CONFIG_SCSI_DH=y
CONFIG_SCSI_DH_RDAC=m
CONFIG_SCSI_DH_HP_SW=m
CONFIG_SCSI_DH_EMC=m
CONFIG_SCSI_DH_ALUA=m
CONFIG_SCSI_OSD_INITIATOR=m
CONFIG_SCSI_OSD_ULD=m
CONFIG_SCSI_OSD_DPRINT_SENSE=1
# CONFIG_SCSI_OSD_DEBUG is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_SIL24=m
CONFIG_ATA_SFF=y
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=y
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INIC162X=m
CONFIG_PATA_ACPI=m
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATP867X=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_CMD640_PCI=m
CONFIG_PATA_CMD64X=m
CONFIG_PATA_CS5520=m
CONFIG_PATA_CS5530=m
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=m
CONFIG_ATA_GENERIC=m
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
# CONFIG_PATA_HPT3X3_DMA is not set
CONFIG_PATA_IT821X=m
CONFIG_PATA_IT8213=m
CONFIG_PATA_JMICRON=m
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_MPIIX=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87410=m
CONFIG_PATA_NS87415=m
CONFIG_PATA_OPTI=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PCMCIA=m
CONFIG_PATA_PDC_OLD=m
# CONFIG_PATA_RADISYS is not set
CONFIG_PATA_RDC=m
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
CONFIG_PATA_VIA=m
CONFIG_PATA_WINBOND=m
CONFIG_PATA_SCH=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
# CONFIG_MULTICORE_RAID456 is not set
CONFIG_MD_RAID6_PQ=m
CONFIG_ASYNC_RAID6_TEST=m
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=y
CONFIG_DM_DEBUG=y
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
CONFIG_DM_LOG_USERSPACE=m
CONFIG_DM_ZERO=y
CONFIG_DM_MULTIPATH=m
CONFIG_DM_MULTIPATH_QL=m
CONFIG_DM_MULTIPATH_ST=m
# CONFIG_DM_DELAY is not set
CONFIG_DM_UEVENT=y
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
CONFIG_FUSION_LAN=m
CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#
#
# You can enable one or both FireWire driver stacks.
#
#
# See the help texts for more information.
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_FIREWIRE_SBP2=m
CONFIG_FIREWIRE_NET=m
# CONFIG_IEEE1394 is not set
CONFIG_I2O=m
# CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_EXT_ADAPTEC_DMA64=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NETDEVICES=y
CONFIG_IFB=m
CONFIG_DUMMY=m
CONFIG_BONDING=m
CONFIG_MACVLAN=m
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_NET_SB1000=m
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_REALTEK_PHY=m
CONFIG_NATIONAL_PHY=m
CONFIG_STE10XP=m
CONFIG_LSI_ET1011C_PHY=m
CONFIG_FIXED_PHY=y
CONFIG_MDIO_BITBANG=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
CONFIG_ETHOC=m
CONFIG_DNET=m
CONFIG_NET_TULIP=y
CONFIG_DE2104X=m
CONFIG_DE2104X_DSL=0
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
CONFIG_TULIP_MMIO=y
# CONFIG_TULIP_NAPI is not set
CONFIG_DE4X5=m
CONFIG_WINBOND_840=m
CONFIG_DM9102=m
CONFIG_ULI526X=m
CONFIG_PCMCIA_XIRCOM=m
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=m
CONFIG_AMD8111_ETH=m
CONFIG_ADAPTEC_STARFIRE=m
CONFIG_B44=m
CONFIG_B44_PCI_AUTOSELECT=y
CONFIG_B44_PCICORE_AUTOSELECT=y
CONFIG_B44_PCI=y
CONFIG_FORCEDETH=m
CONFIG_FORCEDETH_NAPI=y
CONFIG_E100=m
CONFIG_FEALNX=m
CONFIG_NATSEMI=m
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_R6040=m
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SMSC9420=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
# CONFIG_KS8842 is not set
# CONFIG_KS8851_MLL is not set
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_SC92031=m
CONFIG_NET_POCKET=y
CONFIG_ATP=m
CONFIG_DE600=m
CONFIG_DE620=m
CONFIG_ATL2=m
CONFIG_NETDEV_1000=y
CONFIG_ACENIC=m
# CONFIG_ACENIC_OMIT_TIGON_I is not set
CONFIG_DL2K=m
CONFIG_E1000=m
CONFIG_E1000E=m
CONFIG_IP1000=m
CONFIG_IGB=m
CONFIG_IGB_DCA=y
CONFIG_IGBVF=m
CONFIG_NS83820=m
CONFIG_HAMACHI=m
CONFIG_YELLOWFIN=m
CONFIG_R8169=m
CONFIG_R8169_VLAN=y
CONFIG_SIS190=m
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=m
CONFIG_BNX2=m
CONFIG_CNIC=m
CONFIG_QLA3XXX=m
CONFIG_ATL1=m
CONFIG_ATL1E=m
CONFIG_ATL1C=m
CONFIG_JME=m
CONFIG_NETDEV_10000=y
CONFIG_MDIO=m
CONFIG_CHELSIO_T1=m
CONFIG_CHELSIO_T1_1G=y
CONFIG_CHELSIO_T3_DEPENDS=y
CONFIG_CHELSIO_T3=m
CONFIG_ENIC=m
CONFIG_IXGBE=m
CONFIG_IXGBE_DCA=y
CONFIG_IXGBE_DCB=y
CONFIG_IXGB=m
CONFIG_S2IO=m
CONFIG_VXGE=m
# CONFIG_VXGE_DEBUG_TRACE_ALL is not set
CONFIG_MYRI10GE=m
CONFIG_MYRI10GE_DCA=y
CONFIG_NETXEN_NIC=m
CONFIG_NIU=m
CONFIG_MLX4_EN=m
CONFIG_MLX4_CORE=m
CONFIG_MLX4_DEBUG=y
CONFIG_TEHUTI=m
CONFIG_BNX2X=m
CONFIG_QLGE=m
CONFIG_SFC=m
CONFIG_SFC_MTD=y
CONFIG_BE2NET=m
# CONFIG_TR is not set
CONFIG_WLAN=y
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
#
# WiMAX Wireless Broadband devices
#
CONFIG_WIMAX_I2400M=m
CONFIG_WIMAX_I2400M_USB=m
CONFIG_WIMAX_I2400M_SDIO=m
CONFIG_WIMAX_I2400M_DEBUG_LEVEL=8
#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_CDC_EEM=m
CONFIG_USB_NET_DM9601=m
CONFIG_USB_NET_SMSC95XX=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_MCS7830=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=m
CONFIG_USB_HSO=m
CONFIG_USB_NET_INT51X1=m
CONFIG_USB_CDC_PHONET=m
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=m
CONFIG_PCMCIA_3C574=m
CONFIG_PCMCIA_FMVJ18X=m
CONFIG_PCMCIA_PCNET=m
CONFIG_PCMCIA_NMCLAN=m
CONFIG_PCMCIA_SMC91C92=m
CONFIG_PCMCIA_XIRC2PS=m
CONFIG_PCMCIA_AXNET=m
# CONFIG_WAN is not set
CONFIG_ATM_DRIVERS=y
# CONFIG_ATM_DUMMY is not set
CONFIG_ATM_TCP=m
# CONFIG_ATM_LANAI is not set
CONFIG_ATM_ENI=m
# CONFIG_ATM_ENI_DEBUG is not set
# CONFIG_ATM_ENI_TUNE_BURST is not set
CONFIG_ATM_FIRESTREAM=m
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
# CONFIG_ATM_FORE200E is not set
CONFIG_ATM_HE=m
# CONFIG_ATM_HE_USE_SUNI is not set
CONFIG_ATM_SOLOS=m
CONFIG_IEEE802154_DRIVERS=m
CONFIG_IEEE802154_FAKEHARD=m
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
CONFIG_SKFP=m
# CONFIG_HIPPI is not set
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
# CONFIG_PPP_BSDCOMP is not set
CONFIG_PPP_MPPE=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
CONFIG_PPPOL2TP=m
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLHC=m
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_NET_FC=y
CONFIG_NETCONSOLE=m
CONFIG_NETCONSOLE_DYNAMIC=y
CONFIG_NETPOLL=y
CONFIG_NETPOLL_TRAP=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=m
CONFIG_VMXNET3=m
CONFIG_ISDN=y
CONFIG_ISDN_I4L=m
CONFIG_MISDN=m
CONFIG_MISDN_DSP=m
CONFIG_MISDN_L1OIP=m
#
# mISDN hardware drivers
#
CONFIG_MISDN_HFCPCI=m
CONFIG_MISDN_HFCMULTI=m
CONFIG_MISDN_HFCUSB=m
CONFIG_MISDN_AVMFRITZ=m
CONFIG_MISDN_SPEEDFAX=m
CONFIG_MISDN_INFINEON=m
CONFIG_MISDN_W6692=m
CONFIG_MISDN_NETJET=m
CONFIG_MISDN_IPAC=m
CONFIG_MISDN_ISAR=m
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_MPP=y
CONFIG_IPPP_FILTER=y
# CONFIG_ISDN_PPP_BSDCOMP is not set
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=y
#
# ISDN feature submodules
#
CONFIG_ISDN_DIVERSION=m
#
# ISDN4Linux hardware drivers
#
#
# Passive cards
#
CONFIG_ISDN_DRV_HISAX=m
#
# D-channel protocol features
#
CONFIG_HISAX_EURO=y
CONFIG_DE_AOC=y
CONFIG_HISAX_NO_SENDCOMPLETE=y
CONFIG_HISAX_NO_LLC=y
CONFIG_HISAX_NO_KEYPAD=y
CONFIG_HISAX_1TR6=y
CONFIG_HISAX_NI1=y
CONFIG_HISAX_MAX_CARDS=8
#
# HiSax supported cards
#
CONFIG_HISAX_16_3=y
CONFIG_HISAX_TELESPCI=y
CONFIG_HISAX_S0BOX=y
CONFIG_HISAX_FRITZPCI=y
CONFIG_HISAX_AVM_A1_PCMCIA=y
CONFIG_HISAX_ELSA=y
CONFIG_HISAX_DIEHLDIVA=y
CONFIG_HISAX_SEDLBAUER=y
CONFIG_HISAX_NETJET=y
CONFIG_HISAX_NETJET_U=y
CONFIG_HISAX_NICCY=y
CONFIG_HISAX_BKM_A4T=y
CONFIG_HISAX_SCT_QUADRO=y
CONFIG_HISAX_GAZEL=y
CONFIG_HISAX_HFC_PCI=y
CONFIG_HISAX_W6692=y
CONFIG_HISAX_HFC_SX=y
CONFIG_HISAX_ENTERNOW_PCI=y
# CONFIG_HISAX_DEBUG is not set
#
# HiSax PCMCIA card service modules
#
CONFIG_HISAX_SEDLBAUER_CS=m
CONFIG_HISAX_ELSA_CS=m
CONFIG_HISAX_AVM_A1_CS=m
CONFIG_HISAX_TELES_CS=m
#
# HiSax sub driver modules
#
CONFIG_HISAX_ST5481=m
# CONFIG_HISAX_HFCUSB is not set
CONFIG_HISAX_HFC4S8S=m
CONFIG_HISAX_FRITZ_PCIPNP=m
#
# Active cards
#
CONFIG_HYSDN=m
CONFIG_HYSDN_CAPI=y
CONFIG_ISDN_HDLC=m
CONFIG_ISDN_CAPI=m
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
# CONFIG_CAPI_TRACE is not set
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=m
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=m
CONFIG_ISDN_CAPI_CAPIDRV=m
#
# CAPI hardware drivers
#
CONFIG_CAPI_AVM=y
CONFIG_ISDN_DRV_AVMB1_B1PCI=m
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=m
CONFIG_ISDN_DRV_AVMB1_AVM_CS=m
CONFIG_ISDN_DRV_AVMB1_T1PCI=m
CONFIG_ISDN_DRV_AVMB1_C4=m
CONFIG_CAPI_EICON=y
CONFIG_ISDN_DIVAS=m
CONFIG_ISDN_DIVAS_BRIPCI=y
CONFIG_ISDN_DIVAS_PRIPCI=y
CONFIG_ISDN_DIVAS_DIVACAPI=m
CONFIG_ISDN_DIVAS_USERIDI=m
CONFIG_ISDN_DIVAS_MAINT=m
CONFIG_ISDN_DRV_GIGASET=m
CONFIG_GIGASET_BASE=m
CONFIG_GIGASET_M105=m
CONFIG_GIGASET_M101=m
# CONFIG_GIGASET_DEBUG is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_POLLDEV=m
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
CONFIG_XEN_KBDDEV_FRONTEND=y
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ADP5588=m
CONFIG_KEYBOARD_ATKBD=y
CONFIG_QT2160=m
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_LM8323 is not set
CONFIG_KEYBOARD_MAX7359=m
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_KEYBOARD_OPENCORES=m
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_SENTELIC=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_APPLETOUCH=m
CONFIG_MOUSE_BCM5974=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_MOUSE_SYNAPTICS_I2C=m
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
CONFIG_JOYSTICK_A3D=m
CONFIG_JOYSTICK_ADI=m
CONFIG_JOYSTICK_COBRA=m
CONFIG_JOYSTICK_GF2K=m
CONFIG_JOYSTICK_GRIP=m
CONFIG_JOYSTICK_GRIP_MP=m
CONFIG_JOYSTICK_GUILLEMOT=m
CONFIG_JOYSTICK_INTERACT=m
CONFIG_JOYSTICK_SIDEWINDER=m
CONFIG_JOYSTICK_TMDC=m
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=y
CONFIG_JOYSTICK_IFORCE_232=y
CONFIG_JOYSTICK_WARRIOR=m
CONFIG_JOYSTICK_MAGELLAN=m
CONFIG_JOYSTICK_SPACEORB=m
CONFIG_JOYSTICK_SPACEBALL=m
CONFIG_JOYSTICK_STINGER=m
CONFIG_JOYSTICK_TWIDJOY=m
CONFIG_JOYSTICK_ZHENHUA=m
CONFIG_JOYSTICK_DB9=m
CONFIG_JOYSTICK_GAMECON=m
CONFIG_JOYSTICK_TURBOGRAFX=m
CONFIG_JOYSTICK_JOYDUMP=m
CONFIG_JOYSTICK_XPAD=m
CONFIG_JOYSTICK_XPAD_FF=y
CONFIG_JOYSTICK_XPAD_LEDS=y
CONFIG_JOYSTICK_WALKERA0701=m
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=m
CONFIG_TABLET_USB_AIPTEK=m
CONFIG_TABLET_USB_GTCO=m
CONFIG_TABLET_USB_KBTAB=m
CONFIG_TABLET_USB_WACOM=m
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_AD7879_I2C=m
CONFIG_TOUCHSCREEN_AD7879=m
CONFIG_TOUCHSCREEN_EETI=m
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_TOUCHSCREEN_GUNZE=m
CONFIG_TOUCHSCREEN_ELO=m
CONFIG_TOUCHSCREEN_WACOM_W8001=m
CONFIG_TOUCHSCREEN_MCS5000=m
CONFIG_TOUCHSCREEN_MTOUCH=m
CONFIG_TOUCHSCREEN_INEXIO=m
CONFIG_TOUCHSCREEN_MK712=m
CONFIG_TOUCHSCREEN_PENMOUNT=m
CONFIG_TOUCHSCREEN_TOUCHRIGHT=m
CONFIG_TOUCHSCREEN_TOUCHWIN=m
# CONFIG_TOUCHSCREEN_WM97XX is not set
CONFIG_TOUCHSCREEN_USB_COMPOSITE=m
CONFIG_TOUCHSCREEN_USB_EGALAX=y
CONFIG_TOUCHSCREEN_USB_PANJIT=y
CONFIG_TOUCHSCREEN_USB_3M=y
CONFIG_TOUCHSCREEN_USB_ITM=y
CONFIG_TOUCHSCREEN_USB_ETURBO=y
CONFIG_TOUCHSCREEN_USB_GUNZE=y
CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y
CONFIG_TOUCHSCREEN_USB_IRTOUCH=y
CONFIG_TOUCHSCREEN_USB_IDEALTEK=y
CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y
CONFIG_TOUCHSCREEN_USB_GOTOP=y
CONFIG_TOUCHSCREEN_USB_JASTEC=y
CONFIG_TOUCHSCREEN_USB_E2I=y
CONFIG_TOUCHSCREEN_TOUCHIT213=m
CONFIG_TOUCHSCREEN_TSC2007=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_APANEL=m
CONFIG_INPUT_ATLAS_BTNS=m
CONFIG_INPUT_ATI_REMOTE=m
CONFIG_INPUT_ATI_REMOTE2=m
CONFIG_INPUT_KEYSPAN_REMOTE=m
CONFIG_INPUT_POWERMATE=m
CONFIG_INPUT_YEALINK=m
CONFIG_INPUT_CM109=m
CONFIG_INPUT_UINPUT=m
CONFIG_INPUT_WINBOND_CIR=m
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_DEVKMEM is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
CONFIG_SYNCLINK=m
CONFIG_SYNCLINKMP=m
CONFIG_SYNCLINK_GT=m
CONFIG_N_HDLC=m
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_STALDRV is not set
CONFIG_NOZOMI=m
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
CONFIG_VIRTIO_CONSOLE=m
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=m
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_VIA=m
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_NVRAM=y
CONFIG_R3964=m
# CONFIG_APPLICOM is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
CONFIG_CARDMAN_4000=m
CONFIG_CARDMAN_4040=m
CONFIG_IPWIRELESS=m
CONFIG_MWAVE=m
# CONFIG_PC8736x_GPIO is not set
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=8192
CONFIG_HPET=y
# CONFIG_HPET_MMAP is not set
CONFIG_HANGCHECK_TIMER=m
CONFIG_TCG_TPM=y
CONFIG_TCG_TIS=y
CONFIG_TCG_NSC=m
CONFIG_TCG_ATMEL=m
CONFIG_TCG_INFINEON=m
CONFIG_TELCLOCK=m
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCA=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=m
CONFIG_I2C_AMD756_S4882=m
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_ISCH=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_NFORCE2_S4985=m
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
CONFIG_I2C_SIS96X=m
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
#
# ACPI drivers
#
CONFIG_I2C_SCMI=m
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_SIMTEC=m
#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
# CONFIG_I2C_TAOS_EVM is not set
CONFIG_I2C_TINY_USB=m
#
# Graphics adapter I2C/DDC channel drivers
#
# CONFIG_I2C_VOODOO3 is not set
#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_PCA_PLATFORM=m
CONFIG_I2C_STUB=m
#
# Miscellaneous I2C Chip support
#
# CONFIG_DS1682 is not set
CONFIG_SENSORS_TSL2550=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set
# CONFIG_SPI is not set
#
# PPS support
#
CONFIG_PPS=m
# CONFIG_PPS_DEBUG is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
CONFIG_W1=m
CONFIG_W1_CON=y
#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_MATROX is not set
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m
#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2431=m
CONFIG_W1_SLAVE_DS2433=m
CONFIG_W1_SLAVE_DS2433_CRC=y
CONFIG_W1_SLAVE_DS2760=m
CONFIG_W1_SLAVE_BQ27000=m
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
CONFIG_WM8350_POWER=m
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_DS2782 is not set
CONFIG_BATTERY_BQ27x00=m
CONFIG_BATTERY_MAX17040=m
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_ABITUGURU3=m
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7473=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_G760A=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
CONFIG_SENSORS_LTC4215=m
CONFIG_SENSORS_LTC4245=m
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83L786NG=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_WM8350=m
CONFIG_SENSORS_HDAPS=m
CONFIG_SENSORS_APPLESMC=m
#
# ACPI drivers
#
CONFIG_SENSORS_ATK0110=m
CONFIG_SENSORS_LIS3LV02D=m
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_WM8350_WATCHDOG=m
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
# CONFIG_SC520_WDT is not set
CONFIG_SBC_FITPC2_WATCHDOG=m
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
CONFIG_IBMASR=m
# CONFIG_WAFER_WDT is not set
CONFIG_I6300ESB_WDT=m
CONFIG_ITCO_WDT=m
CONFIG_ITCO_VENDOR_SUPPORT=y
CONFIG_IT8712F_WDT=m
CONFIG_IT87_WDT=m
CONFIG_HP_WATCHDOG=m
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
CONFIG_SMSC_SCH311X_WDT=m
# CONFIG_SMSC37B787_WDT is not set
CONFIG_W83627HF_WDT=m
CONFIG_W83697HF_WDT=m
CONFIG_W83697UG_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
# CONFIG_SSB_B43_PCI_BRIDGE is not set
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
CONFIG_SSB_PCMCIAHOST=y
CONFIG_SSB_SDIOHOST_POSSIBLE=y
CONFIG_SSB_SDIOHOST=y
# CONFIG_SSB_DEBUG is not set
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
#
# Multifunction device drivers
#
CONFIG_MFD_CORE=m
CONFIG_MFD_SM501=m
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
CONFIG_MFD_WM8400=m
# CONFIG_MFD_WM831X is not set
CONFIG_MFD_WM8350=m
CONFIG_MFD_WM8350_I2C=m
# CONFIG_MFD_PCF50633 is not set
CONFIG_AB3100_CORE=m
CONFIG_AB3100_OTP=m
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=m
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
CONFIG_REGULATOR_USERSPACE_CONSUMER=m
CONFIG_REGULATOR_BQ24022=m
CONFIG_REGULATOR_MAX1586=m
CONFIG_REGULATOR_WM8350=m
CONFIG_REGULATOR_WM8400=m
CONFIG_REGULATOR_LP3971=m
CONFIG_REGULATOR_AB3100=m
CONFIG_REGULATOR_TPS65023=m
CONFIG_REGULATOR_TPS6507X=m
CONFIG_MEDIA_SUPPORT=m
#
# Multimedia core support
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_COMMON=m
CONFIG_VIDEO_ALLOW_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_DVB_CORE=m
CONFIG_VIDEO_MEDIA=m
#
# Multimedia drivers
#
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_MEDIA_ATTACH=y
CONFIG_MEDIA_TUNER=m
CONFIG_MEDIA_TUNER_CUSTOMISE=y
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA827X=m
CONFIG_MEDIA_TUNER_TDA18271=m
CONFIG_MEDIA_TUNER_TDA9887=m
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_MT2060=m
CONFIG_MEDIA_TUNER_MT2266=m
CONFIG_MEDIA_TUNER_MT2131=m
CONFIG_MEDIA_TUNER_QT1010=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_MEDIA_TUNER_MXL5005S=m
CONFIG_MEDIA_TUNER_MXL5007T=m
CONFIG_MEDIA_TUNER_MC44S803=m
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L1=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_VMALLOC=m
CONFIG_VIDEOBUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
CONFIG_VIDEO_IR_I2C=m
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS5345=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_M52790=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m
CONFIG_VIDEO_SAA6588=m
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_BT866=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_MT9V011=m
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_SAA717X=m
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_VPX3220=m
CONFIG_VIDEO_CX25840=m
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
# CONFIG_VIDEO_VIVI is not set
CONFIG_VIDEO_BT848=m
CONFIG_VIDEO_BT848_DVB=y
CONFIG_VIDEO_BWQCAM=m
CONFIG_VIDEO_CQCAM=m
CONFIG_VIDEO_W9966=m
# CONFIG_VIDEO_CPIA is not set
CONFIG_VIDEO_CPIA2=m
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_VIDEO_STRADIS=m
CONFIG_VIDEO_ZORAN=m
CONFIG_VIDEO_ZORAN_DC30=m
CONFIG_VIDEO_ZORAN_ZR36060=m
CONFIG_VIDEO_ZORAN_BUZ=m
CONFIG_VIDEO_ZORAN_DC10=m
CONFIG_VIDEO_ZORAN_LML33=m
CONFIG_VIDEO_ZORAN_LML33R10=m
CONFIG_VIDEO_ZORAN_AVS6EYES=m
CONFIG_VIDEO_MEYE=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_DVB=m
CONFIG_VIDEO_MXB=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_ALSA=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_MPEG=m
CONFIG_VIDEO_CX88_VP3054=m
CONFIG_VIDEO_CX23885=m
CONFIG_VIDEO_AU0828=m
CONFIG_VIDEO_IVTV=m
CONFIG_VIDEO_FB_IVTV=m
CONFIG_VIDEO_CX18=m
CONFIG_VIDEO_SAA7164=m
# CONFIG_VIDEO_CAFE_CCIC is not set
CONFIG_SOC_CAMERA=m
CONFIG_SOC_CAMERA_MT9M001=m
CONFIG_SOC_CAMERA_MT9M111=m
CONFIG_SOC_CAMERA_MT9T031=m
CONFIG_SOC_CAMERA_MT9V022=m
CONFIG_SOC_CAMERA_TW9910=m
CONFIG_SOC_CAMERA_PLATFORM=m
CONFIG_SOC_CAMERA_OV772X=m
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
CONFIG_USB_M5602=m
CONFIG_USB_STV06XX=m
CONFIG_USB_GL860=m
CONFIG_USB_GSPCA_CONEX=m
CONFIG_USB_GSPCA_ETOMS=m
CONFIG_USB_GSPCA_FINEPIX=m
CONFIG_USB_GSPCA_JEILINJ=m
CONFIG_USB_GSPCA_MARS=m
CONFIG_USB_GSPCA_MR97310A=m
CONFIG_USB_GSPCA_OV519=m
CONFIG_USB_GSPCA_OV534=m
CONFIG_USB_GSPCA_PAC207=m
CONFIG_USB_GSPCA_PAC7311=m
CONFIG_USB_GSPCA_SN9C20X=m
# CONFIG_USB_GSPCA_SN9C20X_EVDEV is not set
CONFIG_USB_GSPCA_SONIXB=m
CONFIG_USB_GSPCA_SONIXJ=m
CONFIG_USB_GSPCA_SPCA500=m
CONFIG_USB_GSPCA_SPCA501=m
CONFIG_USB_GSPCA_SPCA505=m
CONFIG_USB_GSPCA_SPCA506=m
CONFIG_USB_GSPCA_SPCA508=m
CONFIG_USB_GSPCA_SPCA561=m
CONFIG_USB_GSPCA_SQ905=m
CONFIG_USB_GSPCA_SQ905C=m
CONFIG_USB_GSPCA_STK014=m
CONFIG_USB_GSPCA_SUNPLUS=m
CONFIG_USB_GSPCA_T613=m
CONFIG_USB_GSPCA_TV8532=m
CONFIG_USB_GSPCA_VC032X=m
CONFIG_USB_GSPCA_ZC3XX=m
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_HDPVR=m
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_EM28XX_ALSA=m
CONFIG_VIDEO_EM28XX_DVB=m
CONFIG_VIDEO_CX231XX=m
CONFIG_VIDEO_CX231XX_ALSA=m
CONFIG_VIDEO_CX231XX_DVB=m
CONFIG_VIDEO_USBVISION=m
CONFIG_VIDEO_USBVIDEO=m
CONFIG_USB_VICAM=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_OV511 is not set
CONFIG_USB_SE401=m
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
CONFIG_USB_ZR364XX=m
CONFIG_USB_STKWEBCAM=m
CONFIG_USB_S2255=m
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
CONFIG_I2C_SI4713=m
CONFIG_RADIO_SI4713=m
CONFIG_USB_DSBR=m
CONFIG_RADIO_SI470X=y
CONFIG_USB_SI470X=m
CONFIG_I2C_SI470X=m
CONFIG_USB_MR800=m
# CONFIG_RADIO_TEA5764 is not set
CONFIG_DVB_MAX_ADAPTERS=8
CONFIG_DVB_DYNAMIC_MINORS=y
CONFIG_DVB_CAPTURE_DRIVERS=y
#
# Supported SAA7146 based PCI Adapters
#
CONFIG_TTPCI_EEPROM=m
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET_CORE=m
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m
#
# Supported USB Adapters
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
CONFIG_DVB_USB_M920X=m
CONFIG_DVB_USB_GL861=m
CONFIG_DVB_USB_AU6610=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_USB_OPERA1=m
CONFIG_DVB_USB_AF9005=m
CONFIG_DVB_USB_AF9005_REMOTE=m
CONFIG_DVB_USB_DW2102=m
CONFIG_DVB_USB_CINERGY_T2=m
CONFIG_DVB_USB_ANYSEE=m
CONFIG_DVB_USB_DTV5100=m
CONFIG_DVB_USB_AF9015=m
CONFIG_DVB_USB_CE6230=m
CONFIG_DVB_USB_FRIIO=m
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_SMS_SIANO_MDTV=m
#
# Siano module components
#
CONFIG_SMS_USB_DRV=m
CONFIG_SMS_SDIO_DRV=m
#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set
#
# Supported BT878 Adapters
#
CONFIG_DVB_BT8XX=m
#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m
#
# Supported SDMC DM1105 Adapters
#
CONFIG_DVB_DM1105=m
#
# Supported Earthsoft PT1 Adapters
#
CONFIG_DVB_PT1=m
#
# Supported DVB Frontends
#
CONFIG_DVB_FE_CUSTOMISE=y
#
# Customise DVB Frontends
#
#
# Multistandard (satellite) frontends
#
CONFIG_DVB_STB0899=m
CONFIG_DVB_STB6100=m
CONFIG_DVB_STV090x=m
CONFIG_DVB_STV6110x=m
#
# DVB-S (satellite) frontends
#
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_MT312=m
CONFIG_DVB_ZL10036=m
CONFIG_DVB_ZL10039=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_STV0288=m
CONFIG_DVB_STB6000=m
CONFIG_DVB_STV0299=m
CONFIG_DVB_STV6110=m
CONFIG_DVB_STV0900=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_TDA10086=m
CONFIG_DVB_TDA8261=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_TUNER_ITD1000=m
CONFIG_DVB_TUNER_CX24113=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TUA6100=m
CONFIG_DVB_CX24116=m
CONFIG_DVB_SI21XX=m
#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_DRX397XD=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
CONFIG_DVB_DIB7000M=m
CONFIG_DVB_DIB7000P=m
CONFIG_DVB_TDA10048=m
CONFIG_DVB_AF9013=m
#
# DVB-C (cable) frontends
#
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=m
CONFIG_DVB_STV0297=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
CONFIG_DVB_LGDT3304=m
CONFIG_DVB_LGDT3305=m
CONFIG_DVB_S5H1409=m
CONFIG_DVB_AU8522=m
CONFIG_DVB_S5H1411=m
#
# ISDB-T (terrestrial) frontends
#
CONFIG_DVB_S921=m
CONFIG_DVB_DIB8000=m
#
# Digital terrestrial only tuners/PLL
#
CONFIG_DVB_PLL=m
CONFIG_DVB_TUNER_DIB0070=m
#
# SEC control devices for DVB-S
#
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6405=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_ISL6423=m
CONFIG_DVB_LGS8GL5=m
CONFIG_DVB_LGS8GXX=m
#
# Tools to develop new frontends
#
CONFIG_DVB_DUMMY_FE=m
CONFIG_DAB=y
CONFIG_USB_DABUSB=m
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_SIS=y
CONFIG_AGP_VIA=y
CONFIG_VGA_ARB=y
CONFIG_DRM=m
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_TTM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_DDC=m
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
CONFIG_FB_RIVA=m
# CONFIG_FB_RIVA_I2C is not set
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_RIVA_BACKLIGHT=y
# CONFIG_FB_LE80578 is not set
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
# CONFIG_FB_SIS is not set
CONFIG_FB_VIA=m
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
CONFIG_FB_3DFX_ACCEL=y
CONFIG_FB_3DFX_I2C=y
CONFIG_FB_VOODOO1=m
# CONFIG_FB_VT8623 is not set
CONFIG_FB_TRIDENT=m
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_TMIO is not set
CONFIG_FB_SM501=m
CONFIG_FB_VIRTUAL=m
CONFIG_XEN_FBDEV_FRONTEND=y
CONFIG_FB_METRONOME=m
CONFIG_FB_MB862XX=m
CONFIG_FB_MB862XX_PCI_GDC=y
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_ILI9320 is not set
CONFIG_LCD_PLATFORM=m
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
CONFIG_BACKLIGHT_PROGEAR=m
CONFIG_BACKLIGHT_MBP_NVIDIA=m
# CONFIG_BACKLIGHT_SAHARA is not set
#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m
#
# Display hardware drivers
#
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=m
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_JACK=y
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_HRTIMER=m
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_VERBOSE is not set
CONFIG_SND_PCM_XRUN_DEBUG=y
CONFIG_SND_VMASTER=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=m
CONFIG_SND_OPL3_LIB_SEQ=m
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
CONFIG_SND_EMU10K1_SEQ=m
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
CONFIG_SND_PCSP=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_MTS64=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
CONFIG_SND_PORTMAN2X4=m
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_SB_COMMON=m
CONFIG_SND_SB16_DSP=m
CONFIG_SND_PCI=y
CONFIG_SND_AD1889=m
CONFIG_SND_ALS300=m
CONFIG_SND_ALS4000=m
CONFIG_SND_ALI5451=m
CONFIG_SND_ATIIXP=m
CONFIG_SND_ATIIXP_MODEM=m
CONFIG_SND_AU8810=m
CONFIG_SND_AU8820=m
CONFIG_SND_AU8830=m
# CONFIG_SND_AW2 is not set
CONFIG_SND_AZT3328=m
CONFIG_SND_BT87X=m
# CONFIG_SND_BT87X_OVERCLOCK is not set
CONFIG_SND_CA0106=m
CONFIG_SND_CMIPCI=m
CONFIG_SND_OXYGEN_LIB=m
CONFIG_SND_OXYGEN=m
CONFIG_SND_CS4281=m
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
CONFIG_SND_CS5530=m
CONFIG_SND_CS5535AUDIO=m
CONFIG_SND_CTXFI=m
CONFIG_SND_DARLA20=m
CONFIG_SND_GINA20=m
CONFIG_SND_LAYLA20=m
CONFIG_SND_DARLA24=m
CONFIG_SND_GINA24=m
CONFIG_SND_LAYLA24=m
CONFIG_SND_MONA=m
CONFIG_SND_MIA=m
CONFIG_SND_ECHO3G=m
CONFIG_SND_INDIGO=m
CONFIG_SND_INDIGOIO=m
CONFIG_SND_INDIGODJ=m
CONFIG_SND_INDIGOIOX=m
CONFIG_SND_INDIGODJX=m
CONFIG_SND_EMU10K1=m
CONFIG_SND_EMU10K1X=m
CONFIG_SND_ENS1370=m
CONFIG_SND_ENS1371=m
CONFIG_SND_ES1938=m
CONFIG_SND_ES1968=m
CONFIG_SND_FM801=m
CONFIG_SND_FM801_TEA575X_BOOL=y
CONFIG_SND_FM801_TEA575X=m
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_RECONFIG=y
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_JACK=y
CONFIG_SND_HDA_PATCH_LOADER=y
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_ATIHDMI=y
CONFIG_SND_HDA_CODEC_NVHDMI=y
CONFIG_SND_HDA_CODEC_INTELHDMI=y
CONFIG_SND_HDA_ELD=y
CONFIG_SND_HDA_CODEC_CIRRUS=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDSP=m
CONFIG_SND_HDSPM=m
CONFIG_SND_HIFIER=m
CONFIG_SND_ICE1712=m
CONFIG_SND_ICE1724=m
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
CONFIG_SND_KORG1212=m
CONFIG_SND_LX6464ES=m
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MIXART=m
CONFIG_SND_NM256=m
CONFIG_SND_PCXHR=m
CONFIG_SND_RIPTIDE=m
CONFIG_SND_RME32=m
CONFIG_SND_RME96=m
CONFIG_SND_RME9652=m
CONFIG_SND_SONICVIBES=m
CONFIG_SND_TRIDENT=m
CONFIG_SND_VIA82XX=m
CONFIG_SND_VIA82XX_MODEM=m
CONFIG_SND_VIRTUOSO=m
CONFIG_SND_VX222=m
CONFIG_SND_YMFPCI=m
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
CONFIG_SND_USB_CAIAQ=m
CONFIG_SND_USB_CAIAQ_INPUT=y
CONFIG_SND_USB_US122L=m
CONFIG_SND_PCMCIA=y
CONFIG_SND_VXPOCKET=m
CONFIG_SND_PDAUDIOCF=m
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
CONFIG_HIDRAW=y
#
# USB Input Devices
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CYPRESS=y
CONFIG_HID_DRAGONRISE=y
CONFIG_DRAGONRISE_FF=y
CONFIG_HID_EZKEY=y
CONFIG_HID_KYE=y
CONFIG_HID_GYRATION=y
CONFIG_HID_TWINHAN=y
CONFIG_HID_KENSINGTON=y
CONFIG_HID_LOGITECH=y
CONFIG_LOGITECH_FF=y
CONFIG_LOGIRUMBLEPAD2_FF=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_NTRIG=y
CONFIG_HID_PANTHERLORD=y
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
CONFIG_HID_SUNPLUS=y
CONFIG_HID_GREENASIA=y
CONFIG_GREENASIA_FF=y
CONFIG_HID_SMARTJOYPLUS=y
CONFIG_SMARTJOYPLUS_FF=y
CONFIG_HID_TOPSEED=y
CONFIG_HID_THRUSTMASTER=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_HID_WACOM=m
CONFIG_HID_ZEROPLUS=y
CONFIG_ZEROPLUS_FF=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=y
CONFIG_USB_WUSB=m
CONFIG_USB_WUSB_CBAF=m
# CONFIG_USB_WUSB_CBAF_DEBUG is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=m
# CONFIG_USB_XHCI_HCD_DEBUGGING is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_ISP1362_HCD=m
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
# CONFIG_USB_SL811_CS is not set
# CONFIG_USB_R8A66597_HCD is not set
CONFIG_USB_WHCI_HCD=m
CONFIG_USB_HWA_HCD=m
#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_WDM=m
CONFIG_USB_TMC=m
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m
#
# USB port drivers
#
CONFIG_USB_USS720=m
CONFIG_USB_SERIAL=m
CONFIG_USB_EZUSB=y
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CP210X=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_FUNSOFT=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_IUU=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_MOS7720=m
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_MOTOROLA=m
CONFIG_USB_SERIAL_NAVMAN=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_OTI6858=m
CONFIG_USB_SERIAL_QUALCOMM=m
CONFIG_USB_SERIAL_SPCP8X5=m
CONFIG_USB_SERIAL_HP4X=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_SIEMENS_MPI=m
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
CONFIG_USB_SERIAL_SYMBOL=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_OPTICON=m
CONFIG_USB_SERIAL_DEBUG=m
#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_SEVSEG=m
# CONFIG_USB_RIO500 is not set
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_BERRY_CHARGE=m
CONFIG_USB_LED=m
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_SISUSBVGA_CON=y
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_IOWARRIOR=m
# CONFIG_USB_TEST is not set
CONFIG_USB_ISIGHTFW=m
CONFIG_USB_VST=m
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m
CONFIG_USB_CXACRU=m
CONFIG_USB_UEAGLEATM=m
CONFIG_USB_XUSBATM=m
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#
CONFIG_USB_OTG_UTILS=y
CONFIG_NOP_USB_XCEIV=m
CONFIG_UWB=m
CONFIG_UWB_HWA=m
CONFIG_UWB_WHCI=m
CONFIG_UWB_WLP=m
CONFIG_UWB_I1480U=m
CONFIG_UWB_I1480U_WLP=m
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_SDIO_UART=m
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
CONFIG_MMC_RICOH_MMC=m
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMC_WBSD=m
# CONFIG_MMC_AT91 is not set
# CONFIG_MMC_ATMELMCI is not set
CONFIG_MMC_TIFM_SD=m
CONFIG_MMC_SDRICOH_CS=m
CONFIG_MMC_CB710=m
CONFIG_MMC_VIA_SDMMC=m
CONFIG_MEMSTICK=m
# CONFIG_MEMSTICK_DEBUG is not set
#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not set
CONFIG_MSPRO_BLOCK=m
#
# MemoryStick Host Controller Drivers
#
CONFIG_MEMSTICK_TIFM_MS=m
CONFIG_MEMSTICK_JMICRON_38X=m
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
#
# LED drivers
#
CONFIG_LEDS_ALIX2=m
# CONFIG_LEDS_PCA9532 is not set
CONFIG_LEDS_LP3944=m
CONFIG_LEDS_CLEVO_MAIL=m
# CONFIG_LEDS_PCA955X is not set
CONFIG_LEDS_WM8350=m
# CONFIG_LEDS_BD2802 is not set
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=m
CONFIG_LEDS_TRIGGER_HEARTBEAT=m
CONFIG_LEDS_TRIGGER_BACKLIGHT=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m
#
# iptables trigger is under Netfilter config (LED target)
#
CONFIG_ACCESSIBILITY=y
CONFIG_A11Y_BRAILLE_CONSOLE=y
CONFIG_INFINIBAND=m
CONFIG_INFINIBAND_USER_MAD=m
CONFIG_INFINIBAND_USER_ACCESS=m
CONFIG_INFINIBAND_USER_MEM=y
CONFIG_INFINIBAND_ADDR_TRANS=y
CONFIG_INFINIBAND_MTHCA=m
CONFIG_INFINIBAND_MTHCA_DEBUG=y
CONFIG_INFINIBAND_IPATH=m
CONFIG_INFINIBAND_AMSO1100=m
# CONFIG_INFINIBAND_AMSO1100_DEBUG is not set
CONFIG_INFINIBAND_CXGB3=m
# CONFIG_INFINIBAND_CXGB3_DEBUG is not set
CONFIG_MLX4_INFINIBAND=m
CONFIG_INFINIBAND_NES=m
# CONFIG_INFINIBAND_NES_DEBUG is not set
CONFIG_INFINIBAND_IPOIB=m
CONFIG_INFINIBAND_IPOIB_CM=y
CONFIG_INFINIBAND_IPOIB_DEBUG=y
CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y
CONFIG_INFINIBAND_SRP=m
CONFIG_INFINIBAND_ISER=m
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=m
CONFIG_EDAC_MM_EDAC=m
CONFIG_EDAC_AMD64=m
# CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
CONFIG_EDAC_E752X=m
CONFIG_EDAC_I82975X=m
CONFIG_EDAC_I3000=m
CONFIG_EDAC_I3200=m
CONFIG_EDAC_X38=m
CONFIG_EDAC_I5400=m
CONFIG_EDAC_I5000=m
CONFIG_EDAC_I5100=m
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1374=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_MAX6900=m
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_PCF8563=m
CONFIG_RTC_DRV_PCF8583=m
CONFIG_RTC_DRV_M41T80=m
CONFIG_RTC_DRV_M41T80_WDT=y
# CONFIG_RTC_DRV_S35390A is not set
CONFIG_RTC_DRV_FM3130=m
CONFIG_RTC_DRV_RX8581=m
CONFIG_RTC_DRV_RX8025=m
#
# SPI RTC drivers
#
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1286=m
CONFIG_RTC_DRV_DS1511=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_STK17TA8=m
# CONFIG_RTC_DRV_M48T86 is not set
CONFIG_RTC_DRV_M48T35=m
CONFIG_RTC_DRV_M48T59=m
CONFIG_RTC_DRV_BQ4802=m
CONFIG_RTC_DRV_V3020=m
CONFIG_RTC_DRV_WM8350=m
CONFIG_RTC_DRV_AB3100=m
#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y
#
# DMA Devices
#
CONFIG_ASYNC_TX_DISABLE_CHANNEL_SWITCH=y
CONFIG_INTEL_IOATDMA=m
CONFIG_DMA_ENGINE=y
#
# DMA Clients
#
CONFIG_NET_DMA=y
CONFIG_ASYNC_TX_DMA=y
# CONFIG_DMATEST is not set
CONFIG_DCA=m
CONFIG_AUXDISPLAY=y
CONFIG_KS0108=m
CONFIG_KS0108_PORT=0x378
CONFIG_KS0108_DELAY=2
CONFIG_CFAG12864B=m
CONFIG_CFAG12864B_RATE=20
CONFIG_UIO=m
CONFIG_UIO_CIF=m
CONFIG_UIO_PDRV=m
CONFIG_UIO_PDRV_GENIRQ=m
CONFIG_UIO_SMX=m
CONFIG_UIO_AEC=m
CONFIG_UIO_SERCOS3=m
CONFIG_UIO_PCI_GENERIC=m
#
# TI VLYNQ
#
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
CONFIG_XEN_PCIDEV_BE_DEBUG=y
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_MCE=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=y
CONFIG_XEN_S3=y
CONFIG_ACPI_PROCESSOR_XEN=y
CONFIG_XEN_PLATFORM_PCI=y
CONFIG_STAGING=y
# CONFIG_STAGING_EXCLUDE_BUILD is not set
# CONFIG_ET131X is not set
# CONFIG_SLICOSS is not set
# CONFIG_VIDEO_GO7007 is not set
# CONFIG_VIDEO_CX25821 is not set
# CONFIG_USB_IP_COMMON is not set
# CONFIG_W35UND is not set
# CONFIG_PRISM2_USB is not set
# CONFIG_ECHO is not set
# CONFIG_POCH is not set
# CONFIG_OTUS is not set
# CONFIG_RT2860 is not set
# CONFIG_RT2870 is not set
# CONFIG_RT3090 is not set
# CONFIG_COMEDI is not set
# CONFIG_ASUS_OLED is not set
# CONFIG_PANEL is not set
# CONFIG_ALTERA_PCIE_CHDMA is not set
# CONFIG_RTL8187SE is not set
# CONFIG_RTL8192SU is not set
# CONFIG_RTL8192E is not set
# CONFIG_TRANZPORT is not set
#
# Android
#
#
# Qualcomm MSM Camera And Video
#
#
# Camera Sensor Selection
#
# CONFIG_INPUT_GPIO is not set
# CONFIG_DST is not set
# CONFIG_POHMELFS is not set
# CONFIG_B3DFG is not set
# CONFIG_IDE_PHISON is not set
# CONFIG_PLAN9AUTH is not set
# CONFIG_LINE6_USB is not set
CONFIG_DRM_RADEON_KMS=y
# CONFIG_USB_SERIAL_QUATECH2 is not set
# CONFIG_USB_SERIAL_QUATECH_USB2 is not set
# CONFIG_VT6655 is not set
# CONFIG_VT6656 is not set
# CONFIG_FB_UDL is not set
# CONFIG_HYPERV is not set
# CONFIG_VME_BUS is not set
#
# RAR Register Driver
#
# CONFIG_RAR_REGISTER is not set
# CONFIG_IIO is not set
CONFIG_X86_PLATFORM_DEVICES=y
CONFIG_ACER_WMI=m
CONFIG_ACERHDF=m
CONFIG_ASUS_LAPTOP=m
CONFIG_DELL_WMI=m
CONFIG_FUJITSU_LAPTOP=m
# CONFIG_FUJITSU_LAPTOP_DEBUG is not set
CONFIG_HP_WMI=m
CONFIG_MSI_LAPTOP=m
CONFIG_PANASONIC_LAPTOP=m
CONFIG_COMPAL_LAPTOP=m
CONFIG_SONY_LAPTOP=m
CONFIG_SONYPI_COMPAT=y
CONFIG_THINKPAD_ACPI=m
# CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set
# CONFIG_THINKPAD_ACPI_DEBUG is not set
# CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set
CONFIG_THINKPAD_ACPI_VIDEO=y
CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y
# CONFIG_INTEL_MENLOW is not set
CONFIG_EEEPC_LAPTOP=m
CONFIG_ACPI_WMI=m
# CONFIG_ACPI_ASUS is not set
CONFIG_TOPSTAR_LAPTOP=m
CONFIG_ACPI_TOSHIBA=m
#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_EDD_OFF is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=y
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y
CONFIG_ISCSI_IBFT_FIND=y
CONFIG_ISCSI_IBFT=m
#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_FS_XIP=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_DLM=y
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_O2CB=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
# CONFIG_OCFS2_FS_STATS is not set
# CONFIG_OCFS2_DEBUG_MASKLOG is not set
# CONFIG_OCFS2_DEBUG_FS is not set
# CONFIG_OCFS2_FS_POSIX_ACL is not set
CONFIG_BTRFS_FS=m
CONFIG_BTRFS_FS_POSIX_ACL=y
CONFIG_NILFS2_FS=m
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_PRINT_QUOTA_WARNING is not set
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_CUSE=m
CONFIG_GENERIC_ACL=y
#
# Caches
#
CONFIG_FSCACHE=m
CONFIG_FSCACHE_STATS=y
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
CONFIG_FSCACHE_OBJECT_LIST=y
CONFIG_CACHEFILES=m
# CONFIG_CACHEFILES_DEBUG is not set
# CONFIG_CACHEFILES_HISTOGRAM is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
CONFIG_JFFS2_SUMMARY=y
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
# CONFIG_JFFS2_COMPRESSION_OPTIONS is not set
CONFIG_JFFS2_ZLIB=y
# CONFIG_JFFS2_LZO is not set
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
CONFIG_UBIFS_FS=m
CONFIG_UBIFS_FS_XATTR=y
# CONFIG_UBIFS_FS_ADVANCED_COMPR is not set
CONFIG_UBIFS_FS_LZO=y
CONFIG_UBIFS_FS_ZLIB=y
# CONFIG_UBIFS_FS_DEBUG is not set
CONFIG_CRAMFS=m
CONFIG_SQUASHFS=m
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=m
CONFIG_OMFS_FS=m
# CONFIG_HPFS_FS is not set
CONFIG_QNX4FS_FS=m
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
# CONFIG_ROMFS_BACKED_BY_MTD is not set
# CONFIG_ROMFS_BACKED_BY_BOTH is not set
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_UFS_DEBUG is not set
CONFIG_EXOFS_FS=m
# CONFIG_EXOFS_DEBUG is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_V4_1=y
CONFIG_NFS_FSCACHE=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_SUNRPC_XPRT_RDMA=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_UPCALL=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_NCP_FS=m
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_CODA_FS=m
# CONFIG_AFS_FS is not set
CONFIG_9P_FS=m
CONFIG_9P_FSCACHE=y
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
CONFIG_DLM_DEBUG=y
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
CONFIG_STRIP_ASM_SYMS=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
CONFIG_HEADERS_CHECK=y
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_RING_BUFFER=y
CONFIG_RING_BUFFER_ALLOW_SWAP=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
# CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set
# CONFIG_BUILD_DOCSRC is not set
# CONFIG_DYNAMIC_DEBUG is not set
CONFIG_DMA_API_DEBUG=y
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_EARLY_PRINTK_DBGP=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set
#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
# CONFIG_SECURITY_PATH is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
# CONFIG_SECURITY_ROOTPLUG is not set
CONFIG_INTEL_TXT=y
CONFIG_LSM_MMAP_MIN_ADDR=65536
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
CONFIG_IMA=y
CONFIG_IMA_MEASURE_PCR_IDX=10
CONFIG_IMA_AUDIT=y
CONFIG_IMA_LSM_RULES=y
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y
CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_FIPS=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m
#
# Block modes
#
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_LRW=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=m
CONFIG_CRYPTO_FPU=m
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_VMAC=m
#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CRC32C_INTEL=m
CONFIG_CRYPTO_GHASH=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_RMD128=m
CONFIG_CRYPTO_RMD160=m
CONFIG_CRYPTO_RMD256=m
CONFIG_CRYPTO_RMD320=m
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_WP512=m
#
# Ciphers
#
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_X86_64=m
CONFIG_CRYPTO_AES_NI_INTEL=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_KHAZAD=m
# CONFIG_CRYPTO_SALSA20 is not set
CONFIG_CRYPTO_SALSA20_X86_64=m
CONFIG_CRYPTO_SEED=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_TEA=m
# CONFIG_CRYPTO_TWOFISH is not set
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_X86_64=m
#
# Compression
#
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_ZLIB=m
CONFIG_CRYPTO_LZO=m
#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
CONFIG_CRYPTO_DEV_HIFN_795X=m
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
CONFIG_VIRTIO=m
CONFIG_VIRTIO_RING=m
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m
# CONFIG_BINARY_PRINTF is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_NLATTR=y
[-- Attachment #3: domU-config --]
[-- Type: text/plain, Size: 68662 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.36-rc6
# Thu Oct 7 00:23:38 2010
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_EARLY_RES=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
# CONFIG_KTIME_SCALAR is not set
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION="NEB"
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_LZO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=64
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=18
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_DEVICE is not set
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
# CONFIG_CGROUP_MEM_RES_CTLR is not set
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_BLK_CGROUP is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
CONFIG_RELAY=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE="early-devs"
CONFIG_INITRAMFS_ROOT_UID=0
CONFIG_INITRAMFS_ROOT_GID=0
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_LZO=y
# CONFIG_INITRAMFS_COMPRESSION_NONE is not set
CONFIG_INITRAMFS_COMPRESSION_GZIP=y
# CONFIG_INITRAMFS_COMPRESSION_BZIP2 is not set
# CONFIG_INITRAMFS_COMPRESSION_LZMA is not set
# CONFIG_INITRAMFS_COMPRESSION_LZO is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_PERF_COUNTERS is not set
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
# CONFIG_OPROFILE is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_OPTPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=y
#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_SPARSE_IRQ=y
CONFIG_NUMA_IRQ_DESC=y
CONFIG_X86_MPPARSE=y
# CONFIG_X86_EXTENDED_PLATFORM is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_PARAVIRT_GUEST=y
CONFIG_XEN=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=8
CONFIG_XEN_SAVE_RESTORE=y
CONFIG_XEN_DEBUG_FS=y
CONFIG_KVM_CLOCK=y
CONFIG_KVM_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=7
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
CONFIG_CALGARY_IOMMU=y
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
CONFIG_IOMMU_API=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
CONFIG_X86_MCE_INJECT=y
CONFIG_X86_THERMAL_VECTOR=y
# CONFIG_I8K is not set
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
CONFIG_MICROCODE_AMD=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
CONFIG_K8_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y
CONFIG_SPARSEMEM_VMEMMAP=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_COMPACTION is not set
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW_64K=y
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_EFI=y
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
# CONFIG_KEXEC_JUMP is not set
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_ADVANCED_DEBUG is not set
CONFIG_PM_VERBOSE=y
CONFIG_CAN_PM_TRACE=y
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_NVS=y
CONFIG_SUSPEND=y
# CONFIG_PM_TEST_SUSPEND is not set
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
# CONFIG_PM_RUNTIME is not set
CONFIG_PM_OPS=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
# CONFIG_ACPI_POWER_METER is not set
CONFIG_ACPI_SYSFS_POWER=y
# CONFIG_ACPI_EC_DEBUGFS is not set
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_DEBUG_FUNC_TRACE is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_APEI is not set
# CONFIG_SFI is not set
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_DEBUG=y
# CONFIG_CPU_FREQ_STAT is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
#
# CPUFreq processor drivers
#
# CONFIG_X86_PCC_CPUFREQ is not set
CONFIG_X86_ACPI_CPUFREQ=y
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_P4_CLOCKMOD is not set
#
# shared options
#
# CONFIG_X86_SPEEDSTEP_LIB is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_INTEL_IDLE is not set
#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_XEN=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
CONFIG_DMAR=y
# CONFIG_DMAR_DEFAULT_ON is not set
CONFIG_DMAR_FLOPPY_WA=y
# CONFIG_INTR_REMAP is not set
CONFIG_PCIEPORTBUS=y
# CONFIG_HOTPLUG_PCI_PCIE is not set
CONFIG_PCIEAER=y
CONFIG_PCIE_ECRC=y
# CONFIG_PCIEAER_INJECT is not set
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_XEN_PCIDEV_FRONTEND=y
CONFIG_HT_IRQ=y
CONFIG_PCI_IOV=y
CONFIG_PCI_IOAPIC=y
CONFIG_ISA_DMA_API=y
CONFIG_K8_NB=y
CONFIG_PCCARD=y
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
CONFIG_PCCARD_NONSTATIC=y
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
CONFIG_IP_MROUTE=y
# CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_LRO=y
# CONFIG_INET_DIAG is not set
CONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not set
CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
# CONFIG_TCP_CONG_YEAH is not set
# CONFIG_TCP_CONG_ILLINOIS is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=y
CONFIG_INET6_ESP=y
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
CONFIG_INET6_XFRM_MODE_TUNNEL=y
CONFIG_INET6_XFRM_MODE_BEET=y
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_NETFILTER_ADVANCED is not set
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_FTP=y
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_CT_NETLINK=y
CONFIG_NETFILTER_XTABLES=y
#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=m
#
# Xtables targets
#
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=y
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
CONFIG_NETFILTER_XT_TARGET_SECMARK=y
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_POLICY=y
CONFIG_NETFILTER_XT_MATCH_STATE=y
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=y
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_NF_NAT=y
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_NF_NAT_FTP=y
CONFIG_NF_NAT_IRC=y
# CONFIG_NF_NAT_TFTP is not set
# CONFIG_NF_NAT_AMANDA is not set
# CONFIG_NF_NAT_PPTP is not set
# CONFIG_NF_NAT_H323 is not set
CONFIG_NF_NAT_SIP=y
CONFIG_IP_NF_MANGLE=y
#
# IPv6: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV6=y
CONFIG_IP6_NF_IPTABLES=y
CONFIG_IP6_NF_MATCH_IPV6HEADER=y
CONFIG_IP6_NF_TARGET_LOG=y
CONFIG_IP6_NF_FILTER=y
CONFIG_IP6_NF_TARGET_REJECT=y
CONFIG_IP6_NF_MANGLE=y
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
CONFIG_STP=y
CONFIG_BRIDGE=y
CONFIG_BRIDGE_IGMP_SNOOPING=y
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
CONFIG_LLC=y
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_INGRESS is not set
#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
# CONFIG_NET_CLS_CGROUP is not set
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
# CONFIG_NET_EMATCH_CMP is not set
# CONFIG_NET_EMATCH_NBYTE is not set
# CONFIG_NET_EMATCH_U32 is not set
# CONFIG_NET_EMATCH_META is not set
# CONFIG_NET_EMATCH_TEXT is not set
CONFIG_NET_CLS_ACT=y
# CONFIG_NET_ACT_POLICE is not set
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_IPT is not set
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set
CONFIG_DNS_RESOLVER=y
CONFIG_RPS=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_NET_DROP_MONITOR is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
# CONFIG_WIRELESS is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_INPUT=y
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
CONFIG_DEBUG_DEVRES=y
CONFIG_SYS_HYPERVISOR=y
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_XEN_BLKDEV_FRONTEND=m
CONFIG_VIRTIO_BLK=m
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_AD525X_DPOT is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_CS5535_MFGPT is not set
# CONFIG_HP_ILO is not set
# CONFIG_ISL29003 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1780 is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_VMWARE_BALLOON is not set
# CONFIG_BMP085 is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_CB710_CORE is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_SCSI_MOD=m
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=m
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_FC_TGT_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
CONFIG_SCSI_SAS_HOST_SMP=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
CONFIG_BLK_DEV_3W_XXXX_RAID=m
# CONFIG_SCSI_HPSA is not set
CONFIG_SCSI_3W_9XXX=m
# CONFIG_SCSI_3W_SAS is not set
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
CONFIG_AIC79XX_DEBUG_ENABLE=y
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC94XX=m
# CONFIG_AIC94XX_DEBUG is not set
CONFIG_SCSI_MVSAS=m
# CONFIG_SCSI_MVSAS_DEBUG is not set
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_ADVANSYS=m
CONFIG_SCSI_ARCMSR=m
CONFIG_SCSI_ARCMSR_AER=y
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_MEGARAID_LEGACY=m
CONFIG_MEGARAID_SAS=m
CONFIG_SCSI_MPT2SAS=m
CONFIG_SCSI_MPT2SAS_MAX_SGE=128
CONFIG_SCSI_MPT2SAS_LOGGING=y
CONFIG_SCSI_HPTIOP=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_VMWARE_PVSCSI is not set
CONFIG_LIBFC=m
CONFIG_LIBFCOE=m
CONFIG_FCOE=m
# CONFIG_FCOE_FNIC is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_STEX=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA_FC=m
# CONFIG_SCSI_QLA_ISCSI is not set
CONFIG_SCSI_LPFC=m
# CONFIG_SCSI_LPFC_DEBUG_FS is not set
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_DEBUG=m
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
CONFIG_SCSI_SRP=m
# CONFIG_SCSI_BFA_FC is not set
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=m
# CONFIG_SATA_AHCI_PLATFORM is not set
CONFIG_SATA_INIC162X=m
CONFIG_SATA_SIL24=m
CONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
CONFIG_PDC_ADMA=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_SX4=m
CONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIS=m
CONFIG_SATA_SVW=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
CONFIG_PATA_EFAR=m
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
CONFIG_PATA_MARVELL=m
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
CONFIG_PATA_PDC_OLD=m
CONFIG_PATA_RADISYS=m
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SCH=m
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
CONFIG_PATA_SIS=m
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
CONFIG_PATA_WINBOND=m
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
CONFIG_PATA_PCMCIA=m
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set
CONFIG_ATA_GENERIC=m
CONFIG_PATA_LEGACY=m
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
# CONFIG_MULTICORE_RAID456 is not set
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=m
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
# CONFIG_DM_LOG_USERSPACE is not set
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
# CONFIG_DM_MULTIPATH_QL is not set
# CONFIG_DM_MULTIPATH_ST is not set
CONFIG_DM_DELAY=m
# CONFIG_DM_UEVENT is not set
CONFIG_FUSION=y
CONFIG_FUSION_SPI=m
CONFIG_FUSION_FC=m
CONFIG_FUSION_SAS=m
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_CTL=m
# CONFIG_FUSION_LOGGING is not set
#
# IEEE 1394 (FireWire) support
#
#
# You can enable one or both FireWire driver stacks.
#
#
# The newer stack is recommended.
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_FIREWIRE_NOSY is not set
# CONFIG_I2O is not set
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
CONFIG_NETDEVICES=y
# CONFIG_IFB is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=m
CONFIG_DAVICOM_PHY=m
CONFIG_QSEMI_PHY=m
CONFIG_LXT_PHY=m
CONFIG_CICADA_PHY=m
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
# CONFIG_ICPLUS_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MICREL_PHY is not set
CONFIG_FIXED_PHY=y
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_HAPPYMEAL=m
CONFIG_SUNGEM=m
CONFIG_CASSINI=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
# CONFIG_ETHOC is not set
# CONFIG_DNET is not set
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_PCMCIA_XIRCOM is not set
# CONFIG_HP100 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_KSZ884X_PCI is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=y
CONFIG_E100=m
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
# CONFIG_8139CP is not set
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SMSC9420 is not set
# CONFIG_SUNDANCE is not set
CONFIG_TLAN=m
# CONFIG_KS8851_MLL is not set
CONFIG_VIA_RHINE=m
# CONFIG_VIA_RHINE_MMIO is not set
CONFIG_SC92031=m
# CONFIG_ATL2 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=m
CONFIG_E1000E=m
# CONFIG_IP1000 is not set
CONFIG_IGB=m
CONFIG_IGBVF=m
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
CONFIG_SKGE=m
# CONFIG_SKGE_DEBUG is not set
CONFIG_SKY2=m
# CONFIG_SKY2_DEBUG is not set
CONFIG_VIA_VELOCITY=m
CONFIG_TIGON3=y
CONFIG_BNX2=m
# CONFIG_CNIC is not set
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_JME is not set
CONFIG_NETDEV_10000=y
CONFIG_MDIO=m
# CONFIG_CHELSIO_T1 is not set
CONFIG_CHELSIO_T3_DEPENDS=y
# CONFIG_CHELSIO_T3 is not set
CONFIG_CHELSIO_T4_DEPENDS=y
# CONFIG_CHELSIO_T4 is not set
CONFIG_CHELSIO_T4VF_DEPENDS=y
# CONFIG_CHELSIO_T4VF is not set
# CONFIG_ENIC is not set
CONFIG_IXGBE=m
# CONFIG_IXGBEVF is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_NIU is not set
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TEHUTI is not set
CONFIG_BNX2X=m
# CONFIG_QLCNIC is not set
# CONFIG_QLGE is not set
# CONFIG_SFC is not set
# CONFIG_BE2NET is not set
CONFIG_TR=y
# CONFIG_IBMOL is not set
CONFIG_3C359=m
# CONFIG_TMS380TR is not set
# CONFIG_WLAN is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_IPHETH is not set
CONFIG_NET_PCMCIA=y
# CONFIG_PCMCIA_3C589 is not set
# CONFIG_PCMCIA_3C574 is not set
# CONFIG_PCMCIA_FMVJ18X is not set
# CONFIG_PCMCIA_PCNET is not set
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
# CONFIG_PCMCIA_AXNET is not set
# CONFIG_PCMCIA_IBMTR is not set
# CONFIG_WAN is not set
#
# CAIF transport drivers
#
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
# CONFIG_SKFP is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
CONFIG_NETCONSOLE=m
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_VIRTIO_NET=m
# CONFIG_VMXNET3 is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=m
# CONFIG_INPUT_POLLDEV is not set
CONFIG_INPUT_SPARSEKMAP=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
CONFIG_XEN_KBDDEV_FRONTEND=m
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
CONFIG_INPUT_TABLET=y
# CONFIG_TABLET_USB_ACECAD is not set
# CONFIG_TABLET_USB_AIPTEK is not set
# CONFIG_TABLET_USB_GTCO is not set
# CONFIG_TABLET_USB_KBTAB is not set
# CONFIG_TABLET_USB_WACOM is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_WINBOND_CIR is not set
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_ADXL34X is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_N_GSM is not set
# CONFIG_NOZOMI is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CS=m
CONFIG_SERIAL_8250_NR_UARTS=16
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_RSA is not set
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MFD_HSU is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_HW_RANDOM_AMD is not set
CONFIG_HW_RANDOM_VIA=y
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_NVRAM=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_IPWIRELESS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_MMAP is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_RAMOOPS is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
# CONFIG_I2C_MUX is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_I801=y
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_SPI is not set
#
# PPS support
#
# CONFIG_PPS is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_PKGTEMP is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_SENSORS_APPLESMC is not set
#
# ACPI drivers
#
# CONFIG_SENSORS_ATK0110 is not set
# CONFIG_SENSORS_LIS3LV02D is not set
CONFIG_THERMAL=y
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_MFD_SUPPORT=y
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_TPS6507X is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_MFD_STMPE is not set
# CONFIG_MFD_TC35892 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_LPC_SCH is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
# CONFIG_VGA_SWITCHEROO is not set
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_TTM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_RADEON_KMS is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set
CONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_XEN_FBDEV_FRONTEND=m
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
# CONFIG_BACKLIGHT_PROGEAR is not set
# CONFIG_BACKLIGHT_MBP_NVIDIA is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=m
#
# Display hardware drivers
#
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=m
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_LOGO is not set
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
CONFIG_HIDRAW=y
#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
#
# Special HID drivers
#
# CONFIG_HID_3M_PCT is not set
CONFIG_HID_A4TECH=m
# CONFIG_HID_ACRUX_FF is not set
CONFIG_HID_APPLE=m
CONFIG_HID_BELKIN=m
# CONFIG_HID_CANDO is not set
CONFIG_HID_CHERRY=m
CONFIG_HID_CHICONY=m
CONFIG_HID_CYPRESS=m
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EGALAX is not set
CONFIG_HID_EZKEY=m
CONFIG_HID_KYE=m
CONFIG_HID_GYRATION=m
# CONFIG_HID_TWINHAN is not set
CONFIG_HID_KENSINGTON=m
CONFIG_HID_LOGITECH=m
CONFIG_LOGITECH_FF=y
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
CONFIG_HID_MICROSOFT=m
# CONFIG_HID_MOSART is not set
CONFIG_HID_MONTEREY=m
CONFIG_HID_NTRIG=m
# CONFIG_HID_ORTEK is not set
CONFIG_HID_PANTHERLORD=m
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PETALYNX=m
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_QUANTA is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_ROCCAT_KONE is not set
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
# CONFIG_HID_STANTUM is not set
CONFIG_HID_SUNPLUS=m
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
CONFIG_HID_TOPSEED=m
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEBUG=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_XHCI_HCD is not set
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
CONFIG_USB_LIBUSUAL=y
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_GADGET is not set
#
# OTG and related infrastructure
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
#
# LED drivers
#
# CONFIG_LEDS_ALIX2 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_CLEVO_MAIL is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_INTEL_SS4200 is not set
# CONFIG_LEDS_TRIGGERS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=y
# CONFIG_EDAC_MM_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not set
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
#
# SPI RTC drivers
#
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
# CONFIG_INTEL_MID_DMAC is not set
# CONFIG_INTEL_IOATDMA is not set
# CONFIG_TIMB_DMA is not set
# CONFIG_PCH_DMA is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
#
# Xen driver support
#
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_PLATFORM_PCI=m
CONFIG_SWIOTLB_XEN=y
CONFIG_STAGING=y
# CONFIG_STAGING_EXCLUDE_BUILD is not set
# CONFIG_ET131X is not set
# CONFIG_SLICOSS is not set
# CONFIG_USB_IP_COMMON is not set
# CONFIG_ECHO is not set
# CONFIG_COMEDI is not set
# CONFIG_ASUS_OLED is not set
# CONFIG_TRANZPORT is not set
# CONFIG_POHMELFS is not set
# CONFIG_IDE_PHISON is not set
# CONFIG_DRM_VMWGFX is not set
CONFIG_DRM_NOUVEAU=m
# CONFIG_DRM_NOUVEAU_BACKLIGHT is not set
CONFIG_DRM_NOUVEAU_DEBUG=y
#
# I2C encoder or helper chips
#
CONFIG_DRM_I2C_CH7006=m
CONFIG_DRM_I2C_SIL164=m
# CONFIG_FB_UDL is not set
# CONFIG_HYPERV is not set
# CONFIG_VME_BUS is not set
# CONFIG_IIO is not set
# CONFIG_ZRAM is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_SAMSUNG_LAPTOP is not set
# CONFIG_FB_SM7XX is not set
# CONFIG_CRYSTALHD is not set
#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# CONFIG_FB_XGI is not set
# CONFIG_ACPI_QUICKSTART is not set
CONFIG_X86_PLATFORM_DEVICES=y
# CONFIG_ACER_WMI is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_COMPAL_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_IDEAPAD_ACPI is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_INTEL_MENLOW is not set
CONFIG_EEEPC_LAPTOP=y
# CONFIG_ACPI_WMI is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_TOPSTAR_LAPTOP is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_ACPI_CMPC is not set
# CONFIG_INTEL_IPS is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_EFI_VARS=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_ISCSI_IBFT_FIND is not set
#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_EXT3_FS=m
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=m
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_FS_XIP=y
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=m
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=m
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
# CONFIG_XFS_QUOTA is not set
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_DEBUG is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_PRINT_QUOTA_WARNING is not set
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_QUOTACTL_COMPAT=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_LOGFS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_LOCKUP_DETECTOR is not set
# CONFIG_HARDLOCKUP_DETECTOR is not set
# CONFIG_DETECT_HUNG_TASK is not set
# CONFIG_SCHED_DEBUG is not set
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_LKDTM is not set
# CONFIG_CPU_NOTIFIER_ERROR_INJECT is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_FTRACE_SYSCALLS is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not set
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_KPROBE_EVENT=y
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
# CONFIG_DYNAMIC_DEBUG is not set
CONFIG_DMA_API_DEBUG=y
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_EARLY_PRINTK_DBGP=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
CONFIG_DEBUG_NX_TEST=m
CONFIG_IOMMU_DEBUG=y
# CONFIG_IOMMU_STRESS is not set
# CONFIG_IOMMU_LEAK is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
# CONFIG_X86_DECODER_SELFTEST is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
CONFIG_DEBUG_BOOT_PARAMS=y
# CONFIG_CPA_DEBUG is not set
CONFIG_OPTIMIZE_INLINING=y
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
# CONFIG_SECURITYFS is not set
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_NETWORK_XFRM is not set
# CONFIG_SECURITY_PATH is not set
# CONFIG_INTEL_TXT is not set
CONFIG_LSM_MMAP_MIN_ADDR=65534
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_IMA is not set
CONFIG_DEFAULT_SECURITY_SELINUX=y
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_DEFAULT_SECURITY="selinux"
CONFIG_XOR_BLOCKS=m
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
# CONFIG_ASYNC_RAID6_TEST is not set
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y
# CONFIG_CRYPTO_TEST is not set
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set
#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set
#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_AES_NI_INTEL is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
CONFIG_CRYPTO_ZLIB=y
# CONFIG_CRYPTO_LZO is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# CONFIG_CRYPTO_DEV_HIFN_795X is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
# CONFIG_VHOST_NET is not set
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=y
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
CONFIG_RAID6_PQ=m
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_FIND_LAST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_T10DIF=y
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CHECK_SIGNATURE=y
CONFIG_NLATTR=y
[-- Attachment #4: pv-start.xm --]
[-- Type: text/plain, Size: 326 bytes --]
kernel="/home/konrad/git/xtt/bootstrap/dist/common/vmlinuz"
ramdisk="/home/konrad/git/xtt/bootstrap/dist/common/initramfs.cpio.gz"
extra="inittab=/etc/inittab-xen console=hvc0 debug iommu=soft"
memory=1024
vcpus=4
vif = [ 'mac=00:0f:4b:00:00:68, bridge=switch' ]
pci= ["0000:03:00.0","00:1d.0","00:1d.1","00:1d.2","00:1d.7"]
[-- Attachment #5: hvm-start.xm --]
[-- Type: text/plain, Size: 377 bytes --]
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 2048
maxvcpus = 4
serial='pty'
vcpus = 2
disk = [ 'file:/home/konrad/git/xtt/bootstrap/dist/root_image.iso,hdc:cdrom,r']
boot="dn"
vif = [ 'type=ioemu,model=e1000,mac=00:0F:4B:00:00:68, bridge=switch' ]
vfb = [ 'vnc=1, vnclisten=0.0.0.0,vncunused=1']
pci= ["0000:03:00.0","00:1d.0","00:1d.1","00:1d.2","00:1d.7"]
[-- Attachment #6: lspci --]
[-- Type: text/plain, Size: 3600 bytes --]
00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port (rev 10)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 10)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 10)
00:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5 (rev 10)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 10)
00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 10)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 10)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 10)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 10)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 10)
00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 10)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
01:01.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
02:00.0 IDE interface: JMicron Technology Corp. JMB368 IDE controller
03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
04:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09)
04:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09)
0a:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
[-- Attachment #7: menu.lst --]
[-- Type: text/plain, Size: 3162 bytes --]
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_phenom-fc11_root
# initrd /initrd-version.img
#boot=/dev/sda
default=3
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
terminal --timeout=10 serial
title Fedora (2.6.32.23-stable-02166-g2335481)
root (hd0,0)
kernel /vmlinuz-2.6.32.23-stable-02166-g2335481 root=/dev/mapper/vg_phenom-fc11_root debug loglevel=10 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us xen-pciback.hide=(0a:00.1)(03:00.0)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) acpi.debug_layer=0x2 acpi.debug_level=0x1 console=tty console=hvc0 initcall_debug loglevel=10 debug selinux=0 radeon.modeset=0
initrd /initramfs-2.6.32.23-stable-02166-g2335481.img
title XenFedora (2.6.32.23-stable-02166-g2335481)
root (hd0,0)
kernel /xen2.gz guest_loglvl=all loglvl=all console=com1,vga com1=115200,8n1 console_to_ring cpuinfo apic=debug sync_console iommu=off x2apic=off
module /vmlinuz-2.6.32.23-stable-02166-g2335481 root=/dev/mapper/vg_phenom-fc11_root debug loglevel=10 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us xen-pciback.hide=(0a:00.1)(03:00.0)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) acpi.debug_layer=0x2 acpi.debug_level=0x1 console=tty console=hvc0 initcall_debug loglevel=10 debug selinux=0 radeon.modeset=0
module /initramfs-2.6.32.23-stable-02166-g2335481.img
title Fedora (2.6.32.18-stable-01767-gfe999249)
root (hd0,0)
kernel /vmlinuz-2.6.32.18-stable-01767-gfe999249 root=/dev/mapper/vg_phenom-fc11_root debug loglevel=10 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us xen-pciback.hide=(0a:00.1) acpi.debug_layer=0x2 acpi.debug_level=0x1 console=tty console=ttyS0,115200 initcall_debug loglevel=10 debug selinux=0 radeon.modeset=0
initrd /initramfs-2.6.32.18-stable-01767-gfe999249.img
title XenFedora (2.6.32.18-stable-01767-gfe999249)
root (hd0,0)
kernel /xen-4.1-unstable.gz guest_loglvl=all loglvl=all console=com1,vga com1=115200,8n1 console_to_ring cpuinfo apic=debu sync_console iommu=verbose
module /vmlinuz-2.6.32.18-stable-01767-gfe999249 root=/dev/mapper/vg_phenom-fc11_root debug loglevel=10 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us xen-pciback.hide=(0a:00.1)(03:00.0)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) acpi.debug_layer=0x2 acpi.debug_level=0x1 console=tty console=hvc0 initcall_debug loglevel=10 debug selinux=0 radeon.modeset=0
module /initramfs-2.6.32.18-stable-01767-gfe999249.img
title XenFedora (2.6.32.18-j8-01808-g84db183-dirty)
root (hd0,0)
kernel /xen2.gz guest_loglvl=all loglvl=all console=com1,vga com1=115200,8n1 console_to_ring cpuinfo apic=debug dom0_mem=4GB:max
module /vmlinuz-2.6.32.18-j8-01808-g84db183-dirty root=/dev/mapper/vg_phenom-fc11_root debug loglevel=10 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us xen-pciback.hide=(0a:00.1) acpi.debug_layer=0x2 acpi.debug_level=0x1 console=hvc0
module /initramfs-2.6.32.18-j8-01808-g84db183-dirty.img
[-- Attachment #8: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-11 21:46 ` Konrad Rzeszutek Wilk
@ 2010-10-13 21:36 ` Bruce Edge
2010-10-13 21:46 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-13 21:36 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Mon, Oct 11, 2010 at 2:46 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Mon, Oct 11, 2010 at 02:12:22PM -0700, Bruce Edge wrote:
>> On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> >> One of our developers who is working on a tachyon driver is
>> >> complaining that the pvops domU kernel is not working for these MSI
>> >> interrupts.
>> >> This is using the current head of xen/2.6.32.x on both a single
>> >> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> >> 4.0.1, 4.0.2.rc1-pre and 4.1.
>> >
>> >
>> > I just checked on my SuperMicro X8DTN, this combination
>> > - For Dom0, git commit fe999249 (2.6.32.18)
>> > - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
>> > - For Hypervisor I used cs 21976, but found that the latest (22155) works too
>> >
>> > with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
>> > a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>> >
>> > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
>> > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
>> > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
>> > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
>> > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
>> > 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>> >
>> > worked just fine (either defining pci=["..."] or just using pci-attach).
>> >
>> > But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
>> > that happy :-(
>> >
>> >
>>
>> Konrad,
>> To try eliminate the remaining differences here, could you post your
>> dom0/domU config files?
>
> Sure. See attached
Konrad,
That made a big difference. Looks much better now. It's been kicked
over to several developers who have each got our tachyon driver
working a little bit better.
Now the sticking point is an apparent limitation on the amount of
memory one can request using pci_map_single. It appears that we can
only ask for 256K or less. We need a 2MB DMA buffer.
Is there some alternate mechanism for getting a larger physically
contiguous buffer under pvops?
Thanks
-Bruce
>> I'd like to build the same kernels to get an apples->apples comparison.
>>
>> Also, could you include your grub info and domU cfg file?
>>
>> These may eliminate some of the remaining diffs in the configs and
>> show why your's works while mine does not.
>>
>> Thanks
>>
>> -Bruce
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-13 21:36 ` Bruce Edge
@ 2010-10-13 21:46 ` Konrad Rzeszutek Wilk
2010-10-13 22:00 ` Bruce Edge
0 siblings, 1 reply; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-10-13 21:46 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel
On Wed, Oct 13, 2010 at 02:36:47PM -0700, Bruce Edge wrote:
> On Mon, Oct 11, 2010 at 2:46 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Mon, Oct 11, 2010 at 02:12:22PM -0700, Bruce Edge wrote:
> >> On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
> >> <konrad.wilk@oracle.com> wrote:
> >> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> >> >> One of our developers who is working on a tachyon driver is
> >> >> complaining that the pvops domU kernel is not working for these MSI
> >> >> interrupts.
> >> >> This is using the current head of xen/2.6.32.x on both a single
> >> >> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> >> >> 4.0.1, 4.0.2.rc1-pre and 4.1.
> >> >
> >> >
> >> > I just checked on my SuperMicro X8DTN, this combination
> >> > - For Dom0, git commit fe999249 (2.6.32.18)
> >> > - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
> >> > - For Hypervisor I used cs 21976, but found that the latest (22155) works too
> >> >
> >> > with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
> >> > a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
> >> >
> >> > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
> >> > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
> >> > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
> >> > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
> >> > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
> >> > 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
> >> >
> >> > worked just fine (either defining pci=["..."] or just using pci-attach).
> >> >
> >> > But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
> >> > that happy :-(
> >> >
> >> >
> >>
> >> Konrad,
> >> To try eliminate the remaining differences here, could you post your
> >> dom0/domU config files?
> >
> > Sure. See attached
>
> Konrad,
> That made a big difference. Looks much better now. It's been kicked
> over to several developers who have each got our tachyon driver
> working a little bit better.
Hmm, I didn't really try to do anything fancy with the configs. Any
inklings of what config option might have caused all this headache?
>
> Now the sticking point is an apparent limitation on the amount of
> memory one can request using pci_map_single. It appears that we can
> only ask for 256K or less. We need a 2MB DMA buffer.
You can't use SG buffers? And chain them together and provide them
to the device? A lot of other drivers do this ...
> Is there some alternate mechanism for getting a larger physically
> contiguous buffer under pvops?
Why the contiguous requirement?
>
> Thanks
>
> -Bruce
>
> >> I'd like to build the same kernels to get an apples->apples comparison.
> >>
> >> Also, could you include your grub info and domU cfg file?
> >>
> >> These may eliminate some of the remaining diffs in the configs and
> >> show why your's works while mine does not.
> >>
> >> Thanks
> >>
> >> -Bruce
> >
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-13 21:46 ` Konrad Rzeszutek Wilk
@ 2010-10-13 22:00 ` Bruce Edge
2010-10-13 22:08 ` Bruce Edge
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-13 22:00 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Wed, Oct 13, 2010 at 2:46 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Wed, Oct 13, 2010 at 02:36:47PM -0700, Bruce Edge wrote:
>> On Mon, Oct 11, 2010 at 2:46 PM, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> > On Mon, Oct 11, 2010 at 02:12:22PM -0700, Bruce Edge wrote:
>> >> On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
>> >> <konrad.wilk@oracle.com> wrote:
>> >> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>> >> >> One of our developers who is working on a tachyon driver is
>> >> >> complaining that the pvops domU kernel is not working for these MSI
>> >> >> interrupts.
>> >> >> This is using the current head of xen/2.6.32.x on both a single
>> >> >> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>> >> >> 4.0.1, 4.0.2.rc1-pre and 4.1.
>> >> >
>> >> >
>> >> > I just checked on my SuperMicro X8DTN, this combination
>> >> > - For Dom0, git commit fe999249 (2.6.32.18)
>> >> > - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
>> >> > - For Hypervisor I used cs 21976, but found that the latest (22155) works too
>> >> >
>> >> > with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
>> >> > a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>> >> >
>> >> > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
>> >> > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
>> >> > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
>> >> > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
>> >> > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
>> >> > 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>> >> >
>> >> > worked just fine (either defining pci=["..."] or just using pci-attach).
>> >> >
>> >> > But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
>> >> > that happy :-(
>> >> >
>> >> >
>> >>
>> >> Konrad,
>> >> To try eliminate the remaining differences here, could you post your
>> >> dom0/domU config files?
>> >
>> > Sure. See attached
>>
>> Konrad,
>> That made a big difference. Looks much better now. It's been kicked
>> over to several developers who have each got our tachyon driver
>> working a little bit better.
>
> Hmm, I didn't really try to do anything fancy with the configs. Any
> inklings of what config option might have caused all this headache?
I had pruned out a lot of stuff I didn't need from the kernel. I may
have been a bit overzealous. Also, we were using the same kernel for
dom0 and domU. It may be that having all the dom0 baggage in the domU
has some unexpected consequences. Very vague I know, sorry. If I have
time I'll try narrow down the diffs that break it.
>
>>
>> Now the sticking point is an apparent limitation on the amount of
>> memory one can request using pci_map_single. It appears that we can
>> only ask for 256K or less. We need a 2MB DMA buffer.
>
> You can't use SG buffers? And chain them together and provide them
> to the device? A lot of other drivers do this ...
Perhaps. I don't know. I'm not the driver author. I think that it
worked using 1 giant buffer before so there was no need to use SG
buffers.
>
>> Is there some alternate mechanism for getting a larger physically
>> contiguous buffer under pvops?
>
> Why the contiguous requirement?
It may not be a hard requirement and was just a matter of
convenience. I'll kick that over the the tachyon guys and see what
they say. I think it's a non-trivial exercise to switch over. All the
internal buffer mgmt would have to change. If that's the only option,
well, that's it. ...is it?
Thanks again for your help. You've been instrumental it getting this up.
-Bruce
>>
>> Thanks
>>
>> -Bruce
>>
>> >> I'd like to build the same kernels to get an apples->apples comparison.
>> >>
>> >> Also, could you include your grub info and domU cfg file?
>> >>
>> >> These may eliminate some of the remaining diffs in the configs and
>> >> show why your's works while mine does not.
>> >>
>> >> Thanks
>> >>
>> >> -Bruce
>> >
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-13 22:00 ` Bruce Edge
@ 2010-10-13 22:08 ` Bruce Edge
2010-10-14 13:57 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 42+ messages in thread
From: Bruce Edge @ 2010-10-13 22:08 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: xen-devel
On Wed, Oct 13, 2010 at 3:00 PM, Bruce Edge <bruce.edge@gmail.com> wrote:
> On Wed, Oct 13, 2010 at 2:46 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
>> On Wed, Oct 13, 2010 at 02:36:47PM -0700, Bruce Edge wrote:
>>> On Mon, Oct 11, 2010 at 2:46 PM, Konrad Rzeszutek Wilk
>>> <konrad.wilk@oracle.com> wrote:
>>> > On Mon, Oct 11, 2010 at 02:12:22PM -0700, Bruce Edge wrote:
>>> >> On Fri, Oct 1, 2010 at 2:11 PM, Konrad Rzeszutek Wilk
>>> >> <konrad.wilk@oracle.com> wrote:
>>> >> > On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
>>> >> >> One of our developers who is working on a tachyon driver is
>>> >> >> complaining that the pvops domU kernel is not working for these MSI
>>> >> >> interrupts.
>>> >> >> This is using the current head of xen/2.6.32.x on both a single
>>> >> >> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
>>> >> >> 4.0.1, 4.0.2.rc1-pre and 4.1.
>>> >> >
>>> >> >
>>> >> > I just checked on my SuperMicro X8DTN, this combination
>>> >> > - For Dom0, git commit fe999249 (2.6.32.18)
>>> >> > - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
>>> >> > - For Hypervisor I used cs 21976, but found that the latest (22155) works too
>>> >> >
>>> >> > with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I tried
>>> >> > a combination of doing this with IOMMU (VT-d) and without - both cases these devices:
>>> >> >
>>> >> > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
>>> >> > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
>>> >> > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
>>> >> > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
>>> >> > 03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev 06)
>>> >> > 0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
>>> >> >
>>> >> > worked just fine (either defining pci=["..."] or just using pci-attach).
>>> >> >
>>> >> > But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
>>> >> > that happy :-(
>>> >> >
>>> >> >
>>> >>
>>> >> Konrad,
>>> >> To try eliminate the remaining differences here, could you post your
>>> >> dom0/domU config files?
>>> >
>>> > Sure. See attached
>>>
>>> Konrad,
>>> That made a big difference. Looks much better now. It's been kicked
>>> over to several developers who have each got our tachyon driver
>>> working a little bit better.
>>
>> Hmm, I didn't really try to do anything fancy with the configs. Any
>> inklings of what config option might have caused all this headache?
>
> I had pruned out a lot of stuff I didn't need from the kernel. I may
> have been a bit overzealous. Also, we were using the same kernel for
> dom0 and domU. It may be that having all the dom0 baggage in the domU
> has some unexpected consequences. Very vague I know, sorry. If I have
> time I'll try narrow down the diffs that break it.
>
>>
>>>
>>> Now the sticking point is an apparent limitation on the amount of
>>> memory one can request using pci_map_single. It appears that we can
>>> only ask for 256K or less. We need a 2MB DMA buffer.
>>
>> You can't use SG buffers? And chain them together and provide them
>> to the device? A lot of other drivers do this ...
>
> Perhaps. I don't know. I'm not the driver author. I think that it
> worked using 1 giant buffer before so there was no need to use SG
> buffers.
Got some more info. It's a hardware requirement for the tachyon chip.
It uses a 2 MB block for the FC SEST index table. It's one place where
we can't use SG.
It really not a matter of laziness.
-Bruce
>
>>
>>> Is there some alternate mechanism for getting a larger physically
>>> contiguous buffer under pvops?
>>
>> Why the contiguous requirement?
>
> It may not be a hard requirement and was just a matter of
> convenience. I'll kick that over the the tachyon guys and see what
> they say. I think it's a non-trivial exercise to switch over. All the
> internal buffer mgmt would have to change. If that's the only option,
> well, that's it. ...is it?
>
> Thanks again for your help. You've been instrumental it getting this up.
>
> -Bruce
>
>>>
>>> Thanks
>>>
>>> -Bruce
>>>
>>> >> I'd like to build the same kernels to get an apples->apples comparison.
>>> >>
>>> >> Also, could you include your grub info and domU cfg file?
>>> >>
>>> >> These may eliminate some of the remaining diffs in the configs and
>>> >> show why your's works while mine does not.
>>> >>
>>> >> Thanks
>>> >>
>>> >> -Bruce
>>> >
>>
>
^ permalink raw reply [flat|nested] 42+ messages in thread
* Re: pv-ops domU not working with MSI interrupts on Nehalem
2010-10-13 22:08 ` Bruce Edge
@ 2010-10-14 13:57 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 42+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-10-14 13:57 UTC (permalink / raw)
To: Bruce Edge; +Cc: xen-devel
> >> You can't use SG buffers? And chain them together and provide them
> >> to the device? A lot of other drivers do this ...
> >
> > Perhaps. I don't know. I'm not the driver author. I think that it
> > worked using 1 giant buffer before so there was no need to use SG
> > buffers.
>
> Got some more info. It's a hardware requirement for the tachyon chip.
> It uses a 2 MB block for the FC SEST index table. It's one place where
> we can't use SG.
OK, pci_alloc_consistent is the way. I think you can go up to 2MB with it.
> It really not a matter of laziness.
<nods>
^ permalink raw reply [flat|nested] 42+ messages in thread
end of thread, other threads:[~2010-10-14 13:57 UTC | newest]
Thread overview: 42+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-09-27 15:52 pv-ops domU not working with MSI interrupts on Nehalem Bruce Edge
2010-09-27 17:24 ` Konrad Rzeszutek Wilk
2010-09-27 19:16 ` Bruce Edge
2010-09-27 19:54 ` Konrad Rzeszutek Wilk
2010-09-27 23:54 ` Bruce Edge
2010-09-28 1:15 ` Jiang, Yunhong
2010-09-28 3:16 ` Bruce Edge
2010-09-28 3:26 ` Jiang, Yunhong
2010-09-28 4:45 ` Bruce Edge
2010-09-28 16:08 ` Lin, Ray
2010-09-28 16:19 ` Konrad Rzeszutek Wilk
2010-09-28 18:35 ` Lin, Ray
2010-09-28 20:14 ` Konrad Rzeszutek Wilk
2010-09-28 20:38 ` Lin, Ray
2010-09-29 0:53 ` Jiang, Yunhong
2010-09-30 16:30 ` Lin, Ray
2010-09-28 14:56 ` Konrad Rzeszutek Wilk
2010-09-30 18:55 ` Bruce Edge
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19 ` Bruce Edge
2010-10-01 23:30 ` Bruce Edge
2010-10-03 5:46 ` Bruce Edge
2010-10-03 12:08 ` Pasi Kärkkäinen
2010-10-04 14:48 ` Konrad Rzeszutek Wilk
2010-10-05 18:21 ` Bruce Edge
2010-10-06 14:21 ` Konrad Rzeszutek Wilk
2010-10-06 18:21 ` Bruce Edge
2010-10-08 16:48 ` Lin, Ray
2010-10-08 17:30 ` Konrad Rzeszutek Wilk
2010-10-08 17:40 ` Lin, Ray
2010-10-08 17:52 ` Bruce Edge
2010-10-08 21:01 ` Lin, Ray
2010-10-08 17:56 ` Bruce Edge
2010-10-11 21:12 ` Bruce Edge
2010-10-11 21:46 ` Konrad Rzeszutek Wilk
2010-10-13 21:36 ` Bruce Edge
2010-10-13 21:46 ` Konrad Rzeszutek Wilk
2010-10-13 22:00 ` Bruce Edge
2010-10-13 22:08 ` Bruce Edge
2010-10-14 13:57 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2010-09-28 23:25 Lin, Ray
2010-09-28 23:57 ` Konrad Rzeszutek Wilk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).