linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Shuah Khan <shuah@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Joey Gouly <joey.gouly@arm.com>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: arm64: Correct feature test for S1PIE in get-reg-list
Date: Fri, 02 Aug 2024 14:36:14 +0100	[thread overview]
Message-ID: <86a5hv11yp.wl-maz@kernel.org> (raw)
In-Reply-To: <7b9b3ef4-66da-4314-8265-5947998758e9@sirena.org.uk>

On Fri, 02 Aug 2024 13:43:03 +0100,
Mark Brown <broonie@kernel.org> wrote:
> 
> [1  <text/plain; us-ascii (7bit)>]
> On Fri, Aug 02, 2024 at 10:00:28AM +0100, Marc Zyngier wrote:
> 
> > Also, the test predates the generated stuff by some margin.
> 
> Yeah, there were still defines in the main kernel source that were being
> retyped rather than shared previously which made me wonder.

Definitions in the kernel are likely to exist for a long time though,
as the tool is still pretty primitive and doesn't handle anything that
changes layout (such as any register affected by E2H).

> 
> > Mark Brown <broonie@kernel.org> wrote:
> 
> > > I'd certainly be happy to convert, though that does
> > > seem a bit invasive for a fix.
> 
> > Not for a point fix, for sure. And if you do, make sure it is entirely
> > scripted.
> 
> When you say "entirely scripted" here I take it you're referring to the
> list of registers as well, and I guess also to the information about
> what is enumerated by which ID register values?

The register list is indeed the #1 offender, and that should just be a
script that goes over all the occurrences of ARM64_SYS_REG() and
replace the encoding with something that uses the symbolic name.

For the rest (shifts and stuff), we can probably do that by hand
(there are only a few occurrences).

	M.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2024-08-02 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 16:21 [PATCH] KVM: selftests: arm64: Correct feature test for S1PIE in get-reg-list Mark Brown
2024-08-01  9:30 ` Joey Gouly
2024-08-01 16:45 ` Marc Zyngier
2024-08-01 19:14   ` Mark Brown
2024-08-02  9:00     ` Marc Zyngier
2024-08-02 12:43       ` Mark Brown
2024-08-02 13:36         ` Marc Zyngier [this message]
2024-08-02 15:37           ` Mark Brown
2024-08-08 17:08 ` Oliver Upton

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=86a5hv11yp.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=shuah@kernel.org \
    --cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).