From: Miles Glenn <milesg@linux.vnet.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v3 0/4] Add BHRB Facility Support
Date: Mon, 27 Nov 2023 14:51:54 -0600 [thread overview]
Message-ID: <c39ad84ee405d3539b40db34f920dc2879a940b4.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <66558e7df3b0eadece637f452bfbf7add72955eb.camel@linux.vnet.ibm.com>
On Wed, 2023-10-18 at 10:59 -0500, Miles Glenn wrote:
> On Thu, 2023-10-19 at 01:06 +1000, Nicholas Piggin wrote:
> > On Tue Sep 26, 2023 at 3:43 AM AEST, Glenn Miles wrote:
> > > This is a series of patches for adding support for the Branch
> > > History
> > > Rolling Buffer (BHRB) facility. This was added to the Power ISA
> > > starting with version 2.07. Changes were subsequently made in
> > > version
> > > 3.1 to limit BHRB recording to instructions run in problem state
> > > only
> > > and to add a control bit to disable recording (MMCRA[BHRBRD]).
> > >
> > > Version 3 of this series disables branch recording on P8 and P9
> > > due
> > > to a drop in performance caused by recording branches outside of
> > > problem state.
> >
> > Thanks for these, they all look good to me.
> >
> > With P10 CPU, Linux perf branch recording appears to work with this
> > series, and I confirmed that Linux does disable BHRB in MMCRA at
> > boot, so it should not take the performance hit.
> >
> > It had a couple of compile bugs, no matter I fixed them, but I
> > often
> > trip overppc32 and user-mode when working on TCG too, so building
> > with --target-list including ppc64-softmmu,ppc-softmmu,
> > ppc64-linux-user,ppc64le-linux-user,ppc-linux-user is good to catch
> > those.
> >
> > Thanks,
> > Nick
> >
>
> Thanks, Nick. I'll have to remember that for next time!
>
> Glenn
>
Hi Nick,
Is there anything else you need me to do for this series to be merged?
Thanks,
Glenn
> > > Glenn Miles (4):
> > > target/ppc: Add new hflags to support BHRB
> > > target/ppc: Add recording of taken branches to BHRB
> > > target/ppc: Add clrbhrb and mfbhrbe instructions
> > > target/ppc: Add migration support for BHRB
> > >
> > > target/ppc/cpu.h | 24 ++++++
> > > target/ppc/cpu_init.c | 39 +++++++++-
> > > target/ppc/helper.h | 5 ++
> > > target/ppc/helper_regs.c | 35 +++++++++
> > > target/ppc/insn32.decode | 8 ++
> > > target/ppc/machine.c | 23 +++++-
> > > target/ppc/misc_helper.c | 46 +++++++++++
> > > target/ppc/power8-pmu-regs.c.inc | 5 ++
> > > target/ppc/power8-pmu.c | 48 +++++++++++-
> > > target/ppc/power8-pmu.h | 11 ++-
> > > target/ppc/spr_common.h | 1 +
> > > target/ppc/translate.c | 101
> > > +++++++++++++++++++++++--
> > > target/ppc/translate/bhrb-impl.c.inc | 43 +++++++++++
> > > target/ppc/translate/branch-impl.c.inc | 2 +-
> > > 14 files changed, 374 insertions(+), 17 deletions(-)
> > > create mode 100644 target/ppc/translate/bhrb-impl.c.inc
next prev parent reply other threads:[~2023-11-27 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 17:43 [PATCH v3 0/4] Add BHRB Facility Support Glenn Miles
2023-09-25 17:43 ` [PATCH v3 1/4] target/ppc: Add new hflags to support BHRB Glenn Miles
2023-09-25 17:43 ` [PATCH v3 2/4] target/ppc: Add recording of taken branches to BHRB Glenn Miles
2024-02-05 8:37 ` Nicholas Piggin
2023-09-25 17:43 ` [PATCH v3 3/4] target/ppc: Add clrbhrb and mfbhrbe instructions Glenn Miles
2023-09-25 17:43 ` [PATCH v3 4/4] target/ppc: Add migration support for BHRB Glenn Miles
2023-10-18 15:06 ` [PATCH v3 0/4] Add BHRB Facility Support Nicholas Piggin
2023-10-18 15:59 ` Miles Glenn
2023-11-27 20:51 ` Miles Glenn [this message]
2023-11-28 1:50 ` Nicholas Piggin
2024-02-05 8:05 ` 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=c39ad84ee405d3539b40db34f920dc2879a940b4.camel@linux.vnet.ibm.com \
--to=milesg@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=npiggin@gmail.com \
--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).