mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@arm.com>
To: Besar Wicaksono <bwicaksono@nvidia.com>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	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"
	<linux-perf-users@vger.kernel.org>,
	James Clark <james.clark@arm.com>,
	Vikram Sethi <vsethi@nvidia.com>, Rich Wiley <rwiley@nvidia.com>
Subject: Re: [RFC/PATCH 1/1] tools headers arm64: Sync arm64's cputype.h with the kernel sources
Date: Thu, 8 Aug 2024 09:35:05 +0100	[thread overview]
Message-ID: <38be6496-891f-4a6b-ab33-49d63dc9570d@arm.com> (raw)
In-Reply-To: <SJ0PR12MB56763246FC68494FB086DB84A0B92@SJ0PR12MB5676.namprd12.prod.outlook.com>

Hi Besar,

On 8/8/24 05:37, Besar Wicaksono wrote:

[...]

>>>> Today, Arm Ltd implementations happen to share a format, but that isn't
>>>> implied by PMSIDR_EL1.LDS, and there's no guarantee that future CPUs
>>>> will all use the same format.
>>>>
>>>> For the moment we'll have to keep adding to this list.
> 
> I apologize I didn't follow. Do you mean adding new CPU identifier to neoverse_spe[]
> list is still the way to go for now?

Yes, the conclusion is we still need to maintain the CPU ID list for Arm SPE
data source packets.

>>> I would like to use an opposite way - we can only maintain CPU variants with
>>> special data source format, otherwise, all other CPUs use the common format.
>>
>> I think that's not a good idea.
>>
>> Today, Arm Ltd CPUs happen to share *a* common format, but that's likely
>> to change at some point in future, and CPUs from other vendors are
>> likely to use different formats.
>>
>> Assuming any format by default means that when CPUs with different
>> formats are released, we'll produce incorrect results for those CPU by
>> default, we'll need to update tables to exclude those CPUs, and we'll
>> probably want to backport that exclusion to minimize the risk of users
>> getting incorrect/misleading results.
>>
>> While the current situation isn't nice, I think the alternative is
>> worse -- it will confuse and anger users.
>>
>> I think we need to talk with the Arm architects to see if they can
>> define some discovery mechanism for the data source format.
> 
> Is there a follow-up on this from Arm?

I am working on this. The plan is to add meta data support so we can have more
info about Arm SPE features (e.g. data source packet is supported). Then in
the perf tool we need to consolidate to support not only Neoverse core.

It is deferred as I need to firstly resolve the multiple Arm SPE devices, then
I will work on the meta data things and consolidate data source packet (and
include your patches [1]).

Thanks,
Leo

[1] https://lore.kernel.org/linux-perf-users/20240109192310.16234-1-bwicaksono@nvidia.com/


      reply	other threads:[~2024-08-08  8:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 18:33 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
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 [this message]

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=38be6496-891f-4a6b-ab33-49d63dc9570d@arm.com \
    --to=leo.yan@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=bwicaksono@nvidia.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.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=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=rwiley@nvidia.com \
    --cc=vsethi@nvidia.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®