public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	Ravi Bangoria <ravi.bangoria@amd.com>,
	Mark Rutland <mark.rutland@arm.com>,
	James Clark <james.clark@arm.com>,
	Kajol Jain <kjain@linux.ibm.com>,
	Thomas Richter <tmricht@linux.ibm.com>,
	Atish Patra <atishp@atishpatra.org>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Mingwei Zhang <mizhang@google.com>
Subject: Re: [PATCHSET 0/8] perf tools: Do not set attr.exclude_guest by default (v4)
Date: Tue, 1 Oct 2024 14:19:13 -0700	[thread overview]
Message-ID: <ZvxnUfgEiHY-Zmr4@google.com> (raw)
In-Reply-To: <4ce19789-eea1-4e5e-9269-13bd78d846c2@linux.intel.com>

On Tue, Oct 01, 2024 at 01:46:36PM -0400, Liang, Kan wrote:
> 
> 
> On 2024-09-30 8:20 p.m., Namhyung Kim wrote:
> > Hello,
> > 
> > I found perf tools set exclude_guest bit inconsistently.  It used to
> > set the bit but now the default event for perf record doesn't.  So I'm
> > wondering why we want the bit in the first place.
> > 
> > Actually it's not good for PMUs don't support any exclusion like AMD
> > IBS because it disables new features after the exclude_guest due to
> > the missing feature detection logic.
> > 
> > v4 changes)
> > 
> >  * handle EOPNOTSUPP error in compatible way  (Kan)
> >  * drop --exclude-guest option in perf stat
> >  * not to separate exclude_hv fallback
> >  * rename to exclude_GH_default  (Kan)
> >  * drop the RFC from the subject
> > 
> > v3) https://lore.kernel.org/lkml/20240905202426.2690105-1-namhyung@kernel.org/
> > 
> >  * move exclude_guest fallback to the front
> >  * fix precise_max handling on AMD
> >  * simplify the default event for perf record
> > 
> > v2) https://lore.kernel.org/lkml/20240904064131.2377873-1-namhyung@kernel.org/
> > 
> >  * update the missing feature detection logic
> >  * separate exclude_hv fallback
> >  * add new fallback for exclude_guest
> > 
> > v1) https://lore.kernel.org/lkml/20240902014621.2002343-1-namhyung@kernel.org/
> > 
> > AFAIK it doesn't matter for the most cases but perf kvm.  If users
> > need to set the bit, they can still use :H modifier.  For vPMU pass-
> > through or Apple M1, it'd add the exclude_guest during the fallback
> > logic.
> > 
> > Also the kernel feature detection logic should be separated from the
> > exclude bit tests since it depends on the PMU implementation rather
> > than the core kernel features.  So I changed it to use a software
> > event for the detection and factor out some hw-specific checks.
> > 
> > The code is available at 'perf/exclude-v4' branch in
> > git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
> > 
> > Thanks,
> > Namhyung
> > 
> > 
> > Namhyung Kim (8):
> >   perf tools: Add fallback for exclude_guest
> >   perf tools: Don't set attr.exclude_guest by default
> >   perf tools: Simplify evsel__add_modifier()
> >   perf tools: Do not set exclude_guest for precise_ip
> >   perf tools: Detect missing kernel features properly
> >   perf tools: Move x86__is_amd_cpu() to util/env.c
> >   perf tools: Check fallback error and order
> >   perf record: Just use "cycles:P" as the default event
> > 
> 
> The patch set looks good to me.
> 
> Acked-by: Kan Liang <kan.liang@linux.intel.com>

Thanks for your review!
Namhyung


  reply	other threads:[~2024-10-01 21:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01  0:20 [PATCHSET 0/8] perf tools: Do not set attr.exclude_guest by default (v4) Namhyung Kim
2024-10-01  0:20 ` [PATCH 1/8] perf tools: Add fallback for exclude_guest Namhyung Kim
2024-10-01 17:41   ` Ian Rogers
2024-10-01  0:20 ` [PATCH 2/8] perf tools: Don't set attr.exclude_guest by default Namhyung Kim
2024-10-01 17:43   ` Ian Rogers
2024-10-01  0:20 ` [PATCH 3/8] perf tools: Simplify evsel__add_modifier() Namhyung Kim
2024-10-01 17:44   ` Ian Rogers
2024-10-01  0:20 ` [PATCH 4/8] perf tools: Do not set exclude_guest for precise_ip Namhyung Kim
2024-10-01 17:46   ` Ian Rogers
2024-10-01  0:20 ` [PATCH 5/8] perf tools: Detect missing kernel features properly Namhyung Kim
2024-10-01 17:53   ` Ian Rogers
2024-10-01 21:32     ` Namhyung Kim
2024-10-15  4:19   ` Ravi Bangoria
2024-10-16  4:49     ` Namhyung Kim
2024-10-01  0:20 ` [PATCH 6/8] perf tools: Move x86__is_amd_cpu() to util/env.c Namhyung Kim
2024-10-01 16:03   ` Liang, Kan
2024-10-01 22:39     ` Namhyung Kim
2024-10-01  0:20 ` [PATCH 7/8] perf tools: Check fallback error and order Namhyung Kim
2024-10-01 18:00   ` Ian Rogers
2024-10-01 21:36     ` Namhyung Kim
2024-10-01 22:21       ` Ian Rogers
2024-10-03 17:06         ` Namhyung Kim
2024-10-03 17:32           ` Ian Rogers
2024-10-03 22:38             ` Namhyung Kim
2024-10-14 19:22               ` Namhyung Kim
2024-10-15  4:21                 ` Ravi Bangoria
2024-10-16  4:33                   ` Namhyung Kim
2024-10-16  4:47                 ` Ian Rogers
2024-10-01  0:20 ` [PATCH 8/8] perf record: Just use "cycles:P" as the default event Namhyung Kim
2024-10-01 18:00   ` Ian Rogers
2024-10-01 17:46 ` [PATCHSET 0/8] perf tools: Do not set attr.exclude_guest by default (v4) Liang, Kan
2024-10-01 21:19   ` Namhyung Kim [this message]
2024-10-02  9:49 ` James Clark
2024-10-02 18:29   ` Namhyung Kim
2024-10-04 15:40     ` James Clark
2024-10-04 19:17       ` Namhyung Kim
2024-10-15  4:25 ` Ravi Bangoria

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=ZvxnUfgEiHY-Zmr4@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=atishp@atishpatra.org \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=mizhang@google.com \
    --cc=palmer@rivosinc.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    --cc=tmricht@linux.ibm.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