[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <IA1PR20MB49532A7223FD732E7A7812ABBB7E9@IA1PR20MB4953.namprd20.prod.outlook.com>
Date: Wed, 17 May 2023 13:16:52 +0800
From: Inochi Amaoto <inochiama@...look.com>
To: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Nikita Shubin <n.shubin@...ro.com>,
Inochi Amaoto <inochiama@...look.com>
Cc: linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
linux-riscv@...ts.infradead.org
Subject: RESEND Re: [PATCH 2/2] perf vendor events riscv: add T-HEAD C9xx JSON file
As my last email is correct, this is a resend.
>
> They are not the same - they are different in many ways. And c906 list
> seems more complete to me.
>
They are different, as this summary:
event id range | support cpu
0x01 - 0x06 | c906,c910,c920
0x07 | c906
0x08 - 0x0a | c910,c920
0x0b - 0x0f | c906,c910,c920
0x10 - 0x1a | c910,c920
0x1b - 0x1c | c910,c920 (software defined, >= 0x1b)
0x1d - 0x2a | c906
This table shows it is not very different. The events of c910 and c906
are complementary.
> I think you should drop wildcard (it shouldn't be used anyway) then and
> name it c906.
>
> "0x5b7-0x0-0x0,v1,t-head/c906,core" would match both c906 and c910.
>
Drop wildcard is a good idea. But I choose to preserve t-head c9xx id,
as it cover all events for c9xx series.
Powered by blists - more mailing lists