From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] perf/x86/amd: Reject branch stack for IBS events
Date: Mon, 27 Nov 2023 11:32:57 -0300 [thread overview]
Message-ID: <ZWSombzfCkxHc7lC@kernel.org> (raw)
In-Reply-To: <3d70b52f-2042-328c-6dc7-37fcbb3510a2@amd.com>
Em Fri, Nov 24, 2023 at 09:30:37AM +0530, Ravi Bangoria escreveu:
> On 23-Nov-23 8:15 PM, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jun 06, 2023 at 10:08:43AM +0530, Ravi Bangoria escreveu:
> >> On 03-Jun-23 1:15 AM, Namhyung Kim wrote:
> >>> The AMD IBS PMU doesn't handle branch stacks, so it should not accept
> >>> events with brstack.
> >>>
> >>> Cc: Ravi Bangoria <ravi.bangoria@amd.com>
> >>> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> >>
> >> Reviewed-by: Ravi Bangoria <ravi.bangoria@amd.com>
> >
> > It seems this patch was not merged, can you please check?
>
> Right. And it does not apply cleanly on peterz/queue.git/perf/core, since
> surrounding code has changed.
Can you please refresh it if PeterZ has nothing against?
- Arnaldo
next prev parent reply other threads:[~2023-11-27 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 19:45 [PATCH] perf/x86/amd: Reject branch stack for IBS events Namhyung Kim
2023-06-06 4:38 ` Ravi Bangoria
2023-11-23 14:45 ` Arnaldo Carvalho de Melo
2023-11-24 4:00 ` Ravi Bangoria
2023-11-27 14:32 ` Arnaldo Carvalho de Melo [this message]
2023-11-30 6:28 ` Ravi Bangoria
2023-11-30 13:03 ` Arnaldo Carvalho de Melo
2023-12-01 20:23 ` Namhyung Kim
2023-12-01 20:31 ` Arnaldo Carvalho de Melo
2023-12-04 19:37 ` 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=ZWSombzfCkxHc7lC@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.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