>>> On 13.05.15 at 14:12, wrote:
> On Wed, 13 May 2015 11:01:24 +0100
> "Jan Beulich" wrote:
>> Okay, if the tools do this in v2, then I think the compatibility v1
>> path should indeed do so too (in the hypervisor).
>
> Are you working on a patch?
Not yet, but I'm going to as soon as I can fin
On Wed, 13 May 2015 11:01:24 +0100
"Jan Beulich" wrote:
> >>> On 13.05.15 at 11:53, wrote:
> > On 13/05/15 09:12, Jan Beulich wrote:
> > On 13.05.15 at 09:35, wrote:
> >>> Fundamentally if you are transfering control in long mode you have to
> >>> set up some page table. I giant identity m
>>> On 13.05.15 at 11:53, wrote:
> On 13/05/15 09:12, Jan Beulich wrote:
> On 13.05.15 at 09:35, wrote:
>>> Fundamentally if you are transfering control in long mode you have to
>>> set up some page table. I giant identity mapped page table that can use
>>> 1G or 2M pages takes up very littl
On 13/05/15 09:12, Jan Beulich wrote:
On 13.05.15 at 09:35, wrote:
>> Fundamentally if you are transfering control in long mode you have to
>> set up some page table. I giant identity mapped page table that can use
>> 1G or 2M pages takes up very little memory, and can be very simply
>> and
On Wed, 13 May 2015 09:12:47 +0100
"Jan Beulich" wrote:
> >>> On 13.05.15 at 09:35, wrote:
> > Fundamentally if you are transfering control in long mode you have to
> > set up some page table. I giant identity mapped page table that can use
> > 1G or 2M pages takes up very little memory, and ca
>>> On 13.05.15 at 09:35, wrote:
> Fundamentally if you are transfering control in long mode you have to
> set up some page table. I giant identity mapped page table that can use
> 1G or 2M pages takes up very little memory, and can be very simply
> and easily before the transfer of control takes
"Jan Beulich" writes:
On 13.05.15 at 07:26, wrote:
>> The low 640k was weird. We copied it off in purgatory so that it could
>> be capture in a dump. The linux kernel itself winds up using that
>> memory fundamentally because to fire up subsequent processors you have
>> to have memory in
>>> On 13.05.15 at 07:26, wrote:
> The low 640k was weird. We copied it off in purgatory so that it could
> be capture in a dump. The linux kernel itself winds up using that
> memory fundamentally because to fire up subsequent processors you have
> to have memory in the low 640k as processors s
Petr Tesarik writes:
> Hi all,
>
> note that I'm not subscribed to the xen-devel mailing list, but Jan
> quoted from this mail of Andrew's in SUSE Bugzilla:
>
>> This is all from a while ago. It is quite possible that we didn't
>> actually tested the compatibility case with a 64bit dom0 kernel,
