qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, Thomas Huth <thuth@redhat.com>,
	Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
	farosas@linux.ibm.com, "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org, clg@kaod.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	paulus@samba.org
Subject: Re: [PATCH v6 06/18] spapr, ppc: Remove VPM0/RMLS hacks for POWER9
Date: Tue, 25 Feb 2020 16:58:01 +0100	[thread overview]
Message-ID: <20200225165801.14cba74c@bahia.home> (raw)
In-Reply-To: <20200225122900.0fe0780b@bahia.home>

On Tue, 25 Feb 2020 12:29:00 +0100
Greg Kurz <groug@kaod.org> wrote:

> On Tue, 25 Feb 2020 10:37:12 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > For the "pseries" machine, we use "virtual hypervisor" mode where we
> > only model the CPU in non-hypervisor privileged mode.  This means that
> > we need guest physical addresses within the modelled cpu to be treated
> > as absolute physical addresses.
> > 
> > We used to do that by clearing LPCR[VPM0] and setting LPCR[RMLS] to a high
> > limit so that the old offset based translation for guest mode applied,
> > which does what we need.  However, POWER9 has removed support for that
> > translation mode, which meant we had some ugly hacks to keep it working.
> > 
> > We now explicitly handle this sort of translation for virtual hypervisor
> > mode, so the hacks aren't necessary.  We don't need to set VPM0 and RMLS
> > from the machine type code - they're now ignored in vhyp mode.  On the cpu
> > side we don't need to allow LPCR[RMLS] to be set on POWER9 in vhyp mode -
> > that was only there to allow the hack on the machine side.
> > 
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > Reviewed-by: Cédric Le Goater <clg@kaod.org>
> > ---
> 
> Reviewed-by: Greg Kurz <groug@kaod.org>
> 

Ah wait...

> >  hw/ppc/spapr_cpu_core.c | 6 +-----
> >  target/ppc/mmu-hash64.c | 8 --------
> >  2 files changed, 1 insertion(+), 13 deletions(-)
> > 
> > diff --git a/hw/ppc/spapr_cpu_core.c b/hw/ppc/spapr_cpu_core.c
> > index d09125d9af..ea5e11f1d9 100644
> > --- a/hw/ppc/spapr_cpu_core.c
> > +++ b/hw/ppc/spapr_cpu_core.c
> > @@ -58,14 +58,10 @@ static void spapr_reset_vcpu(PowerPCCPU *cpu)
> >       * we don't get spurious wakups before an RTAS start-cpu call.
> >       * For the same reason, set PSSCR_EC.
> >       */
> > -    lpcr &= ~(LPCR_VPM0 | LPCR_VPM1 | LPCR_ISL | LPCR_KBV | pcc->lpcr_pm);
> > +    lpcr &= ~(LPCR_VPM1 | LPCR_ISL | LPCR_KBV | pcc->lpcr_pm);

... a few lines above, we have a comment that should be dropped as well.

     * Clearing VPM0 will also cause us to use RMOR in mmu-hash64.c for
     * real mode accesses, which thankfully defaults to 0 and isn't
     * accessible in guest mode.

My R-b tag stands anyway.

