Linux Perf Users
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Besar Wicaksono <bwicaksono@nvidia.com>,
	Will Deacon <will@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [RFC/PATCH 1/1] tools headers arm64: Sync arm64's cputype.h with the kernel sources
Date: Tue, 4 Jun 2024 15:34:36 +0100	[thread overview]
Message-ID: <Zl8l_NdVEmcrsuSx@J2N7QTR9R3> (raw)
In-Reply-To: <Zl8cYk0Tai2fs7aM@x1>

On Tue, Jun 04, 2024 at 10:53:38AM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Jun 04, 2024 at 10:11:22AM +0100, Mark Rutland wrote:
> > On Mon, Jun 03, 2024 at 03:33:07PM -0300, Arnaldo Carvalho de Melo wrote:
> > > The changes in the above patch add MIDR_NEOVERSE_V[23] and
> > > MIDR_NEOVERSE_V1 is used in arm-spe.c, so probably we need to add those
> > > and perhaps MIDR_CORTEX_X4 to that array? Or maybe we need to leave this
> > > for later when this is all tested on those machines?
> > 
> > Hmm... looking at where that was added this is somewhat misnamed, this
> > is really saying that these cores use the same IMPLEMENTATION DEFINED
> > encoding of the source field. That's not really a property of Neoverse
> > specifically, and I'm not sure what Arm's policy is here going forwards.
> > 
> > We should probably rename that to something like
> > common_data_source_encoding, with a big comment about exactly what it
> > implies.
> > 
> > I would not touch this for now -- someone would have to go audit the
> 
> Ok, you mean not touch tools/perf/util/arm-spe.c, right, can I just go
> ahead and update the copy of that header so that we have a clean (of
> build warnings) build?

Yes: update the header, but leave arm-spe.c unchanged. Sorry for not
being clear!

It'd be nice if we could update the commit message to note that we're
deliberately leaving that as-is.

Either way:

Acked-by: Mark Rutland <mark.rutland@arm.com>

Mark.

  reply	other threads:[~2024-06-04 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 18:33 [RFC/PATCH 1/1] tools headers arm64: Sync arm64's cputype.h with the kernel sources Arnaldo Carvalho de Melo
2024-06-04  9:11 ` Mark Rutland
2024-06-04 13:53   ` Arnaldo Carvalho de Melo
2024-06-04 14:34     ` Mark Rutland [this message]
2024-06-04 18:55       ` Arnaldo Carvalho de Melo
2024-06-04 17:14   ` Leo Yan
2024-06-04 18:55     ` Mark Rutland
2024-06-04 20:01       ` Leo Yan
2024-06-05  9:32         ` Mark Rutland
2024-08-08  4:37           ` Besar Wicaksono
2024-08-08  8:35             ` Leo Yan

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=Zl8l_NdVEmcrsuSx@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=bwicaksono@nvidia.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --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