linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH V2 0/2] perf parse-events: Do not break up AUX event group
Date: Mon,  8 May 2023 12:39:50 +0300	[thread overview]
Message-ID: <20230508093952.27482-1-adrian.hunter@intel.com> (raw)

Hi

Here is a fix needed in v6.4, but dependent on Ian's patch
"perf evsel: Modify group pmu name for software events", refer:

https://lore.kernel.org/lkml/20230502223851.2234828-20-irogers@google.com/

There is also a test amendment to test the AUX event group fix for
Intel PT.


Changes in V2:

   Add an Intel PT test amendment for the AUX event group fix
   Change AUX event group fix as suggested by Ian


Adrian Hunter (2):
      perf test: test_intel_pt.sh: Test sample mode with named PMU
      perf parse-events: Do not break up AUX event group

 tools/perf/tests/shell/test_intel_pt.sh | 7 +++++++
 tools/perf/util/evsel.c                 | 9 +++------
 2 files changed, 10 insertions(+), 6 deletions(-)


Regards
Adrian

             reply	other threads:[~2023-05-08  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  9:39 Adrian Hunter [this message]
2023-05-08  9:39 ` [PATCH V2 1/2] perf test: test_intel_pt.sh: Test sample mode with event with PMU name Adrian Hunter
2023-05-08  9:39 ` [PATCH V2 2/2] perf parse-events: Do not break up AUX event group Adrian Hunter
2023-05-08 22:18   ` Ian Rogers
2023-05-10 17:13 ` [PATCH V2 0/2] " Arnaldo Carvalho de Melo
2023-05-10 17:38   ` Adrian Hunter
2023-05-10 17:15 ` Arnaldo Carvalho de Melo

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=20230508093952.27482-1-adrian.hunter@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@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).