From: David Gibson <david@gibson.dropbear.id.au>
To: Alexander Graf <agraf@suse.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [0/4] pseries: Support and improvements for KVM Book3S-HV support (v2)
Date: Tue, 11 Oct 2011 10:39:14 +1100 [thread overview]
Message-ID: <20111010233914.GB12250@truffala.fritz.box> (raw)
In-Reply-To: <95EA8947-05BF-4356-84B0-3D47E0DEAD82@suse.de>
On Fri, Oct 07, 2011 at 08:57:49AM +0200, Alexander Graf wrote:
>
> On 30.09.2011, at 09:39, David Gibson wrote:
>
> > Alex Graf has added support for KVM acceleration of the pseries
> > machine, using his Book3S-PR KVM variant, which runs the guest in
> > userspace, emulating supervisor operations. Recent kernels now have
> > the Book3S-HV KVM variant which uses the hardware hypervisor features
> > of recent POWER CPUs. Alex's changes to qemu are enough to get qemu
> > working roughly with Book3S-HV, but taking full advantage of this mode
> > needs more work. This patch series makes a start on better exploiting
> > Book3S-HV.
> >
> > Even with these patches, qemu won't quite be able to run on a current
> > Book3S-HV KVM kernel. That's because current Book3S-HV requires guest
> > memory to be backed by hugepages, but qemu refuses to use hugepages
> > for guest memory unless KVM advertises CAP_SYNC_MMU, which Book3S-HV
> > does not currently do. We're working on improvements to the KVM code
> > which will implement CAP_SYNC_MMU and allow smallpage backing of
> > guests, but they're not there yet. So, in order to test Book3S-HV for
> > now you need to either:
> >
> > * Hack the host kernel to lie and advertise CAP_SYNC_MMU even though
> > it doesn't really implement it.
> >
> > or
> >
> > * Hack qemu so it does not check for CAP_SYNC_MMU when the -mem-path
> > option is used.
> >
> > Bot approaches are ugly and unsafe, but it seems we can generally get
> > away with it in practice. Obviously this is only an interim hack
> > until the proper CAP_SYNC_MMU support is ready.
>
> I would prefer the latter. We could even #ifdef it for TARGET_PPC.
Well, I don't see either approach as being remotely mergable. So it's
really up to each individual person playing with it which hack is
easier for them to apply temporarily while waiting for the proper
solution to come along.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2011-10-11 0:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 7:39 [Qemu-devel] [0/4] pseries: Support and improvements for KVM Book3S-HV support (v2) David Gibson
2011-09-30 7:39 ` [Qemu-devel] [PATCH 1/4] pseries: Support SMT systems for KVM Book3S-HV David Gibson
2011-09-30 7:39 ` [Qemu-devel] [PATCH 2/4] pseries: Allow KVM Book3S-HV on PPC970 CPUS David Gibson
2011-09-30 7:39 ` [Qemu-devel] [PATCH 3/4] pseries: Use Book3S-HV TCE acceleration capabilities David Gibson
2011-09-30 7:39 ` [Qemu-devel] [PATCH 4/4] pseries: Update SLOF firmware image David Gibson
2011-10-07 6:57 ` [Qemu-devel] [0/4] pseries: Support and improvements for KVM Book3S-HV support (v2) Alexander Graf
2011-10-10 23:39 ` David Gibson [this message]
2011-10-11 0:20 ` Alexander Graf
2011-10-11 0:39 ` David Gibson
2011-10-07 7:06 ` Alexander Graf
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=20111010233914.GB12250@truffala.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).