Linux Perf Users
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kan@google.com, Liang@google.com, kan.liang@linux.intel.com,
	James Clark <james.clark@linaro.org>,
	Weilin Wang <weilin.wang@intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] perf evsel: Add per-thread warning for EOPNOTSUPP open failues
Date: Mon, 12 May 2025 13:46:32 -0300	[thread overview]
Message-ID: <aCIl6G9yUCE8ySlp@x1> (raw)
In-Reply-To: <20250412004704.2297939-1-irogers@google.com>

On Fri, Apr 11, 2025 at 05:47:03PM -0700, Ian Rogers wrote:
> The mrvl_ddr_pmu will return EOPNOTSUPP if opened in per-thread
> mode. Give a warning for this similar to EINVAL. Doing this better
> supports metric testing with limited permissions when the mrvl_ddr_pmu
> is present, as the failure to open causes the test to skip and not
> fail.


Thanks, applied to perf-tools-next,

- Arnaldo

      parent reply	other threads:[~2025-05-12 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-12  0:47 [PATCH v1 1/2] perf evsel: Add per-thread warning for EOPNOTSUPP open failues Ian Rogers
2025-04-12  0:47 ` [PATCH v1 2/2] perf tests metrics: Permission related fixes Ian Rogers
2025-05-12 16:46 ` Arnaldo Carvalho de Melo [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=aCIl6G9yUCE8ySlp@x1 \
    --to=acme@kernel.org \
    --cc=Kan@google.com \
    --cc=Liang@google.com \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox