lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 18 Jul 2012 12:08:03 +1000
From:	Michael Ellerman <michael@...erman.id.au>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Matt Evans <matt@...abs.org>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, kvm-ppc@...r.kernel.org,
	prerna@...ux.vnet.ibm.com,
	David Gibson <david@...son.dropbear.id.au>,
	Sasha Levin <levinsasha928@...il.com>,
	Asias He <asias.hejun@...il.com>,
	Cyrill Gorcunov <gorcunov@...il.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC/PATCH] Use kernel supplied MMU info for kvm tool

On Tue, 2012-07-17 at 17:09 +0300, Pekka Enberg wrote:
> On Tue, Jul 17, 2012 at 12:33 PM, Matt Evans <matt@...abs.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 Evans <matt@...abs.org>
> 
> Applied, thanks guys!

Thanks Pekka.

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 you planning on doing that in the master kvmtool tree anytime soon?
It's still based on 3.4-rc1 it seems.

cheers


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