linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@redhat.com>
Cc: linux-perf-users@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v8] libperf: Add arm64 support to perf_mmap__read_self()
Date: Tue, 14 Dec 2021 16:08:35 -0600	[thread overview]
Message-ID: <CAL_Jsq+F1x-spV4hatHLFmFHo8e4U-gf8goz69_MPihfPirTXw@mail.gmail.com> (raw)
In-Reply-To: <20211214215630.4025090-1-robh@kernel.org>

On Tue, Dec 14, 2021 at 3:56 PM Rob Herring <robh@kernel.org> wrote:
>
> Add the arm64 variants for read_perf_counter() and read_timestamp().
> Unfortunately the counter number is encoded into the instruction, so the
> code is a bit verbose to enumerate all possible counters.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> v8:
>  - Set attr.config1 to request user access on arm64

Hit send a bit too quick. The kernel side[1] has now been applied by
Will, so hopefully the libperf enabling can land in 5.17 too.

Rob

[1] https://lore.kernel.org/all/163948145564.2060329.17036263207999776606.b4-ty@kernel.org/

  reply	other threads:[~2021-12-14 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 21:56 [PATCH v8] libperf: Add arm64 support to perf_mmap__read_self() Rob Herring
2021-12-14 22:08 ` Rob Herring [this message]
2022-01-11 22:43 ` Rob Herring
2022-01-12 18:00 ` Masayoshi Mizuma
     [not found] ` <CAP-5=fWkFhHZhPQ1WUTwJjMijBOJS6GMwG1UAo0GBsuS2G6Q8g@mail.gmail.com>
2022-01-14 14:49   ` Rob Herring

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=CAL_Jsq+F1x-spV4hatHLFmFHo8e4U-gf8goz69_MPihfPirTXw@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.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 \
    /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;
as well as URLs for NNTP newsgroup(s).