From: Bharata B Rao <bharata@linux.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: aneesh.kumar@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
npiggin@gmail.com, kvm-ppc@vger.kernel.org
Subject: Re: [RFC PATCH v0 2/2] KVM: PPC: Book3S HV: Use H_RPT_INVALIDATE in nested KVM
Date: Thu, 9 Jul 2020 14:38:51 +0530 [thread overview]
Message-ID: <20200709090851.GD7902@in.ibm.com> (raw)
In-Reply-To: <20200709051803.GC2822576@thinks.paulus.ozlabs.org>
On Thu, Jul 09, 2020 at 03:18:03PM +1000, Paul Mackerras wrote:
> On Fri, Jul 03, 2020 at 04:14:20PM +0530, Bharata B Rao wrote:
> > In the nested KVM case, replace H_TLB_INVALIDATE by the new hcall
> > H_RPT_INVALIDATE if available. The availability of this hcall
> > is determined from "hcall-rpt-invalidate" string in ibm,hypertas-functions
> > DT property.
>
> What are we going to use when nested KVM supports HPT guests at L2?
> L1 will need to do partition-scoped tlbies with R=0 via a hypercall,
> but H_RPT_INVALIDATE says in its name that it only handles radix
> page tables (i.e. R=1).
For L2 HPT guests, the old hcall is expected to work after it adds
support for R=0 case?
The new hcall should be advertised via ibm,hypertas-functions only
for radix guests I suppose.
Regards,
Bharata.
WARNING: multiple messages have this Message-ID (diff)
From: Bharata B Rao <bharata@linux.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: aneesh.kumar@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
npiggin@gmail.com, kvm-ppc@vger.kernel.org
Subject: Re: [RFC PATCH v0 2/2] KVM: PPC: Book3S HV: Use H_RPT_INVALIDATE in nested KVM
Date: Thu, 09 Jul 2020 09:20:51 +0000 [thread overview]
Message-ID: <20200709090851.GD7902@in.ibm.com> (raw)
In-Reply-To: <20200709051803.GC2822576@thinks.paulus.ozlabs.org>
On Thu, Jul 09, 2020 at 03:18:03PM +1000, Paul Mackerras wrote:
> On Fri, Jul 03, 2020 at 04:14:20PM +0530, Bharata B Rao wrote:
> > In the nested KVM case, replace H_TLB_INVALIDATE by the new hcall
> > H_RPT_INVALIDATE if available. The availability of this hcall
> > is determined from "hcall-rpt-invalidate" string in ibm,hypertas-functions
> > DT property.
>
> What are we going to use when nested KVM supports HPT guests at L2?
> L1 will need to do partition-scoped tlbies with R=0 via a hypercall,
> but H_RPT_INVALIDATE says in its name that it only handles radix
> page tables (i.e. R=1).
For L2 HPT guests, the old hcall is expected to work after it adds
support for R=0 case?
The new hcall should be advertised via ibm,hypertas-functions only
for radix guests I suppose.
Regards,
Bharata.
next prev parent reply other threads:[~2020-07-09 9:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 10:44 [RFC PATCH v0 0/2] Use H_RPT_INVALIDATE for nested guest Bharata B Rao
2020-07-03 10:56 ` Bharata B Rao
2020-07-03 10:44 ` [RFC PATCH v0 1/2] KVM: PPC: Book3S HV: Add support for H_RPT_INVALIDATE (nested case only) Bharata B Rao
2020-07-03 10:56 ` Bharata B Rao
2020-07-03 10:44 ` [RFC PATCH v0 2/2] KVM: PPC: Book3S HV: Use H_RPT_INVALIDATE in nested KVM Bharata B Rao
2020-07-03 10:56 ` Bharata B Rao
2020-07-09 5:18 ` Paul Mackerras
2020-07-09 5:18 ` Paul Mackerras
2020-07-09 9:08 ` Bharata B Rao [this message]
2020-07-09 9:20 ` Bharata B Rao
2020-07-09 10:07 ` Paul Mackerras
2020-07-09 10:07 ` Paul Mackerras
2020-07-14 5:31 ` Bharata B Rao
2020-07-14 5:43 ` Bharata B Rao
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=20200709090851.GD7902@in.ibm.com \
--to=bharata@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.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.