From: David Gibson <david@gibson.dropbear.id.au>
To: kvm-ppc@vger.kernel.org
Subject: Re: [RFC PATCH 20/32] KVM: PPC: Book3S HV: Nested guest entry via hypercall
Date: Thu, 27 Sep 2018 03:28:03 +0000 [thread overview]
Message-ID: <20180927032803.GG30868@umbus.fritz.box> (raw)
In-Reply-To: <1537524123-9578-21-git-send-email-paulus@ozlabs.org>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
On Thu, Sep 27, 2018 at 11:45:21AM +1000, Paul Mackerras wrote:
> On Thu, Sep 27, 2018 at 10:57:17AM +1000, David Gibson wrote:
> > On Wed, Sep 26, 2018 at 08:59:22PM +1000, Paul Mackerras wrote:
> > > On Wed, Sep 26, 2018 at 03:41:07PM +1000, David Gibson wrote:
> > > > On Fri, Sep 21, 2018 at 08:01:51PM +1000, Paul Mackerras wrote:
> > > > > + if (!kvm_is_radix(vcpu->kvm))
> > > > > + return H_FUNCTION;
> > > >
> > > > Would it be safer / cleaner to have this instead check that the L1 has
> > > > completed an H_SET_PARTITION_TABLE? Which wouldn't be allowed for an
> > > > HPT guest.
> > >
> > > There is no valid bit in the PTCR value, and the PTCR could have been
> > > set via the one-reg interface without there having been a
> > > H_SET_PARTITION_TABLE in the lifetime of this KVM instance (for
> > > example when the L1 guest has been migrated in from another machine),
> > > so I don't see a foolproof way to do what you suggest.
> >
> > Ah, right.
> >
> > Would checking if the vPTCR is != it's initial value (0?) do the job?
> > (AFAICT PTCR==0 would be unusable, even if technically allowed).
>
> If I did check PTCR, what error code would you suggest? I'm sure
> you'd tell me not to use H_FUNCTION. :)
Probably H_NOT_AVAILABLE? That's what I use if you attempt an HPT
resize from an RPT guest.
--
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-09-27 3:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 10:01 [RFC PATCH 20/32] KVM: PPC: Book3S HV: Nested guest entry via hypercall Paul Mackerras
2018-09-26 5:41 ` David Gibson
2018-09-26 10:59 ` Paul Mackerras
2018-09-27 0:57 ` David Gibson
2018-09-27 1:45 ` Paul Mackerras
2018-09-27 3:28 ` 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=20180927032803.GG30868@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.