From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
James Morse <james.morse@arm.com>, Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Oliver Upton <oliver.upton@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
kvmarm@lists.cs.columbia.edu, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/7] arm64/sysreg: Convert SPE registers to automatic generation
Date: Thu, 20 Oct 2022 15:33:40 +0100 [thread overview]
Message-ID: <Y1FcRNhFpZxZ7AMx@sirena.org.uk> (raw)
In-Reply-To: <20220825-arm-spe-v8-7-v2-3-e37322d68ac0@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
On Wed, Oct 19, 2022 at 02:11:26PM -0500, Rob Herring wrote:
> Convert all the SPE register defines to automatic generation. No
> functional changes.
>
> New registers and fields for SPEv1.2 are added with the conversion.
>
> Some of the PMBSR MSS field defines are kept as the automatic generation
> has no way to create multiple names for the same register bits. The
> meaning of the MSS field depends on other bits.
A few small things below from checking against DDI0487I.a, nothing
major:
> +Sysreg PMSCR_EL1 3 0 9 9 0
> +Res0 63:8
> +Field 7:6 PCT
Given the potential multiple meanings depending on both integration and
runtime configuration representing this as a field seems sensible.
> +Sysreg PMSNEVFR_EL1 3 0 9 9 1
> +Field 63:0 E
> +EndSysreg
While this does look rather different to the spec it does appear to be a
sensible interpretation - the intent is clearly to have a mask of
feature bits.
> +Sysreg PMSIDR_EL1 3 0 9 9 7
> +Field 23:20 FORMAT
> +Field 19:16 COUNTSIZE
> +Field 15:12 MAXSIZE
> +Field 11:8 INTERVAL
These should really be enums.
> +Sysreg PMBLIMITR_EL1 3 0 9 10 0
> +Enum 2:1 FM
> + 0b0000 STOP_IRQ
> +EndEnum
DDI0487I.a also defines
0b01 DISCARD
from FEAT_SPEv1p2. Also this is a two bit field so 0b00 would be a bit
better.
> +Sysreg PMBSR_EL1 3 0 9 10 3
> +Res0 63:32
> +Enum 31:26 EC
> + 0b000000 BUF
> + 0b100100 FAULT_S1
> + 0b100101 FAULT_S2
> +EndEnum
DDI0487I.a also has
0b011110 FAULT_GPC
0b011111 IMP_DEF
(the former from FEAT_RME).
> +Sysreg PMBIDR_EL1 3 0 9 10 7
> +Res0 63:12
> +Field 11:8 EA
This looks like it should be described as an enum.
> +Field 3:0 ALIGN
This could potentially also be an enum.
> +Sysreg PMSCR_EL2 3 4 9 9 0
> +Res0 63:8
> +Field 7:6 PCT
This lookslike it should be an enum.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-20 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 19:11 [PATCH v2 0/7] perf: Arm SPEv1.2 support Rob Herring
2022-10-19 19:11 ` [PATCH v2 1/7] perf: arm_spe: Use feature numbering for PMSEVFR_EL1 defines Rob Herring
2022-10-19 19:11 ` [PATCH v2 2/7] arm64: Drop SYS_ from SPE register defines Rob Herring
2022-10-19 19:11 ` [PATCH v2 3/7] arm64/sysreg: Convert SPE registers to automatic generation Rob Herring
2022-10-20 14:33 ` Mark Brown [this message]
2022-10-20 19:51 ` Rob Herring
2022-10-21 10:44 ` Mark Brown
2022-10-19 19:11 ` [PATCH v2 4/7] perf: arm_spe: Drop BIT() and use FIELD_GET/PREP accessors Rob Herring
2022-10-19 19:11 ` [PATCH v2 5/7] perf: arm_spe: Support new SPEv1.2/v8.7 'not taken' event Rob Herring
2022-10-19 19:11 ` [PATCH v2 6/7] perf: Add perf_event_attr::config3 Rob Herring
2022-10-19 19:11 ` [PATCH v2 7/7] perf: arm_spe: Add support for SPEv1.2 inverted event filtering Rob Herring
2022-11-04 11:30 ` [PATCH v2 0/7] perf: Arm SPEv1.2 support James Clark
2022-11-04 14:47 ` 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=Y1FcRNhFpZxZ7AMx@sirena.org.uk \
--to=broonie@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandru.elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jolsa@kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=suzuki.poulose@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
all inboxes | Powered by JetHome®