All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	Thomas Richter <tmricht@linux.ibm.com>,
	James Clark <james.clark@arm.com>
Subject: Re: [PATCH v2] perf test: Simplify object code reading test
Date: Wed, 8 Nov 2023 17:10:17 -0300	[thread overview]
Message-ID: <ZUvrKT0TjGeSi98K@kernel.org> (raw)
In-Reply-To: <c1aedc2e-e51b-4b17-a05e-cd347f56d83b@intel.com>

Em Mon, Nov 06, 2023 at 10:15:07AM +0200, Adrian Hunter escreveu:
> On 3/11/23 21:55, Namhyung Kim wrote:
> > It tries cycles (or cpu-clock on s390) event with exclude_kernel bit to
> > open.  But other arch on a VM can fail with the hardware event and need
> > to fallback to the software event in the same way.
> > 
> > So let's get rid of the cpuid check and use generic fallback mechanism
> > using an array of event candidates.  Now event in the odd index excludes
> > the kernel so use that for the return value.
> > 
> > Cc: Thomas Richter <tmricht@linux.ibm.com>
> > Tested-by: James Clark <james.clark@arm.com>
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> 
> Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>

Thanks, applied to perf-tools-next.

- Arnaldo


      reply	other threads:[~2023-11-08 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 19:55 [PATCH v2] perf test: Simplify object code reading test Namhyung Kim
2023-11-06  8:15 ` Adrian Hunter
2023-11-08 20:10   ` 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=ZUvrKT0TjGeSi98K@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tmricht@linux.ibm.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.