From: Namhyung Kim <namhyung@kernel.org>
To: "Wang, Weilin" <weilin.wang@intel.com>
Cc: Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Taylor, Perry" <perry.taylor@intel.com>,
"Alt, Samantha" <samantha.alt@intel.com>,
"Biggers, Caleb" <caleb.biggers@intel.com>
Subject: Re: [RFC PATCH v14 0/8] TPEBS counting mode support
Date: Thu, 27 Jun 2024 13:32:23 -0700 [thread overview]
Message-ID: <Zn3MV8lCSHLEEXDG@google.com> (raw)
In-Reply-To: <CO6PR11MB563505F0D97C0E2D5949F583EED62@CO6PR11MB5635.namprd11.prod.outlook.com>
On Wed, Jun 26, 2024 at 06:17:22PM +0000, Wang, Weilin wrote:
>
>
> > -----Original Message-----
> > From: Namhyung Kim <namhyung@kernel.org>
> > Sent: Wednesday, June 26, 2024 10:59 AM
> > To: Wang, Weilin <weilin.wang@intel.com>
> > Cc: Ian Rogers <irogers@google.com>; Arnaldo Carvalho de Melo
> > <acme@kernel.org>; Peter Zijlstra <peterz@infradead.org>; Ingo Molnar
> > <mingo@redhat.com>; Alexander Shishkin
> > <alexander.shishkin@linux.intel.com>; Jiri Olsa <jolsa@kernel.org>; Hunter,
> > Adrian <adrian.hunter@intel.com>; Kan Liang <kan.liang@linux.intel.com>;
> > linux-perf-users@vger.kernel.org; linux-kernel@vger.kernel.org; Taylor, Perry
> > <perry.taylor@intel.com>; Alt, Samantha <samantha.alt@intel.com>; Biggers,
> > Caleb <caleb.biggers@intel.com>
> > Subject: Re: [RFC PATCH v14 0/8] TPEBS counting mode support
> >
> > On Mon, Jun 24, 2024 at 06:20:16PM -0400, weilin.wang@intel.com wrote:
> > > From: Weilin Wang <weilin.wang@intel.com>
> > >
> > > Changes in v14:
> > > - Fix the python import test failure. We cannot support PYTHON_PERF
> > because it
> > > will trigger a chain of dependency issues if we add intel-tpebs.c to it. So,
> > > only enable tpebs functions in evsel and evlist when PYTHON_PERF is not
> > > defined.
> >
> > I think it's easier if we have Ian's python build cleanup first.
> >
> > https://lore.kernel.org/linux-perf-users/20240625214117.953777-1-
> > irogers@google.com
> >
> > Let me take a look at it..
>
> Ok, I will hold the cmd option name update until we conclude on this one.
> Thanks a lot!
Please take a look at the current perf-tools-next branch.
Thanks,
Namhyung
next prev parent reply other threads:[~2024-06-27 20:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 22:20 [RFC PATCH v14 0/8] TPEBS counting mode support weilin.wang
2024-06-24 22:20 ` [RFC PATCH v14 1/8] perf parse-events: Add a retirement latency modifier weilin.wang
2024-06-24 22:20 ` [RFC PATCH v14 2/8] perf data: Allow to use given fd in data->file.fd weilin.wang
2024-06-24 22:20 ` [RFC PATCH v14 3/8] perf stat: Fork and launch perf record when perf stat needs to get retire latency value for a metric weilin.wang
2024-06-24 22:20 ` [RFC PATCH v14 4/8] perf stat: Plugin retire_lat value from sampled data to evsel weilin.wang
2024-06-24 22:20 ` [RFC PATCH v14 5/8] perf vendor events intel: Add MTL metric json files weilin.wang
2024-06-24 22:20 ` [RFC PATCH v14 6/8] perf stat: Add command line option for enabling tpebs recording weilin.wang
2024-06-26 17:55 ` Namhyung Kim
2024-06-26 18:14 ` Wang, Weilin
2024-06-24 22:20 ` [RFC PATCH v14 7/8] perf Document: Add TPEBS to Documents weilin.wang
2024-06-24 22:20 ` [RFC PATCH v14 8/8] perf test: Add test for Intel TPEBS counting mode weilin.wang
2024-06-26 17:58 ` [RFC PATCH v14 0/8] TPEBS counting mode support Namhyung Kim
2024-06-26 18:17 ` Wang, Weilin
2024-06-27 20:32 ` Namhyung Kim [this message]
2024-06-30 5:12 ` Wang, Weilin
2024-07-02 4:27 ` Wang, Weilin
2024-07-02 18:59 ` Namhyung Kim
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=Zn3MV8lCSHLEEXDG@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=weilin.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.