From: Mark Brown <broonie@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, leo.yan@linaro.org, john.garry@huawei.com,
catalin.marinas@arm.com, will@kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Mark Rutland <mark.rutland@arm.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] arm64/sve: Add Perf extensions documentation
Date: Thu, 1 Sep 2022 14:33:35 +0100 [thread overview]
Message-ID: <YxC0r6RCffBXXllT@sirena.org.uk> (raw)
In-Reply-To: <20220901132658.1024635-3-james.clark@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 169 bytes --]
On Thu, Sep 01, 2022 at 02:26:58PM +0100, James Clark wrote:
> Document that the VG register is available in Perf samples
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-01 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:26 [PATCH v3 0/2] perf: arm64: Kernel support for Dwarf unwinding through SVE functions James Clark
2022-09-01 13:26 ` [PATCH v3 1/2] perf: arm64: Add SVE vector granule register to user regs James Clark
2022-09-01 13:26 ` [PATCH v3 2/2] arm64/sve: Add Perf extensions documentation James Clark
2022-09-01 13:33 ` Mark Brown [this message]
2022-09-20 10:28 ` James Clark
2022-09-22 14:04 ` [PATCH v3 0/2] perf: arm64: Kernel support for Dwarf unwinding through SVE functions Will Deacon
2022-09-22 14:31 ` James Clark
2022-09-22 20:57 ` Will Deacon
2022-09-22 20:33 ` Will Deacon
2022-09-23 9:32 ` James Clark
2022-09-23 12:36 ` Will Deacon
2022-09-23 12:43 ` James Clark
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=YxC0r6RCffBXXllT@sirena.org.uk \
--to=broonie@kernel.org \
--cc=acme@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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).