From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: Disha Goel <disgoel@linux.ibm.com>,
Namhyung Kim <namhyung@kernel.org>,
James Clark <james.clark@arm.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
Kajol Jain <kjain@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Disha Goel <disgoel@linux.vnet.ibm.com>
Subject: Re: [PATCH] perf vendor events: Update datasource event name to fix duplicate events
Date: Mon, 4 Dec 2023 17:00:40 -0300 [thread overview]
Message-ID: <ZW4v6OpQKGC7bHi2@kernel.org> (raw)
In-Reply-To: <87E3CA3F-77D0-4A99-8575-C85544D207E1@linux.vnet.ibm.com>
Em Sun, Dec 03, 2023 at 09:27:25PM +0530, Athira Rajeev escreveu:
> > On 29-Nov-2023, at 10:51 AM, Athira Rajeev <atrajeev@linux.vnet.ibm.com> wrote:
> >> On 27-Nov-2023, at 5:32 PM, Disha Goel <disgoel@linux.ibm.com> wrote:
> >>> Fixes: fc1435807533 ("perf vendor events power10: Update JSON/events")
> >>> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
> >> I have tested the patch on Power10 machine. Perf list works correctly without any segfault now.
> >> # ./perf list
> >> List of pre-defined events (to be used in -e or -M):
> >> branch-instructions OR branches [Hardware event]
> >> branch-misses [Hardware event]
> >> Tested-by: Disha Goel <disgoel@linux.ibm.com>
> > Thanks Disha for testing
> Hi Arnaldo,
> Can we get this pulled in if the patch looks good ?
Thanks, applied to perf-tools-next.
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: Ian Rogers <irogers@google.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Kajol Jain <kjain@linux.ibm.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Disha Goel <disgoel@linux.vnet.ibm.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
James Clark <james.clark@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Disha Goel <disgoel@linux.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] perf vendor events: Update datasource event name to fix duplicate events
Date: Mon, 4 Dec 2023 17:00:40 -0300 [thread overview]
Message-ID: <ZW4v6OpQKGC7bHi2@kernel.org> (raw)
In-Reply-To: <87E3CA3F-77D0-4A99-8575-C85544D207E1@linux.vnet.ibm.com>
Em Sun, Dec 03, 2023 at 09:27:25PM +0530, Athira Rajeev escreveu:
> > On 29-Nov-2023, at 10:51 AM, Athira Rajeev <atrajeev@linux.vnet.ibm.com> wrote:
> >> On 27-Nov-2023, at 5:32 PM, Disha Goel <disgoel@linux.ibm.com> wrote:
> >>> Fixes: fc1435807533 ("perf vendor events power10: Update JSON/events")
> >>> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
> >> I have tested the patch on Power10 machine. Perf list works correctly without any segfault now.
> >> # ./perf list
> >> List of pre-defined events (to be used in -e or -M):
> >> branch-instructions OR branches [Hardware event]
> >> branch-misses [Hardware event]
> >> Tested-by: Disha Goel <disgoel@linux.ibm.com>
> > Thanks Disha for testing
> Hi Arnaldo,
> Can we get this pulled in if the patch looks good ?
Thanks, applied to perf-tools-next.
- Arnaldo
next prev parent reply other threads:[~2023-12-04 20:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 16:01 [PATCH] perf vendor events: Update datasource event name to fix duplicate events Athira Rajeev
2023-11-23 16:01 ` Athira Rajeev
2023-11-27 12:02 ` Disha Goel
2023-11-27 12:02 ` Disha Goel
2023-11-29 5:21 ` Athira Rajeev
2023-11-29 5:21 ` Athira Rajeev
2023-12-03 15:57 ` Athira Rajeev
2023-12-03 15:57 ` Athira Rajeev
2023-12-04 20:00 ` Arnaldo Carvalho de Melo [this message]
2023-12-04 20:00 ` Arnaldo Carvalho de Melo
2023-12-04 20:12 ` Ian Rogers
2023-12-04 20:12 ` Ian Rogers
2023-12-04 20:20 ` Arnaldo Carvalho de Melo
2023-12-04 20:20 ` Arnaldo Carvalho de Melo
2023-12-04 20:22 ` Arnaldo Carvalho de Melo
2023-12-04 20:22 ` Arnaldo Carvalho de Melo
2023-12-04 21:13 ` Ian Rogers
2023-12-04 21:13 ` Ian Rogers
2023-12-05 7:16 ` Athira Rajeev
2023-12-05 7:16 ` Athira Rajeev
2023-12-05 7:14 ` Athira Rajeev
2023-12-05 7:14 ` Athira Rajeev
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=ZW4v6OpQKGC7bHi2@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--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 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.