From: Glenn Miles <milesg@linux.vnet.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>
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>,
"Greg Kurz" <groug@kaod.org>,
"open list:PowerPC TCG CPUs" <qemu-ppc@nongnu.org>
Subject: Re: [PATCH 1/4] target/ppc: Add new hflags to support BHRB
Date: Tue, 19 Sep 2023 16:19:12 -0500 [thread overview]
Message-ID: <61e8d5bb7aa50c3fc16caf29a8ff7dce@linux.vnet.ibm.com> (raw)
In-Reply-To: <CVJ2M9HZE734.1G62AT05YOJTP@wheely>
On 2023-09-14 19:39, Nicholas Piggin wrote:
> On Wed Sep 13, 2023 at 6:23 AM AEST, Glenn Miles wrote:
>> This commit is preparatory to the addition of Branch History
>> Rolling Buffer (BHRB) functionality, which is being provided
>> today starting with the P8 processor.
>>
>> BHRB uses several SPR register fields to control whether or not
>> a branch instruction's address (and sometimes target address)
>> should be recorded. Checking each of these fields with each
>> branch instruction using jitted code would lead to a significant
>> decrease in performance.
>>
>> Therefore, it was decided that BHRB configuration bits that are
>> not expected to change frequently should have their state stored in
>> hflags so that the amount of checking done by jitted code can
>> be reduced.
>>
>> This commit contains the changes for storing the state of the
>> following register fields as hflags:
>>
>> MMCR0[FCP] - Determines if BHRB recording is frozen in the
>> problem state
>>
>> MMCR0[FCPC] - A modifier for MMCR0[FCP]
>>
>> MMCRA[BHRBRD] - Disables all BHRB recording for a thread
>>
>> Signed-off-by: Glenn Miles <milesg@linux.vnet.ibm.com>
>> ---
>> target/ppc/cpu.h | 9 +++++++++
>> target/ppc/cpu_init.c | 4 ++--
>> target/ppc/helper.h | 1 +
>> target/ppc/helper_regs.c | 12 ++++++++++++
>> target/ppc/machine.c | 2 +-
>> target/ppc/power8-pmu-regs.c.inc | 5 +++++
>> target/ppc/power8-pmu.c | 15 +++++++++++----
>> target/ppc/power8-pmu.h | 4 ++--
>> target/ppc/spr_common.h | 1 +
>> target/ppc/translate.c | 6 ++++++
>> 10 files changed, 50 insertions(+), 9 deletions(-)
>>
>> diff --git a/target/ppc/cpu.h b/target/ppc/cpu.h
>> index 25fac9577a..20ae1466a5 100644
>> --- a/target/ppc/cpu.h
>> +++ b/target/ppc/cpu.h
>> @@ -439,6 +439,9 @@ FIELD(MSR, LE, MSR_LE, 1)
>> #define MMCR0_FC56 PPC_BIT(59) /* PMC Freeze Counters 5-6
>> bit */
>> #define MMCR0_PMC1CE PPC_BIT(48) /* MMCR0 PMC1 Condition
>> Enabled */
>> #define MMCR0_PMCjCE PPC_BIT(49) /* MMCR0 PMCj Condition
>> Enabled */
>> +#define MMCR0_BHRBA PPC_BIT_NR(42) /* BHRB Available */
>
> It's confusing to use NR for this. Either call it MMCR0_BHRBA_NR or
> have
> the facility check in patch 3 take the bit value. I'd move it to patch
> 3
> too.
>
Ok, adding NR suffix.
>> +#define MMCR0_FCP PPC_BIT(34) /* Freeze Counters/BHRB if
>> PR=1 */
>> +#define MMCR0_FCPC PPC_BIT(51) /* Condition for FCP bit */
>> /* MMCR0 userspace r/w mask */
>> #define MMCR0_UREG_MASK (MMCR0_FC | MMCR0_PMAO | MMCR0_PMAE)
>> /* MMCR2 userspace r/w mask */
>> @@ -451,6 +454,9 @@ FIELD(MSR, LE, MSR_LE, 1)
>> #define MMCR2_UREG_MASK (MMCR2_FC1P0 | MMCR2_FC2P0 | MMCR2_FC3P0 | \
>> MMCR2_FC4P0 | MMCR2_FC5P0 | MMCR2_FC6P0)
>>
>> +#define MMCRA_BHRBRD PPC_BIT(26) /* BHRB Recording
>> Disable */
>> +
>> +
>> #define MMCR1_EVT_SIZE 8
>> /* extract64() does a right shift before extracting */
>> #define MMCR1_PMC1SEL_START 32
>> @@ -703,6 +709,9 @@ enum {
>> HFLAGS_PMCJCE = 17, /* MMCR0 PMCjCE bit */
>> HFLAGS_PMC_OTHER = 18, /* PMC other than PMC5-6 is enabled */
>> HFLAGS_INSN_CNT = 19, /* PMU instruction count enabled */
>> + HFLAGS_FCPC = 20, /* MMCR0 FCPC bit */
>> + HFLAGS_FCP = 21, /* MMCR0 FCP bit */
>> + HFLAGS_BHRBRD = 22, /* MMCRA BHRBRD bit */
>> HFLAGS_VSX = 23, /* MSR_VSX if cpu has VSX */
>> HFLAGS_VR = 25, /* MSR_VR if cpu has VRE */
>
> hflags are an interesting tradeoff. You can specialise some code but
> at the cost of duplicating your jit footprint, which is often the
> most costly thing. The ideal hflag is one where code is not shared
> between flag set/clear like PR and HV. Rarely used features is another
> good one, that BHRB falls into.
>
> But, we do want flags that carry stronger or more direct semantics
> wrt code generation because you want to avoid redundant hflags values
> that result in the same code generation. I might have missed something
> but AFAIKS BHRB_ENABLED could be a combination of this logic (from
> later patch):
>
> + /* ISA 3.1 adds the PMCRA[BRHBRD] and problem state checks */
> + if ((ctx->insns_flags2 & PPC2_ISA310) && (ctx->mmcra_bhrbrd ||
> !ctx->pr)) {
> + return;
> + }
> +
> + /* Check for BHRB "frozen" conditions */
> + if (ctx->mmcr0_fcpc) {
> + if (ctx->mmcr0_fcp) {
> + if ((ctx->hv) && (ctx->pr)) {
> + return;
> + }
> + } else if (!(ctx->hv) && (ctx->pr)) {
> + return;
> + }
> + } else if ((ctx->mmcr0_fcp) && (ctx->pr)) {
> + return;
> + }
>
Ok, Combining above logic into a single hflag.
> Otherwise the patch looks good to me.
>
> Thanks,
> Nick
next prev parent reply other threads:[~2023-09-19 21:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 19:21 [PATCH 0/4] Add BHRB Facility Support Glenn Miles
2023-09-12 20:23 ` [PATCH 1/4] target/ppc: Add new hflags to support BHRB Glenn Miles
2023-09-15 0:39 ` Nicholas Piggin
2023-09-19 21:19 ` Glenn Miles [this message]
2023-09-12 20:24 ` [PATCH 2/4] target/ppc: Add recording of taken branches to BHRB Glenn Miles
2023-09-15 1:02 ` Nicholas Piggin
2023-09-19 21:35 ` Glenn Miles
2023-09-21 15:45 ` Glenn Miles
2023-09-12 20:24 ` [PATCH 3/4] target/ppc: Add clrbhrb and mfbhrbe instructions Glenn Miles
2023-09-15 1:13 ` Nicholas Piggin
2023-09-19 21:40 ` Glenn Miles
2023-09-12 20:25 ` [PATCH 4/4] target/ppc: Add migration support for BHRB Glenn Miles
2023-09-15 1:20 ` Nicholas Piggin
2023-09-19 22:01 ` Glenn Miles
2023-09-12 20:57 ` [PATCH 3/4] target/ppc: Add clrbhrb and mfbhrbe instructions Glenn Miles
2023-09-12 21:05 ` [PATCH 4/4] target/ppc: Add migration support for BHRB Glenn Miles
2023-09-12 21:27 ` Glenn Miles
-- strict thread matches above, loose matches on Subject: below --
2023-09-11 21:23 [PATCH 0/4] Add BHRB Facility Support Glenn Miles
2023-09-11 21:23 ` [PATCH 1/4] target/ppc: Add new hflags to support BHRB Glenn Miles
2023-09-12 20:00 ` Glenn Miles
2023-09-12 20:17 ` Cédric Le Goater
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=61e8d5bb7aa50c3fc16caf29a8ff7dce@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=groug@kaod.org \
--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).