On 24/08/15 12:47, Jan Beulich wrote:
On 24.08.15 at 12:36, wrote:
>> The infrastructure around xenheap_max_mfn() is supposed cause all
>> xenheap page allocations to fall within the Xen direct mapped region,
>> but experimentally doesn't work correctly.
>>
>> In all cases I have seen, the ba
>>> On 24.08.15 at 12:36, wrote:
> The infrastructure around xenheap_max_mfn() is supposed cause all
> xenheap page allocations to fall within the Xen direct mapped region,
> but experimentally doesn't work correctly.
>
> In all cases I have seen, the bad xenheap allocations have been from
> call
(Following up from a discussion at the Seattle Summit).
While the theoretical Xen x86 host memory limit is 16TB (or 123TB with
CONFIG_BIGMEM), Xen doesn't actually function correctly if host ram
exceeds the addressable range in the directmap region, which is at the
5TB boundary (or 3.5TB with CONF
