public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Stephane Eranian <eranian@google.com>, linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, kan.liang@intel.com, ak@linux.intel.com,
	acme@redhat.com, namhyung@kernel.org, irogers@google.com
Subject: Re: [PATCH] perf/x86/intel/lbr: fix branch type encoding
Date: Thu, 11 Aug 2022 08:23:31 -0400	[thread overview]
Message-ID: <0267c94e-7989-ca92-4175-d820d1d63a0c@linux.intel.com> (raw)
In-Reply-To: <20220810210656.2799243-1-eranian@google.com>



On 2022-08-10 5:06 p.m., Stephane Eranian wrote:
> With architected LBR, the procesosr can record the type of each sampled taken
> branch. The type is encoded in 4-bit field in the LBR_INFO MSR of each entry.
> 
> The branch type must then extracted and saved in the perf_branch_entry in the
> perf_events sampling buffer. With the current code, the raw Intel encoding of
> the branch is exported to user tools. 

In the intel_pmu_lbr_filter(), the raw encoding will be converted into
the X86_BR_* format via arch_lbr_br_type_map[]. Then the
common_branch_type() will convert the X86_BR_* format to the generic
PERF_BR_* type and expose to user tools.

I double check the existing arch_lbr_br_type_map[] and branch_map[].
They should generate the same PERF_BR_* type as your arch_lbr_type_map[].

Is there a test case which I can use to reproduce the problem?

Thanks,
Kan

> Yet tools, such as perf, expected the
> branch type to be encoded using perf_events branch type enum
> (see tools/perf/util/branch.c). As a result of the discrepancy, the output of
> perf report -D shows bogus branch types.
> 
> Fix the problem by converting the Intel raw encoding into the perf_events
> branch type enum values. With that in place and with no changes to the tools,
> the branch types are now reported properly.
> 
> Signed-off-by: Stephane Eranian <eranian@google.com>
> ---
>  arch/x86/events/intel/lbr.c | 35 ++++++++++++++++++++++++++++++++---
>  1 file changed, 32 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/events/intel/lbr.c b/arch/x86/events/intel/lbr.c
> index 4f70fb6c2c1e..ef63d4d46b50 100644
> --- a/arch/x86/events/intel/lbr.c
> +++ b/arch/x86/events/intel/lbr.c
> @@ -894,9 +894,23 @@ static DEFINE_STATIC_KEY_FALSE(x86_lbr_mispred);
>  static DEFINE_STATIC_KEY_FALSE(x86_lbr_cycles);
>  static DEFINE_STATIC_KEY_FALSE(x86_lbr_type);
>  
> -static __always_inline int get_lbr_br_type(u64 info)
> +/*
> + * Array index encodes IA32_LBR_x_INFO Branch Type Encodings
> + * as per Intel SDM Vol3b Branch Types section
> + */
> +static const int arch_lbr_type_map[]={
> +	[0] = PERF_BR_COND,
> +	[1] = PERF_BR_IND,
> +	[2] = PERF_BR_UNCOND,
> +	[3] = PERF_BR_IND_CALL,
> +	[4] = PERF_BR_CALL,
> +	[5] = PERF_BR_RET,
> +};
> +#define ARCH_LBR_TYPE_COUNT ARRAY_SIZE(arch_lbr_type_map)
> +
> +static __always_inline u16 get_lbr_br_type(u64 info)
>  {
> -	int type = 0;
> +	u16 type = 0;
>  
>  	if (static_branch_likely(&x86_lbr_type))
>  		type = (info & LBR_INFO_BR_TYPE) >> LBR_INFO_BR_TYPE_OFFSET;
> @@ -904,6 +918,21 @@ static __always_inline int get_lbr_br_type(u64 info)
>  	return type;
>  }
>  
> +/*
> + * The kernel cannot expose raw Intel branch type encodings because they are
> + * not generic. Instead, the function below  maps the encoding to the
> + * perf_events user visible branch types.
> + */
> +static __always_inline int get_lbr_br_type_mapping(u64 info)
> +{
> +	if (static_branch_likely(&x86_lbr_type)) {
> +		u16 raw_type = get_lbr_br_type(info);
> +		if (raw_type < ARCH_LBR_TYPE_COUNT)
> +			return arch_lbr_type_map[raw_type];
> +	}
> +	return PERF_BR_UNKNOWN;
> +}
> +
>  static __always_inline bool get_lbr_mispred(u64 info)
>  {
>  	bool mispred = 0;
> @@ -957,7 +986,7 @@ static void intel_pmu_store_lbr(struct cpu_hw_events *cpuc,
>  		e->in_tx	= !!(info & LBR_INFO_IN_TX);
>  		e->abort	= !!(info & LBR_INFO_ABORT);
>  		e->cycles	= get_lbr_cycles(info);
> -		e->type		= get_lbr_br_type(info);
> +		e->type		= get_lbr_br_type_mapping(info);
>  	}
>  
>  	cpuc->lbr_stack.nr = i;

  reply	other threads:[~2022-08-11 12:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 21:06 [PATCH] perf/x86/intel/lbr: fix branch type encoding Stephane Eranian
2022-08-11 12:23 ` Liang, Kan [this message]
2022-08-11 14:17   ` Stephane Eranian
2022-08-11 14:41     ` Liang, Kan
2022-08-11 15:28       ` Stephane Eranian
2022-08-11 15:33         ` Stephane Eranian
2022-08-11 15:56           ` Liang, Kan
2022-08-12  8:16             ` Andi Kleen
2022-08-14 19:37               ` Liang, Kan
2022-08-15 19:45                 ` Stephane Eranian
2022-08-15 20:39                   ` Liang, Kan
2022-08-12 19:35             ` Arnaldo Carvalho de Melo
2022-08-14 19:39               ` Liang, Kan
2022-08-11 20:21           ` Andi Kleen

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=0267c94e-7989-ca92-4175-d820d1d63a0c@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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