On Wed, 18 Jul 2012, Michael Ellerman wrote:
> It occurred to me overnight that I forgot to mention that in order to
> build the new code you need the headers from a 3.5-rc1 era kernel (for
> the ioctl & KVM_CAP definitions).
>
> The easiest way to do that is to merge linus' tree into kvmtool.
>
On Wed, 18 Jul 2012, Michael Ellerman wrote:
It occurred to me overnight that I forgot to mention that in order to
build the new code you need the headers from a 3.5-rc1 era kernel (for
the ioctl KVM_CAP definitions).
The easiest way to do that is to merge linus' tree into kvmtool.
Are
On Tue, 2012-07-17 at 17:09 +0300, Pekka Enberg wrote:
> On Tue, Jul 17, 2012 at 12:33 PM, Matt Evans wrote:
> > Just had a look, all good. Thanks for tidying some old FIXMEs, especially
> > the page/segment DT props encoding grot -- and the designated inits in the
> > cpuinfo struct, whew, I
On Tue, 2012-07-17 at 10:33 +0100, Matt Evans wrote:
> Hi Michael,
>
> On 2012-07-17 06:00, Michael Ellerman wrote:
>
> > This is a series for kvmtool that uses a newish kernel API to get
> > MMU info, which is then fed to the guest.
> >
> > Currently we just make a good guess based on the PVR,
On Tue, Jul 17, 2012 at 12:33 PM, Matt Evans wrote:
> Just had a look, all good. Thanks for tidying some old FIXMEs, especially
> the page/segment DT props encoding grot -- and the designated inits in the
> cpuinfo struct, whew, I heard the scream on IRC. Sorry. ;-)
>
> Acked-by: Matt Evans
Hi Michael,
On 2012-07-17 06:00, Michael Ellerman wrote:
This is a series for kvmtool that uses a newish kernel API to get
MMU info, which is then fed to the guest.
Currently we just make a good guess based on the PVR, but that is
potentially flakey in a few ways. The most notable is that if
Hi Michael,
On 2012-07-17 06:00, Michael Ellerman wrote:
This is a series for kvmtool that uses a newish kernel API to get
MMU info, which is then fed to the guest.
Currently we just make a good guess based on the PVR, but that is
potentially flakey in a few ways. The most notable is that if
On Tue, Jul 17, 2012 at 12:33 PM, Matt Evans m...@ozlabs.org wrote:
Just had a look, all good. Thanks for tidying some old FIXMEs, especially
the page/segment DT props encoding grot -- and the designated inits in the
cpuinfo struct, whew, I heard the scream on IRC. Sorry. ;-)
Acked-by: Matt
On Tue, 2012-07-17 at 10:33 +0100, Matt Evans wrote:
Hi Michael,
On 2012-07-17 06:00, Michael Ellerman wrote:
This is a series for kvmtool that uses a newish kernel API to get
MMU info, which is then fed to the guest.
Currently we just make a good guess based on the PVR, but that is
On Tue, 2012-07-17 at 17:09 +0300, Pekka Enberg wrote:
On Tue, Jul 17, 2012 at 12:33 PM, Matt Evans m...@ozlabs.org wrote:
Just had a look, all good. Thanks for tidying some old FIXMEs, especially
the page/segment DT props encoding grot -- and the designated inits in the
cpuinfo struct,
Hi all,
This is a series for kvmtool that uses a newish kernel API to get
MMU info, which is then fed to the guest.
Currently we just make a good guess based on the PVR, but that is
potentially flakey in a few ways. The most notable is that if you don't
specify hugepages we don't boot - because
Hi all,
This is a series for kvmtool that uses a newish kernel API to get
MMU info, which is then fed to the guest.
Currently we just make a good guess based on the PVR, but that is
potentially flakey in a few ways. The most notable is that if you don't
specify hugepages we don't boot - because
12 matches
Mail list logo
