From: Nicholas Piggin <npiggin@gmail.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH v2 7/9] powerpc/64s: do not allocate lppaca if we are not virtualized
Date: Sat, 14 Oct 2017 13:54:44 +1000 [thread overview]
Message-ID: <20171014135444.45a8405f@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20171013224759.GA26120@fergus.ozlabs.ibm.com>
On Sat, 14 Oct 2017 09:47:59 +1100
Paul Mackerras <paulus@ozlabs.org> wrote:
> On Sun, Aug 13, 2017 at 11:33:44AM +1000, Nicholas Piggin wrote:
> > The "lppaca" is a structure registered with the hypervisor. This
> > is unnecessary when running on non-virtualised platforms. One field
> > from the lppaca (pmcregs_in_use) is also used by the host, so move
> > the host part out into the paca (lppaca field is still updated in
> > guest mode).
>
> There is an error in the patch, see below...
>
> > diff --git a/arch/powerpc/kvm/book3s_hv_rmhandlers.S b/arch/powerpc/kvm/book3s_hv_rmhandlers.S
> > index c52184a8efdf..b838348e3a2b 100644
> > --- a/arch/powerpc/kvm/book3s_hv_rmhandlers.S
> > +++ b/arch/powerpc/kvm/book3s_hv_rmhandlers.S
> > @@ -99,8 +99,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_ARCH_207S)
> > mtspr SPRN_SPRG_VDSO_WRITE,r3
> >
> > /* Reload the host's PMU registers */
> > - ld r3, PACALPPACAPTR(r13) /* is the host using the PMU? */
> > - lbz r4, LPPACA_PMCINUSE(r3)
> > + lbz r4, PACA_PMCINUSE(r13) /* is the host using the PMU? */
> > cmpwi r4, 0
> > beq 23f /* skip if not */
> > BEGIN_FTR_SECTION
> > @@ -1671,7 +1670,7 @@ END_FTR_SECTION_IFSET(CPU_FTR_ARCH_207S)
> > mtspr SPRN_MMCRA, r7
> > isync
> > beq 21f /* if no VPA, save PMU stuff anyway */
> > - lbz r7, LPPACA_PMCINUSE(r8)
> > + lbz r7, PACA_PMCINUSE(r13)
>
> We really do need to check the guest's flag not the host's here, since
> we're deciding whether to save the PMU state to the vcpu struct.
Okay I'll fix that up.
Thanks,
Nick
next prev parent reply other threads:[~2017-10-14 3:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 11:34 [PATCH v2 0/9] improve early structure allocations (paca, lppaca, etc) Nicholas Piggin
2017-08-13 1:33 ` [PATCH v2 1/9] KVM: PPC: Book3S HV: Fix H_REGISTER_VPA VPA size validation Nicholas Piggin
2017-08-15 11:24 ` Michael Ellerman
2017-08-31 3:41 ` Paul Mackerras
2017-08-13 1:33 ` [PATCH v2 2/9] powerpc/powernv: powernv platform is not constrained by RMA Nicholas Piggin
2017-08-31 11:36 ` [v2, " Michael Ellerman
2017-08-13 1:33 ` [PATCH v2 3/9] powerpc/powernv: Remove real mode access limit for early allocations Nicholas Piggin
2017-08-14 12:49 ` Michael Ellerman
2017-08-14 13:10 ` Benjamin Herrenschmidt
2017-08-14 14:51 ` Nicholas Piggin
2017-08-14 13:13 ` Benjamin Herrenschmidt
2017-08-15 12:10 ` Nicholas Piggin
2017-08-15 12:48 ` Benjamin Herrenschmidt
2017-08-15 13:02 ` Nicholas Piggin
2017-09-12 10:13 ` Aneesh Kumar K.V
2017-09-12 10:26 ` Benjamin Herrenschmidt
2017-08-13 1:33 ` [PATCH v2 4/9] powerpc/64s/radix: Remove bolted-SLB address limit for per-cpu stacks Nicholas Piggin
2017-08-31 11:36 ` [v2, " Michael Ellerman
2017-08-13 1:33 ` [PATCH v2 5/9] powerpc/64s: Relax PACA address limitations Nicholas Piggin
2017-08-13 1:33 ` [PATCH v2 6/9] powerpc/64s/radix: Do not allocate SLB shadow structures Nicholas Piggin
2017-08-31 11:36 ` [v2, " Michael Ellerman
2017-08-13 1:33 ` [PATCH v2 7/9] powerpc/64s: do not allocate lppaca if we are not virtualized Nicholas Piggin
2017-10-13 22:47 ` Paul Mackerras
2017-10-14 3:54 ` Nicholas Piggin [this message]
2017-08-13 1:33 ` [PATCH v2 8/9] powerpc/64: Use a table of paca pointers and allocate pacas individually Nicholas Piggin
2017-08-15 15:50 ` Nicholas Piggin
2017-08-15 17:30 ` kbuild test robot
2017-08-13 1:33 ` [PATCH v2 9/9] powerpc/64: Use a table of lppaca pointers and allocate lppacas individually Nicholas Piggin
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=20171014135444.45a8405f@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 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).