linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf, script: Minimize "not reaching sample" for brstackinsn
Date: Wed, 28 Feb 2024 15:33:23 -0800	[thread overview]
Message-ID: <Zd_Cw6QeuGx-Dblm@tassilo> (raw)
In-Reply-To: <ceb7d039-5088-45e7-b7ea-8f2056f5f7dc@intel.com>

> > There are two common cases where the message is bogus:
> > - The LBR only logs taken branches, but the branch might be a
> > conditional branch that is not taken (that is the most common
> > case actually)
> 
> How do you know it is not a taken branch that missed the LBR update?

I don't, but the not taken case is totally valid (and also common)
so it doesn't make sense to have a mere sanity check make a common
case unusable.

> 
> > - The LBR sampling uses a filter ignoring some branches,
> > but the perf script check checks for all branches.
> 
> Not understanding this case.  Do you mean you expect not to reach
> the sample, so there is no point printing the message?

If the LBR is e.g. filtered on far branches it makes no sense to 
check for non far branches. There are lot of filtering cases here which
would be very complicated to handle for a mere sanity check,
so the best way is to not do the bogus sanity check.

-Andi

  reply	other threads:[~2024-02-28 23:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 18:39 [PATCH] perf, script: Minimize "not reaching sample" for brstackinsn Andi Kleen
2024-02-28 11:04 ` Adrian Hunter
2024-02-28 23:33   ` Andi Kleen [this message]
2024-02-29  7:37     ` Adrian Hunter

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=Zd_Cw6QeuGx-Dblm@tassilo \
    --to=ak@linux.intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=linux-perf-users@vger.kernel.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).