> >      lpcr |= LPCR_LPES0 | LPCR_LPES1;
> >      env->spr[SPR_PSSCR] |= PSSCR_EC;
> >  
> > -    /* Set RMLS to the max (ie, 16G) */
> > -    lpcr &= ~LPCR_RMLS;
> > -    lpcr |= 1ull << LPCR_RMLS_SHIFT;
> > -
> >      ppc_store_lpcr(cpu, lpcr);
> >  
> >      /* Set a full AMOR so guest can use the AMR as it sees fit */
> > diff --git a/target/ppc/mmu-hash64.c b/target/ppc/mmu-hash64.c
> > index e372c42add..caf47ad6fc 100644
> > --- a/target/ppc/mmu-hash64.c
> > +++ b/target/ppc/mmu-hash64.c
> > @@ -1126,14 +1126,6 @@ void ppc_store_lpcr(PowerPCCPU *cpu, target_ulong val)
> >                        (LPCR_PECE_L_MASK & (LPCR_PDEE | LPCR_HDEE | LPCR_EEE |
> >                        LPCR_DEE | LPCR_OEE)) | LPCR_MER | LPCR_GTSE | LPCR_TC |
> >                        LPCR_HEIC | LPCR_LPES0 | LPCR_HVICE | LPCR_HDICE);
> > -        /*
> > -         * If we have a virtual hypervisor, we need to bring back RMLS. It
> > -         * doesn't exist on an actual P9 but that's all we know how to
> > -         * configure with softmmu at the moment
> > -         */
> > -        if (cpu->vhyp) {
> > -            lpcr |= (val & LPCR_RMLS);
> > -        }
> >          break;
> >      default:
> >          g_assert_not_reached();
> 
> 



  reply	other threads:[~2020-02-25 15:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 23:37 [PATCH v6 00/18] target/ppc: Correct some errors with real mode handling David Gibson
2020-02-24 23:37 ` [PATCH v6 01/18] pseries: Update SLOF firmware image David Gibson
2020-02-24 23:37 ` [PATCH v6 02/18] ppc: Remove stub support for 32-bit hypervisor mode David Gibson
2020-02-25  6:31   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 03/18] ppc: Remove stub of PPC970 HID4 implementation David Gibson
2020-02-24 23:37 ` [PATCH v6 04/18] target/ppc: Correct handling of real mode accesses with vhyp on hash MMU David Gibson
2020-02-25 10:29   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 05/18] target/ppc: Introduce ppc_hash64_use_vrma() helper David Gibson
2020-02-25  0:12   ` Fabiano Rosas
2020-02-25 10:30   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 06/18] spapr, ppc: Remove VPM0/RMLS hacks for POWER9 David Gibson
2020-02-25 11:29   ` Greg Kurz
2020-02-25 15:58     ` Greg Kurz [this message]
2020-02-26  1:00       ` David Gibson
2020-02-24 23:37 ` [PATCH v6 07/18] target/ppc: Remove RMOR register from POWER9 & POWER10 David Gibson
2020-02-25 11:30   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 08/18] target/ppc: Use class fields to simplify LPCR masking David Gibson
2020-02-25 15:48   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 09/18] target/ppc: Streamline calculation of RMA limit from LPCR[RMLS] David Gibson
2020-02-25 17:05   ` Greg Kurz
2020-02-25 22:47     ` Greg Kurz
2020-02-26  1:04       ` David Gibson
2020-02-26  7:56         ` Greg Kurz
2020-02-27  4:25           ` David Gibson
2020-02-24 23:37 ` [PATCH v6 10/18] target/ppc: Correct RMLS table David Gibson
2020-02-26  8:23   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 11/18] target/ppc: Only calculate RMLS derived RMA limit on demand David Gibson
2020-02-26 13:24   ` Greg Kurz
2020-02-27  4:33     ` David Gibson
2020-02-24 23:37 ` [PATCH v6 12/18] target/ppc: Don't store VRMA SLBE persistently David Gibson
2020-02-25  0:25   ` Fabiano Rosas
2020-02-26 13:29   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 13/18] spapr: Don't use weird units for MIN_RMA_SLOF David Gibson
2020-02-25  7:49   ` Cédric Le Goater
2020-02-26 13:32   ` Greg Kurz
2020-02-24 23:37 ` [PATCH v6 14/18] spapr,ppc: Simplify signature of kvmppc_rma_size() David Gibson
2020-02-24 23:37 ` [PATCH v6 15/18] spapr: Don't attempt to clamp RMA to VRMA constraint David Gibson
2020-02-24 23:37 ` [PATCH v6 16/18] spapr: Don't clamp RMA to 16GiB on new machine types David Gibson
2020-02-24 23:37 ` [PATCH v6 17/18] spapr: Clean up RMA size calculation David Gibson
2020-02-25 11:07   ` Philippe Mathieu-Daudé
2020-02-26  1:08     ` David Gibson
2020-02-26 13:37   ` Greg Kurz
2020-02-27  6:04     ` David Gibson
2020-02-24 23:37 ` [PATCH v6 18/18] spapr: Fold spapr_node0_size() into its only caller David Gibson
2020-02-26 14:47   ` Greg Kurz

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=20200225165801.14cba74c@bahia.home \
    --to=groug@kaod.org \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=farosas@linux.ibm.com \
    --cc=imammedo@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=paulus@samba.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=xiaoguangrong.eric@gmail.com \
    /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).