On Tue, 2015-11-17 at 03:19 -0700, Jan Beulich wrote:
> > > > On 16.11.15 at 17:52, wrote:
> > On Thu, 2015-11-12 at 08:52 -0700, Jan Beulich wrote:
> > > There's no point in mapping more than the memory we actually may need
> > > to touch, and in fact the too large region could actually extend in
>>> On 16.11.15 at 17:52, wrote:
> On Thu, 2015-11-12 at 08:52 -0700, Jan Beulich wrote:
>> There's no point in mapping more than the memory we actually may need
>> to touch, and in fact the too large region could actually extend into
>> another device's one (which currently is benign on x86 since
On Thu, 2015-11-12 at 08:52 -0700, Jan Beulich wrote:
> There's no point in mapping more than the memory we actually may need
> to touch, and in fact the too large region could actually extend into
> another device's one (which currently is benign on x86 since only a
> single page gets mapped anywa
On 12/11/15 15:52, Jan Beulich wrote:
> There's no point in mapping more than the memory we actually may need
> to touch, and in fact the too large region could actually extend into
> another device's one (which currently is benign on x86 since only a
> single page gets mapped anyway, but which is
There's no point in mapping more than the memory we actually may need
to touch, and in fact the too large region could actually extend into
another device's one (which currently is benign on x86 since only a
single page gets mapped anyway, but which is a latent bug on ARM
whenever PCI support gets
