public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@google.com>,
	Sandipan Das <sandipan.das@amd.com>
Subject: Re: [PATCH v5 0/2] perf: Relax privilege restriction on AMD IBS
Date: Thu, 7 Nov 2024 22:47:50 -0800	[thread overview]
Message-ID: <Zy20Fm7sVbfReWBE@google.com> (raw)
In-Reply-To: <d5187836-3c1e-4bdb-90a2-779d3c1f086d@amd.com>

On Wed, Oct 30, 2024 at 03:22:02PM +0530, Ravi Bangoria wrote:
> On 29-Oct-24 1:31 AM, Namhyung Kim wrote:
> > Hello,
> > 
> > This is v5 to allow AMD IBS to regular users on the default settings
> > where kernel-level profiling is disabled (perf_event_paranoid=2).
> > Currently AMD IBS doesn't allow any kind of exclusion in the event
> > attribute.  But users needs to set attr.exclude_kernel to open an
> > event on such an environment.
> 
> For the series:
> 
> Reviewed-and-tested-by: Ravi Bangoria <ravi.bangoria@amd.com>

Thanks for your review!

Peter and Ingo, can you please take a look at this?

Thanks,
Namhyung


      reply	other threads:[~2024-11-08  6:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 20:01 [PATCH v5 0/2] perf: Relax privilege restriction on AMD IBS Namhyung Kim
2024-10-28 20:01 ` [PATCH v5 1/2] perf/core: Export perf_exclude_event() Namhyung Kim
2024-10-28 20:01 ` [PATCH v5 2/2] perf/x86: Relax privilege filter restriction on AMD IBS Namhyung Kim
2024-10-30  9:52 ` [PATCH v5 0/2] perf: Relax privilege " Ravi Bangoria
2024-11-08  6:47   ` Namhyung Kim [this message]

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=Zy20Fm7sVbfReWBE@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    --cc=sandipan.das@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