From: Oliver Upton <oliver.upton@linux.dev>
To: Eric Auger <eauger@redhat.com>
Cc: Mark Brown <broonie@kernel.org>,
kvm@vger.kernel.org, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org,
Jing Zhang <jingzhangos@google.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
James Morse <james.morse@arm.com>, Marc Zyngier <maz@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3 4/5] tools headers arm64: Update sysreg.h with kernel sources
Date: Thu, 19 Oct 2023 00:06:25 +0000 [thread overview]
Message-ID: <ZTBzAR1KsWuurob7@linux.dev> (raw)
In-Reply-To: <8baca35a-9154-97e6-d682-032fc69d2da6@redhat.com>
Hi Eric,
Thanks for reviewing the series.
On Wed, Oct 18, 2023 at 03:06:12PM +0200, Eric Auger wrote:
> Hi Mark, Oliver,
>
> On 10/18/23 14:16, Mark Brown wrote:
> > On Wed, Oct 18, 2023 at 01:57:31PM +0200, Eric Auger wrote:
> >> On 10/11/23 21:57, Oliver Upton wrote:
> >
> >>> #define set_pstate_pan(x) asm volatile(SET_PSTATE_PAN(x))
> >>> #define set_pstate_uao(x) asm volatile(SET_PSTATE_UAO(x))
> >>> #define set_pstate_ssbs(x) asm volatile(SET_PSTATE_SSBS(x))
> >>> +#define set_pstate_dit(x) asm volatile(SET_PSTATE_DIT(x))
> >
> >> could you comment on the *DIT* addictions, what is it for?
> >
> > DIT is data independent timing, this tells the processor to ensure that
> > instructions take a constant time regardless of the data they are
> > handling.
>
> >
> > Note that this file is just a copy of arch/arm64/include/asm/gpr-num.h,
> > the main purpose here is to sync with the original.
>
> Ah thanks. that's helpful for me to understand where this gpr-num.h
> comes from. This could be documented in the commit msg though.
>
> Something like:
>
> adding tools/arch/arm64/include/asm/gpr-num.h matching linux
> arch/arm64/include/asm/gpr-num.h
>
> and syncing tools/arch/arm64/include/asm/sysreg.h with the fellow header
> in the linux tree.
Yeah, I could've spelled it out a bit more. I already cracked this off
of an even larger patch from before I picked up the series because the
diff was massive.
> tbh I did not initially understand that all this diffstat was aimed to
> match the linux arch/arm64/include/asm/sysreg.h. Now diffing both I have
> some diffs. Doesn't it need a refresh?
I'm worried it is a fool's errand at this point to keep the two in sync,
as I'm sure there will be more in -rc1. The tools copy of sysreg.h isn't
a verbatim copy either, there are some deliberate deletions in there as
well.
I've taken this as is, we can always come back and update the headers
afterwards if we find a need for it
--
Thanks,
Oliver
_______________________________________________
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:[~2023-10-19 0:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 19:57 [PATCH v3 0/5] KVM: selftests: Add ID reg test, update headers Oliver Upton
2023-10-11 19:57 ` [PATCH v3 1/5] tools: arm64: Add a Makefile for generating sysreg-defs.h Oliver Upton
2023-10-18 9:50 ` Eric Auger
2023-10-11 19:57 ` [PATCH v3 2/5] perf build: Generate arm64's sysreg-defs.h and add to include path Oliver Upton
2023-10-17 22:23 ` Namhyung Kim
2023-10-18 14:12 ` Arnaldo Carvalho de Melo
2023-11-07 6:10 ` Ian Rogers
2023-11-17 21:42 ` Ian Rogers
2023-10-11 19:57 ` [PATCH v3 3/5] KVM: selftests: Generate " Oliver Upton
2023-10-18 9:52 ` Eric Auger
2023-10-23 13:53 ` Nina Schoetterl-Glausch
2023-10-27 0:59 ` Oliver Upton
2023-10-25 9:02 ` Aishwarya TCV
2023-10-25 19:07 ` Oliver Upton
2023-10-26 1:06 ` Aishwarya TCV
2023-10-11 19:57 ` [PATCH v3 4/5] tools headers arm64: Update sysreg.h with kernel sources Oliver Upton
2023-10-18 11:57 ` Eric Auger
2023-10-18 12:16 ` Mark Brown
2023-10-18 13:06 ` Eric Auger
2023-10-19 0:06 ` Oliver Upton [this message]
2023-10-19 8:43 ` Eric Auger
2023-10-19 19:48 ` Oliver Upton
2023-10-11 19:57 ` [PATCH v3 5/5] KVM: arm64: selftests: Test for setting ID register from usersapce Oliver Upton
2023-10-16 15:30 ` Cornelia Huck
2023-10-17 8:03 ` Oliver Upton
2023-10-18 12:35 ` Cornelia Huck
2023-10-19 8:38 ` Eric Auger
2024-01-05 9:07 ` Zenghui Yu
2024-01-08 22:40 ` Oliver Upton
2024-01-09 1:31 ` Jing Zhang
2024-01-09 15:36 ` Zenghui Yu
2024-01-09 16:23 ` Jing Zhang
2024-01-09 7:50 ` Itaru Kitayama
2023-10-18 13:44 ` [PATCH v3 0/5] KVM: selftests: Add ID reg test, update headers Marc Zyngier
2023-10-18 23:58 ` 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=ZTBzAR1KsWuurob7@linux.dev \
--to=oliver.upton@linux.dev \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=broonie@kernel.org \
--cc=eauger@redhat.com \
--cc=irogers@google.com \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=jolsa@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.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=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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).