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
>>> 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]
>> >> >
>>> 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
_
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
> -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
>>> 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
>
>>> 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
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
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+
>>> 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)[]
> -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)[] _
> -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
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
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
14 matches
Mail list logo