Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Andrew Cooper
On 15/01/2019 11:50, Jan Beulich wrote: > >>> And even >>> if I re-phrased your reply to mean an arbitrary alignment / order >>> less than 9, then populating this with such a smaller order is still >>> fine, and requesting the IOMMU mapping with that smaller order >>> is still not going to trip the

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Jan Beulich
>>> On 15.01.19 at 12:07, wrote: > On Tue, Jan 15, 2019 at 03:49:07AM -0700, Jan Beulich wrote: >> >>> On 15.01.19 at 11:27, wrote: >> > On Tue, Jan 15, 2019 at 03:16:01AM -0700, Jan Beulich wrote: >> >> >>> On 15.01.19 at 10:44, wrote: >> >> >> -Original Message- >> >> > [snip] >> >> >

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Jan Beulich
>>> On 15.01.19 at 11:55, wrote: > I guess the question is whether we want to allow arbitrary alignment of the > memory passed into iommu_map() or not. If we do then I think a count > parameter makes more sense. Agreed. Till now I simply don't see the use case. Jan _

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Roger Pau Monné
On Tue, Jan 15, 2019 at 03:49:07AM -0700, Jan Beulich wrote: > >>> On 15.01.19 at 11:27, wrote: > > On Tue, Jan 15, 2019 at 03:16:01AM -0700, Jan Beulich wrote: > >> >>> On 15.01.19 at 10:44, wrote: > >> >> -Original Message- > >> > [snip] > >> >> >> (XEN) Xen call trace: > >> >> >> (XEN

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Paul Durrant
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 15 January 2019 10:53 > To: Andrew Cooper > Cc: Paul Durrant ; Roger Pau Monne > ; Chao Gao ; xen-devel de...@lists.xenproject.org> > Subject: Re: [Xen-devel] an assertion triggered w

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Jan Beulich
>>> On 15.01.19 at 11:42, wrote: > On 15/01/2019 10:27, Roger Pau Monné wrote: >> On Tue, Jan 15, 2019 at 03:16:01AM -0700, Jan Beulich wrote: >> On 15.01.19 at 10:44, wrote: > -Original Message- [snip] >>> (XEN) Xen call trace: >>> (XEN)[] iommu_map+0xba/0x176 >

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Jan Beulich
>>> On 15.01.19 at 11:27, wrote: > On Tue, Jan 15, 2019 at 03:16:01AM -0700, Jan Beulich wrote: >> >>> On 15.01.19 at 10:44, wrote: >> >> -Original Message- >> > [snip] >> >> >> (XEN) Xen call trace: >> >> >> (XEN)[] iommu_map+0xba/0x176 >> >> >> (XEN)[] iommu_hwdom_init+0xef/0x2

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Andrew Cooper
On 15/01/2019 10:27, Roger Pau Monné wrote: > On Tue, Jan 15, 2019 at 03:16:01AM -0700, Jan Beulich wrote: > On 15.01.19 at 10:44, wrote: -Original Message- >>> [snip] >> (XEN) Xen call trace: >> (XEN)[] iommu_map+0xba/0x176 >> (XEN)[] iommu_hwdom_init+0xef/0x

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Roger Pau Monné
On Tue, Jan 15, 2019 at 03:16:01AM -0700, Jan Beulich wrote: > >>> On 15.01.19 at 10:44, wrote: > >> -Original Message- > > [snip] > >> >> (XEN) Xen call trace: > >> >> (XEN)[] iommu_map+0xba/0x176 > >> >> (XEN)[] iommu_hwdom_init+0xef/0x220 > >> >> (XEN)[] dom0_construct_pvh+

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Jan Beulich
>>> On 15.01.19 at 10:44, wrote: >> -Original Message- > [snip] >> >> (XEN) Xen call trace: >> >> (XEN)[] iommu_map+0xba/0x176 >> >> (XEN)[] iommu_hwdom_init+0xef/0x220 >> >> (XEN)[] dom0_construct_pvh+0x189/0x129e >> >> (XEN)[] construct_dom0+0xd4/0xb14 >> >> (XEN)[]

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Paul Durrant
> -Original Message- [snip] > >> (XEN) Xen call trace: > >> (XEN)[] iommu_map+0xba/0x176 > >> (XEN)[] iommu_hwdom_init+0xef/0x220 > >> (XEN)[] dom0_construct_pvh+0x189/0x129e > >> (XEN)[] construct_dom0+0xd4/0xb14 > >> (XEN)[] __start_xen+0x2710/0x2830 > >> (XEN)[] _

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Paul Durrant
> -Original Message- > From: Roger Pau Monne > Sent: 15 January 2019 08:18 > To: Chao Gao > Cc: xen-devel@lists.xenproject.org; Paul Durrant > Subject: Re: [Xen-devel] an assertion triggered when running Xen on a HSW > desktop > > On Tue, Jan 15, 2019 at 04:04

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Chao Gao
On Tue, Jan 15, 2019 at 09:18:25AM +0100, Roger Pau Monné wrote: >On Tue, Jan 15, 2019 at 04:04:40PM +0800, Chao Gao wrote: >[...] >> (XEN) Xen version 4.12-unstable (root@) (gcc (Ubuntu 7.3.0-27ubuntu1~18.04) >> 7.3.0) debug=y Tue Jan 15 07:25:29 UTC 2019 >> (XEN) Latest ChangeSet: Mon Dec 17 09

Re: [Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Roger Pau Monné
On Tue, Jan 15, 2019 at 04:04:40PM +0800, Chao Gao wrote: [...] > (XEN) Xen version 4.12-unstable (root@) (gcc (Ubuntu 7.3.0-27ubuntu1~18.04) > 7.3.0) debug=y Tue Jan 15 07:25:29 UTC 2019 > (XEN) Latest ChangeSet: Mon Dec 17 09:22:59 2018 + git:a5b0eb3636 [...] > (XEN) *** Building a PVH Dom0

[Xen-devel] an assertion triggered when running Xen on a HSW desktop

2019-01-15 Thread Chao Gao
The output of lscpu is: Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):8 On-line CPU(s) list: 0-7 Thread(s) per core:2 Core(s) per socket:4 Socket(s): 1 NUMA node(s): 1 Vendor ID: