lkml.org 
[lkml]   [2019]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [Xen-devel] [PATCH v2 1/2] x86: respect memory size limiting via mem= parameter
From
Date
On 11/02/2019 13:23, Ingo Molnar wrote:
>
> * Juergen Gross <jgross@suse.com> wrote:
>
>>> If PCI devices had physical mmio memory areas above this range, we'd
>>> still expect them to work - the option was really only meant to limit
>>> RAM.
>>
>> No, in this case it seems to be real RAM added via PCI. The RAM is
>> initially present in the E820 map, but the "mem=" will remove it from
>> there again. During ACPI scan it is found (again) and will be added via
>> hotplug mechanism, so "mem=" has no effect for that memory.
>
> OK. With that background:
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
>
> I suppose you want this to go upstream via the Xen tree, which is the
> main testcase for the bug to begin with?

Yes, I'd prefer that.


Juergen

\
 
 \ /
  Last update: 2019-02-11 13:36    [W:0.034 / U:1.008 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site