|
Am 08.11.2010 schrieb ""Kay, Allen M" <allen.m.kay@xxxxxxxxx>":
> > # lspci -n -s 10:00.0
> > 10:00.0 0280: 8086:422c (rev 35)
> > And the id 8086:422c is not in your switch statement and therewith
> > map_me_phantom_function() is not called.
>
> Have you tried to add "case 0x422c8086" to code to see if it solve the problem for you?
Yes I tried this but it didn't help.
I have to admit that I took only the me_wifi_quirk() part of your patch and
hacked this in our SLES11 SP1 hypervisor source.
After looking a little bit deeper into the sources I have some questions.
I have 3 drhd units. After tracing in acpi_parse_one_drhd() I saw that the
segment item in the acpi_table_drhd is always 0. When my phantom device
should be mapped (0.22.7) it uses the iommu with the INCLUDE_ALL flag set.
But this drhd addresses the segment 0 too.
The Intel VTd-spec writes in chapter 8.3. "DMA Remapping Hardware Unit
Definition Structure" that the "Segment Number" is the PCI Segment associated
with this unit.
So what is a PCI Segment here?
But my WLAN card is on bus 10. Is then the bus 10 belonging to the segment 0
too or is the bus number wrong.
Or is there no drhd - unit for the bus 10 because the BIOS didn't set up this
table right?
Thanks.
Dietmar.
(XEN) [VT-D]dmar.c:700: Host address width 36
(XEN) [VT-D]dmar.c:715: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:407: dmaru->address = fed90000
(XEN) [VT-D]iommu.c:1219: drhd->address = fed90000 iommu->reg = ffff82c3fff57000
(XEN) [VT-D]iommu.c:1221: cap = c9008020e30272 ecap = 1000
(XEN) [VT-D]dmar.c:342: endpoint: 0:1b.0
(XEN) [VT-D]dmar.c:715: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:407: dmaru->address = fed91000
(XEN) [VT-D]iommu.c:1219: drhd->address = fed91000 iommu->reg = ffff82c3fff56000
(XEN) [VT-D]iommu.c:1221: cap = c0000020230272 ecap = 1000
(XEN) [VT-D]dmar.c:342: endpoint: 0:2.0
(XEN) [VT-D]dmar.c:715: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:407: dmaru->address = fed93000
(XEN) [VT-D]iommu.c:1219: drhd->address = fed93000 iommu->reg = ffff82c3fff55000
(XEN) [VT-D]iommu.c:1221: cap = c9008020630272 ecap = 1000
(XEN) [VT-D]dmar.c:425: flags: INCLUDE_ALL
(XEN) [VT-D]dmar.c:720: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:342: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:342: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:592: RMRR region: base_addr bb6e9000 end_address bb6fffff
(XEN) [VT-D]dmar.c:720: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:342: endpoint: 0:2.0
(XEN) [VT-D]dmar.c:592: RMRR region: base_addr bde00000 end_address bfffffff
>
> By the way, I do not have access to this Fujitsu machine so I would need to rely on you to see if adding the wifi ID would work.
>
> Allen
>
> ------
>
> From: Dietmar Hahn [mailto:dietmar.hahn@xxxxxxxxxxxxxx]
> Sent: Monday, November 08, 2010 6:18 AM
> To: Kay, Allen M
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Problem: WIndows domu switches power off
>
> Hi Allen,
> Am 05.11.2010 schrieb ""Kay, Allen M" <allen.m.kay@xxxxxxxxx>":
> > Dietmar,
> >
> > This is a known issue with WLAN passthrough cause by ME (management engine) interaction. The latest xen-unstable has quirk to workaround issue.
> Are you think of this quirk:
> http://xenbits.xensource.com/staging/xen-unstable.hg?rev/b48d8f27fca2
> > Can you give it a try and let me know if it fixes the problem for you?
> I looked at the sources and found your me_wifi_quirk() stuff.
> But if I understand the code right, the patch doesn't help.
> # lspci -n -s 00:00.0
> 00:00.0 0600: 8086:0044 (rev 02)
> So IS_ILK(id) should be true.
> But my WLAN adapter is:
> 10:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
> # lspci -n -s 10:00.0
> 10:00.0 0280: 8086:422c (rev 35)
> And the id 8086:422c is not in your switch statement and therewith
> map_me_phantom_function() is not called.
> By the way I don't see a pci device 0:22.7
> > By the way, which brand of Core i5 laptop do you have. I would like to see if I have one locally.
> It's a Fujitsu Lifebook S760
> Following the intel spec I checked the device id of the D31:F0 device function:
> 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
> # lspci -n -s 00:1f.0
> 00:1f.0 0601: 8086:3b07 (rev 05)
> And this is the Intel(r) QM57 Chipset.
> Thanks.
> Dietmar.
> For your information:
> # lspci
> 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
> 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
> 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
> 00:16.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset PT IDER Controller (rev 06)
> 00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT Controller (rev 06)
> 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)
> 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
> 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
> 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05)
> 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
> 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
> 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
> 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05)
> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
> 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
> 10:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
> ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
> ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
> ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
> ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
> ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
> ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
> >
> > Allen
> >
> > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dietmar Hahn
> > Sent: Tuesday, October 26, 2010 12:24 AM
> > To: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-devel] Problem: WIndows domu switches power off
> >
> >
> > Hi list,
> >
> > I have a special effect on a Laptop with:
> >
> > cpu: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz with integrated graphics
> >
> > Chipsatz: Intel QM57
> >
> > with SLES11 SP1 (xen-4.0 with some patches from Novell)
> >
> > I passed through the sound and WLAN pci controller to the gues
> >
> > I start a Windows 7 guest and while installing the driver for the WLAN
> >
> > controller within Windows the power of the notebook got switched off.
> >
> > I couldnt see any message on the serial console.
> >
> > I tried Windows on bare metall and all runs very well. Later on starting this
> >
> > Windows guest again the power got switched of after login into Windows - maybe
> >
> > the WLAN driver got started there.
> >
> > For a test I prepared a OpenSuSE 11.3 as HVM guest and were able to configure
> >
> > the WLAN device without any problems.
> >
> > And here I need some assistance to prevent the power off and to add some tracer
> >
> > in the hypervisor.
> >
> > By the way I have no problems with the sound device.
> >
> > If wanted I can add more informations.
> >
> > Thanks.
> >
> > Dietmar.
>
--
Company details: http://ts.fujitsu.com/imprint.html | 
