From: Michael Ellerman <michael@ellerman.id.au>
To: Pekka Enberg <penberg@kernel.org>
Cc: Matt Evans <matt@ozlabs.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm-ppc@vger.kernel.org, prerna@linux.vnet.ibm.com,
David Gibson <david@gibson.dropbear.id.au>,
Sasha Levin <levinsasha928@gmail.com>,
Asias He <asias.hejun@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC/PATCH] Use kernel supplied MMU info for kvm tool
Date: Wed, 18 Jul 2012 12:08:03 +1000 [thread overview]
Message-ID: <1342577283.25827.8.camel@concordia> (raw)
In-Reply-To: <CAOJsxLGf6K0G90i==-TJ8WmGvuwtp9mpxsCMSJYw7Wn-JAvpcA@mail.gmail.com>
On Tue, 2012-07-17 at 17:09 +0300, Pekka Enberg wrote:
> On Tue, Jul 17, 2012 at 12:33 PM, Matt Evans <matt@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 Evans <matt@ozlabs.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
next prev parent reply other threads:[~2012-07-18 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 5:00 [RFC/PATCH] Use kernel supplied MMU info for kvm tool Michael Ellerman
2012-07-17 5:00 ` [PATCH 01/10] kvm tools: Move mmap_anon_or_hugetblfs() into util Michael Ellerman
2012-07-17 5:00 ` [PATCH 02/10] kvm tools, powerpc: Use mmap_anon_or_hugetblfs() in kvm__arch_init() Michael Ellerman
2012-07-17 5:00 ` [PATCH 03/10] kvm tools: Remember page size as kvm->ram_pagesize Michael Ellerman
2012-07-17 5:00 ` [PATCH 04/10] kvm tools, powerpc: Use designated initializers for struct cpu_info Michael Ellerman
2012-07-17 5:00 ` [PATCH 05/10] kvm tools, powerpc: Use ARRAY_SIZE() in find_cpu_info() Michael Ellerman
2012-07-17 5:00 ` [PATCH 06/10] kvm tools, powerpc: Reformatting " Michael Ellerman
2012-07-17 5:00 ` [PATCH 07/10] kvm tools, powerpc: Restructure find_cpu_info() Michael Ellerman
2012-07-17 5:00 ` [PATCH 08/10] kvm tools, powerpc: Use MMU info from the kernel for ibm,segment-page-sizes Michael Ellerman
2012-07-17 5:00 ` [PATCH 09/10] kvm tools, powerpc: Use MMU info for ibm,processor-segment-sizes Michael Ellerman
2012-07-17 5:00 ` [PATCH 10/10] kvm tools, powerpc: Use MMU info for ibm,slb-size Michael Ellerman
2012-07-17 9:33 ` [RFC/PATCH] Use kernel supplied MMU info for kvm tool Matt Evans
2012-07-17 14:09 ` Pekka Enberg
2012-07-18 2:08 ` Michael Ellerman [this message]
2012-07-31 6:22 ` Pekka Enberg
2012-07-18 2:03 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1342577283.25827.8.camel@concordia \
--to=michael@ellerman.id.au \
--cc=asias.hejun@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=gorcunov@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@ozlabs.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prerna@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox