From: Jan Beulich <jbeulich@suse.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: binutils@sourceware.org, kito.cheng@sifive.com,
palmer@dabbelt.com, christoph.muellner@vrull.eu,
wuwei2016@iscas.ac.cn, shihua@iscas.ac.cn, shiyulong@iscas.ac.cn,
chenyixuan@iscas.ac.cn, Jiawei <jiawei@iscas.ac.cn>
Subject: Re: [PATCH] RISC-V: Add 'Smcntrpmf' extension and its CSRs
Date: Tue, 1 Aug 2023 08:11:25 +0200 [thread overview]
Message-ID: <41a2a27e-79d3-90e8-ca05-517c1626a740@suse.com> (raw)
In-Reply-To: <CAPpQWtCB+E4iWmrZjopX6jQ2z-i5JwvHar1iqxQz-ckuLtx0cw@mail.gmail.com>
On 01.08.2023 06:51, Nelson Chu wrote:
> On Mon, Jul 24, 2023 at 1:25 PM Jiawei <jiawei@iscas.ac.cn> wrote:
>
>> This patch supports RISC-V cycle and instret privilege mode filtering
>> extension(Smcntrpmf)[1]. It adds two new 64-bits register mcyclecfg
>> and minstretcfg that configure privilege mode filtering for the cycle
>> and instret counters, respectively. Remove dropped CSRs that use the
>> same CSR number with Smcntrpmf extension(mscounteren, mhcounteren).
>>
>
> If we still want to support the privileged versions, then we should use
> DECLARE_CSR_ALIAS for these kinds of the reused csrs. However, maybe it's
> time that we should give up on supporting the multiple privileged versions
> in binutils, and then support the newest one.
That might work now, but going forward you won't be able to always only
support the newest version, I suppose.
Jan
next prev parent reply other threads:[~2023-08-01 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 5:24 Jiawei
2023-08-01 4:51 ` Nelson Chu
2023-08-01 6:11 ` Jan Beulich [this message]
2023-08-01 7:05 ` Tsukasa OI
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=41a2a27e-79d3-90e8-ca05-517c1626a740@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=chenyixuan@iscas.ac.cn \
--cc=christoph.muellner@vrull.eu \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=nelson@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).