Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-20 Thread Konrad Rzeszutek Wilk
On Thu, Feb 19, 2015 at 09:13:52AM +, Jan Beulich wrote: > >>> On 18.02.15 at 19:15, wrote: > > On Tue, Feb 17, 2015 at 02:14:20PM +, Andrew Cooper wrote: > >> On 17/02/15 13:39, Jan Beulich wrote: > >> On 17.02.15 at 14:32, wrote: > >> >> On 17/02/15 12:36, Jan Beulich wrote: > >> >

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-19 Thread Jan Beulich
>>> On 18.02.15 at 19:15, wrote: > On Tue, Feb 17, 2015 at 02:14:20PM +, Andrew Cooper wrote: >> On 17/02/15 13:39, Jan Beulich wrote: >> On 17.02.15 at 14:32, wrote: >> >> On 17/02/15 12:36, Jan Beulich wrote: >> >> On 14.02.15 at 00:21, wrote: >> On Fri, Feb 13, 2015 at 10:09

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-18 Thread Konrad Rzeszutek Wilk
On Tue, Feb 17, 2015 at 02:14:20PM +, Andrew Cooper wrote: > On 17/02/15 13:39, Jan Beulich wrote: > On 17.02.15 at 14:32, wrote: > >> On 17/02/15 12:36, Jan Beulich wrote: > >> On 14.02.15 at 00:21, wrote: > On Fri, Feb 13, 2015 at 10:09:39PM +, Andrew Cooper wrote: > >

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-17 Thread Andrew Cooper
On 17/02/15 13:39, Jan Beulich wrote: On 17.02.15 at 14:32, wrote: >> On 17/02/15 12:36, Jan Beulich wrote: >> On 14.02.15 at 00:21, wrote: On Fri, Feb 13, 2015 at 10:09:39PM +, Andrew Cooper wrote: > If I understand the problem correctly, I believe that the correct > so

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-17 Thread Jan Beulich
>>> On 17.02.15 at 14:32, wrote: > On 17/02/15 12:36, Jan Beulich wrote: > On 14.02.15 at 00:21, wrote: >>> On Fri, Feb 13, 2015 at 10:09:39PM +, Andrew Cooper wrote: If I understand the problem correctly, I believe that the correct solution would be to add a dmar_rmrr[ command

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-17 Thread Andrew Cooper
On 17/02/15 12:36, Jan Beulich wrote: On 14.02.15 at 00:21, wrote: >> On Fri, Feb 13, 2015 at 10:09:39PM +, Andrew Cooper wrote: >>> If I understand the problem correctly, I believe that the correct >>> solution would be to add a dmar_rmrr[ command line parameter along the >>> same lines

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-17 Thread Jan Beulich
>>> On 14.02.15 at 00:21, wrote: > On Fri, Feb 13, 2015 at 10:09:39PM +, Andrew Cooper wrote: >> If I understand the problem correctly, I believe that the correct >> solution would be to add a dmar_rmrr[ command line parameter along the >> same lines as ivrs_hpet[ and ivrs_ioapic[ which allows

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-13 Thread Elena Ufimtseva
On Fri, Feb 13, 2015 at 10:09:39PM +, Andrew Cooper wrote: > On 13/02/15 18:52, Elena Ufimtseva wrote: > > It appears from the experiments that some devices on few systems > > may attempt to access memory ranges that are not RMRRs regions (and > > are not reported by ACPI) and are reserved in t

Re: [Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-13 Thread Andrew Cooper
On 13/02/15 18:52, Elena Ufimtseva wrote: > It appears from the experiments that some devices on few systems > may attempt to access memory ranges that are not RMRRs regions (and > are not reported by ACPI) and are reserved in the host e820 map. > These memory addresses appear to be the targets for

[Xen-devel] [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges

2015-02-13 Thread Elena Ufimtseva
It appears from the experiments that some devices on few systems may attempt to access memory ranges that are not RMRRs regions (and are not reported by ACPI) and are reserved in the host e820 map. These memory addresses appear to be the targets for DMA reads by devices. Presumably, these devices m