[patch 02/18] x86: kvmclock: allocate pvclock shared memory area

We want to expose the pvclock shared memory areas, which the hypervisor periodically updates, to userspace. For a linear mapping from userspace, it is necessary that entire page sized regions are used for array of pvclock structures. There is no such guarantee with per cpu areas, therefore move

Re: [patch 02/18] x86: kvmclock: allocate pvclock shared memory area (v2)

On 11/16/2012 06:07 AM, Marcelo Tosatti wrote: > > We want to expose the pvclock shared memory areas, which > the hypervisor periodically updates, to userspace. > > For a linear mapping from userspace, it is necessary that > entire page sized regions are used for array of pvclock > structures.

[patch 02/18] x86: kvmclock: allocate pvclock shared memory area (v2)

We want to expose the pvclock shared memory areas, which the hypervisor periodically updates, to userspace. For a linear mapping from userspace, it is necessary that entire page sized regions are used for array of pvclock structures. There is no such guarantee with per cpu areas, therefore mov

Re: [patch 02/18] x86: kvmclock: allocate pvclock shared memory area

On 11/15/2012 04:08 AM, Marcelo Tosatti wrote: > We want to expose the pvclock shared memory areas, which > the hypervisor periodically updates, to userspace. > > For a linear mapping from userspace, it is necessary that > entire page sized regions are used for array of pvclock > structures. >

[patch 02/18] x86: kvmclock: allocate pvclock shared memory area

We want to expose the pvclock shared memory areas, which the hypervisor periodically updates, to userspace. For a linear mapping from userspace, it is necessary that entire page sized regions are used for array of pvclock structures. There is no such guarantee with per cpu areas, therefore move