From: David Gibson <david@gibson.dropbear.id.au>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] pseries: Correct vmx/dfp handling in both KVM and TCG cases
Date: Tue, 25 Oct 2011 10:11:40 +1100 [thread overview]
Message-ID: <20111024231140.GC4191@truffala.fritz.box> (raw)
In-Reply-To: <8DEA1BBB-904C-457E-8269-3A4C98092EC3@suse.de>
On Mon, Oct 24, 2011 at 10:25:26AM -0700, Alexander Graf wrote:
> On 23.10.2011, at 22:29, David Gibson wrote:
> > On Thu, Oct 20, 2011 at 11:49:40PM -0700, Alexander Graf wrote:
[snip]
> >>> This gets further complicated in the case of the w-i-p patch I have to
> >>> properly advertise page sizes, where it's not just presence or absence
> >>> of a feature, but the specific SLB and HPTE encodings must be
> >>> advertised to the guest.
> >>
> >> Yup, so we'd read out the host dt to find the host possible
> >> encodings (probably a bad idea, but that's a different story)
> >
> > Um, a different story perhaps, but one I kind of need an answer to in
> > the near future... I can query the host cpu's page sizes easily
> > enough, but I'm really not sure where this should be stashed before
> > filtering as suggested below.
>
> Page sizes are usually powers of 2, so we should be ok with just
> having a bitmap there with each bit meaning 1 << (n + 12).
Not sufficient. Again, it's not just the presence/absence of page
sizes I need, but the SLB and HPTE bit encodings. And even if it
weren't for that, we need which base page size versus actual page
sizes combinations are supported, not just whether a given page size
is supported somehow.
I did have a draft patch adding more generalized multiple page size
support to TCG, which would have provided a solution except that a) I
don't really want to finish tha off - still a fair bit of work - just
in order to pass through host page sizes and b) I lost the draft in an
unfortunate encfs+git corruption incident :(.
--
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
prev parent reply other threads:[~2011-10-24 23:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 4:15 [Qemu-devel] [PATCH] pseries: Correct vmx/dfp handling in both KVM and TCG cases David Gibson
2011-10-20 17:12 ` Alexander Graf
2011-10-21 0:41 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2011-10-21 2:40 ` Alexander Graf
2011-10-21 5:06 ` David Gibson
2011-10-21 6:49 ` Alexander Graf
2011-10-24 5:29 ` David Gibson
2011-10-24 17:25 ` Alexander Graf
2011-10-24 17:55 ` Alexander Graf
2011-10-24 17:59 ` Alexander Graf
2011-10-24 23:08 ` David Gibson
2011-10-24 23:43 ` Alexander Graf
2011-10-25 0:09 ` David Gibson
2011-10-25 1:20 ` Alexander Graf
2011-10-24 23:11 ` David Gibson [this message]
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=20111024231140.GC4191@truffala.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).