Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-04 Thread Eric Shelton
On Wed, Dec 2, 2015 at 10:41 AM, Jan Beulich wrote: > >>> On 02.12.15 at 16:37, wrote: > > On Dec 2, 2015, at 10:28 AM, Jan Beulich wrote: > > > > On 02.12.15 at 16:04, wrote: > >>> I have attached the output

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Eric Shelton
On Dec 2, 2015, at 10:28 AM, Jan Beulich wrote: On 02.12.15 at 16:04, wrote: >> I have attached the output from 'xl dmesg' with iommu=debug >> apic_verbosity=debug loglvl=all > > As of 4.6.0 it actually takes a debug hypervisor to get those >

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Jan Beulich
>>> On 02.12.15 at 16:37, wrote: > On Dec 2, 2015, at 10:28 AM, Jan Beulich wrote: > > On 02.12.15 at 16:04, wrote: >>> I have attached the output from 'xl dmesg' with iommu=debug >>> apic_verbosity=debug loglvl=all >> >> As of

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Eric Shelton
I have attached the output from 'xl dmesg' with iommu=debug apic_verbosity=debug loglvl=all This is with 4.6.0, with the recent patch enabling mwait-idle on Skylake applied. My initial post was running the latest out of xen.git master. I may be able to try to newer code again later this week.

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Jan Beulich
>>> On 02.12.15 at 16:04, wrote: > I have attached the output from 'xl dmesg' with iommu=debug > apic_verbosity=debug loglvl=all As of 4.6.0 it actually takes a debug hypervisor to get those messages logged (which arguably is wrong, and which quite certainly is wrong for

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Shuai Ruan
On Sat, Nov 28, 2015 at 03:46:05PM -0500, Eric Shelton wrote: hi eric: I test this on my skylake machine. Result is follow > Not enabling x2APIC (upon firmware request) I got the message too. > ... > mwait-idle: does not run on family 6 model 94 I got the message too. > ... > [VT-D] iommu.c:875:

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Shuai Ruan
On Wed, Dec 02, 2015 at 04:47:17PM +0800, Shuai Ruan wrote: > On Sat, Nov 28, 2015 at 03:46:05PM -0500, Eric Shelton wrote: > > hi eric: > > I test this on my skylake machine. Result is follow > > Not enabling x2APIC (upon firmware request) > I got the message too. According to Andrew's

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Andrew Cooper
On 02/12/15 02:51, Eric Shelton wrote: > ASRock Z170 Extreme 4 with BIOS version 2.30 was motherboard #1 > Gigabyte GA-Z170XP-SLI with BIOS version F5 was motherboard #2 > > As I initially reported, both were reporting the error involving f0:1f.0 > > Not surprisingly, there are no f0:xx.y devices.

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-02 Thread Jan Beulich
>>> On 02.12.15 at 03:51, wrote: > ASRock Z170 Extreme 4 with BIOS version 2.30 was motherboard #1 > Gigabyte GA-Z170XP-SLI with BIOS version F5 was motherboard #2 > > As I initially reported, both were reporting the error involving f0:1f.0 > > Not surprisingly, there are no

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-01 Thread Eric Shelton
ASRock Z170 Extreme 4 with BIOS version 2.30 was motherboard #1 Gigabyte GA-Z170XP-SLI with BIOS version F5 was motherboard #2 As I initially reported, both were reporting the error involving f0:1f.0 Not surprisingly, there are no f0:xx.y devices. The closest I suppose is: 00:1f.0 ISA Bridge:

Re: [Xen-devel] Skylake: VT-d and other error messages

2015-12-01 Thread Tian, Kevin
Eric, could you provide your motherboard information and as Andrew pointed out what’s f0:1f.0? From: Andrew Cooper [mailto:andrew.coop...@citrix.com] Sent: Sunday, November 29, 2015 6:15 AM To: Eric Shelton; xen-devel; Zhang, Yang Z; Tian, Kevin; Keir Fraser; Jan Beulich Subject: Re: Skylake:

[Xen-devel] Skylake: VT-d and other error messages

2015-11-28 Thread Eric Shelton
Looking through the output of 'xl dmesg' on a Skylake system (i5-6600K), I found a number of error messages that I do not encounter on a Haswell-based system. I have tried two motherboards from different manufacturers, with pretty much the same results. Below are some of the unexpected messages: