On 24/07/15 11:34, David Vrabel wrote:
> On 24/07/15 10:51, Julien Grall wrote:
>> On 24/07/15 10:48, David Vrabel wrote:
>>> On 24/07/15 10:39, Julien Grall wrote:
Hi David,
On 24/07/15 10:28, David Vrabel wrote:
> On 09/07/15 21:42, Julien Grall wrote:
>> The Xen hypercall
On Fri, 2015-07-24 at 11:34 +0100, David Vrabel wrote:
> it would be better to think that:
>
> PFNs index guest-sized pages (which may be 64 KiB).
>
> GFNs index Xen-sized pages (which is always 4 KiB).
This concept could be usefully added to the comment in
xen/include/xen/mm.h IMHO.
>
>
On 24/07/15 10:51, Julien Grall wrote:
> On 24/07/15 10:48, David Vrabel wrote:
>> On 24/07/15 10:39, Julien Grall wrote:
>>> Hi David,
>>>
>>> On 24/07/15 10:28, David Vrabel wrote:
On 09/07/15 21:42, Julien Grall wrote:
> The Xen hypercall interface is always using 4K page granularity
On 24/07/15 10:48, David Vrabel wrote:
> On 24/07/15 10:39, Julien Grall wrote:
>> Hi David,
>>
>> On 24/07/15 10:28, David Vrabel wrote:
>>> On 09/07/15 21:42, Julien Grall wrote:
The Xen hypercall interface is always using 4K page granularity on ARM
and x86 architecture.
With
On 24/07/15 10:39, Julien Grall wrote:
> Hi David,
>
> On 24/07/15 10:28, David Vrabel wrote:
>> On 09/07/15 21:42, Julien Grall wrote:
>>> The Xen hypercall interface is always using 4K page granularity on ARM
>>> and x86 architecture.
>>>
>>> With the incoming support of 64K page granularity
Hi David,
On 24/07/15 10:28, David Vrabel wrote:
> On 09/07/15 21:42, Julien Grall wrote:
>> The Xen hypercall interface is always using 4K page granularity on ARM
>> and x86 architecture.
>>
>> With the incoming support of 64K page granularity for ARM64 guest, it
>> won't be possible to re-use
On 09/07/15 21:42, Julien Grall wrote:
> The Xen hypercall interface is always using 4K page granularity on ARM
> and x86 architecture.
>
> With the incoming support of 64K page granularity for ARM64 guest, it
> won't be possible to re-use the Linux page definition in Xen drivers.
>
> Introduce
Hi David,
On 24/07/15 10:28, David Vrabel wrote:
On 09/07/15 21:42, Julien Grall wrote:
The Xen hypercall interface is always using 4K page granularity on ARM
and x86 architecture.
With the incoming support of 64K page granularity for ARM64 guest, it
won't be possible to re-use the Linux
On 24/07/15 10:48, David Vrabel wrote:
On 24/07/15 10:39, Julien Grall wrote:
Hi David,
On 24/07/15 10:28, David Vrabel wrote:
On 09/07/15 21:42, Julien Grall wrote:
The Xen hypercall interface is always using 4K page granularity on ARM
and x86 architecture.
With the incoming support of
On 09/07/15 21:42, Julien Grall wrote:
The Xen hypercall interface is always using 4K page granularity on ARM
and x86 architecture.
With the incoming support of 64K page granularity for ARM64 guest, it
won't be possible to re-use the Linux page definition in Xen drivers.
Introduce Xen
On 24/07/15 10:39, Julien Grall wrote:
Hi David,
On 24/07/15 10:28, David Vrabel wrote:
On 09/07/15 21:42, Julien Grall wrote:
The Xen hypercall interface is always using 4K page granularity on ARM
and x86 architecture.
With the incoming support of 64K page granularity for ARM64 guest, it
On 24/07/15 11:34, David Vrabel wrote:
On 24/07/15 10:51, Julien Grall wrote:
On 24/07/15 10:48, David Vrabel wrote:
On 24/07/15 10:39, Julien Grall wrote:
Hi David,
On 24/07/15 10:28, David Vrabel wrote:
On 09/07/15 21:42, Julien Grall wrote:
The Xen hypercall interface is always using 4K
On Fri, 2015-07-24 at 11:34 +0100, David Vrabel wrote:
it would be better to think that:
PFNs index guest-sized pages (which may be 64 KiB).
GFNs index Xen-sized pages (which is always 4 KiB).
This concept could be usefully added to the comment in
xen/include/xen/mm.h IMHO.
David
--
On 24/07/15 10:51, Julien Grall wrote:
On 24/07/15 10:48, David Vrabel wrote:
On 24/07/15 10:39, Julien Grall wrote:
Hi David,
On 24/07/15 10:28, David Vrabel wrote:
On 09/07/15 21:42, Julien Grall wrote:
The Xen hypercall interface is always using 4K page granularity on ARM
and x86
14 matches
Mail list logo
