>>> On 31.08.16 at 14:32, wrote:
> On 31/08/16 13:28, Jan Beulich wrote:
> On 30.08.16 at 18:35, wrote:
>>> On 19/08/16 13:57, Jan Beulich wrote:
>>> On 19.08.16 at 14:39, wrote:
> On 19/08/16 08:52,
On 31/08/16 13:28, Jan Beulich wrote:
On 30.08.16 at 18:35, wrote:
>> On 19/08/16 13:57, Jan Beulich wrote:
>> On 19.08.16 at 14:39, wrote:
On 19/08/16 08:52, Jan Beulich wrote:
> Page tables get pre-populated with physical
>>> On 30.08.16 at 18:35, wrote:
> On 19/08/16 13:57, Jan Beulich wrote:
> On 19.08.16 at 14:39, wrote:
>>> On 19/08/16 08:52, Jan Beulich wrote:
Page tables get pre-populated with physical addresses which, due to
living inside
On 19/08/16 13:57, Jan Beulich wrote:
On 19.08.16 at 14:39, wrote:
>> On 19/08/16 08:52, Jan Beulich wrote:
>>> Page tables get pre-populated with physical addresses which, due to
>>> living inside the Xen image, will never exceed 32 bits in width. That
>>> in turn
>>> On 19.08.16 at 14:39, wrote:
> On 19/08/16 08:52, Jan Beulich wrote:
>> Page tables get pre-populated with physical addresses which, due to
>> living inside the Xen image, will never exceed 32 bits in width. That
>> in turn results in the tool generating the
On 19/08/16 08:52, Jan Beulich wrote:
> Page tables get pre-populated with physical addresses which, due to
> living inside the Xen image, will never exceed 32 bits in width. That
> in turn results in the tool generating the relocations to produce
> 32-bit relocations for them instead of the
Page tables get pre-populated with physical addresses which, due to
living inside the Xen image, will never exceed 32 bits in width. That
in turn results in the tool generating the relocations to produce
32-bit relocations for them instead of the 64-bit ones needed for
relocating virtual