From: Yangyu Chen <cyy@cyyself.name>
To: conor@kernel.org
Cc: ajones@ventanamicro.com, anup@brainfault.org,
aou@eecs.berkeley.edu, atishp@atishpatra.org,
conor.dooley@microchip.com, dqfext@gmail.com, guoren@kernel.org,
heiko@sntech.de, inochiama@outlook.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
mark.rutland@arm.com, palmer@dabbelt.com,
paul.walmsley@sifive.com, will@kernel.org
Subject: Re: [PATCH] perf: RISC-V: fix IRQ detection on T-Head C908
Date: Fri, 12 Apr 2024 14:27:28 +0800 [thread overview]
Message-ID: <tencent_49E156C63C84E435E6F16509D6699339520A@qq.com> (raw)
In-Reply-To: <20240314-pep-announcer-2d7f10ff8b65@spud>
>> IMHO, it may be better to use a new DT property like "riscv,cpu-errata" or
>> "<vendor>,cpu-errata". It can achieve almost everything like using pseudo
>> isa. And the only cost I think is a small amount code to parse this.
>
> I suppose we could do that, but accounting for vendor specifics was one
> of the goals for the property I only just added and that I am suggesting
> to use here.
I think there is a simpler way to do that. We use T-Head PMU by default
for All T-Head CPUs (from mvendor id). Then, to test there is sscofpmf in
the ISA string being probed by the kernel. If yes, then use scofpmf.
Otherwise, use T-Head PMU.
I will check if this can also be switched in any vendor CSR like Svpbmt and
T-Head MAE we discussed before.
Thanks,
Yangyu Chen
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-04-12 6:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 6:30 [PATCH] perf: RISC-V: fix IRQ detection on T-Head C908 Qingfang Deng
2024-03-11 7:13 ` Inochi Amaoto
2024-03-11 7:56 ` Qingfang Deng
2024-03-12 14:07 ` Conor Dooley
2024-03-13 1:31 ` Inochi Amaoto
2024-03-14 20:41 ` Conor Dooley
2024-03-15 5:23 ` Inochi Amaoto
2024-04-12 6:27 ` Yangyu Chen [this message]
2024-04-12 7:40 ` Conor Dooley
2024-03-15 8:11 ` Andrew Jones
2024-03-15 12:22 ` Inochi Amaoto
2024-03-18 22:46 ` Atish Patra
2024-03-18 23:48 ` Conor Dooley
2024-03-19 0:48 ` Atish Patra
2024-03-19 9:06 ` Conor Dooley
2024-03-19 13:39 ` Andrew Jones
2024-03-19 15:36 ` Conor Dooley
2024-03-19 20:11 ` Atish Patra
2024-03-19 20:08 ` Atish Patra
2024-04-12 6:09 ` Yangyu Chen
2024-04-17 6:29 ` Guo Ren
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=tencent_49E156C63C84E435E6F16509D6699339520A@qq.com \
--to=cyy@cyyself.name \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=dqfext@gmail.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=inochiama@outlook.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).