From: Alan Kao <alankao@andestech.com>
To: "hch@infradead.org" <hch@infradead.org>
Cc: Atish Patra <Atish.Patra@wdc.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"anup@brainfault.org" <anup@brainfault.org>,
"palmer@sifive.com" <palmer@sifive.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"johan@kernel.org" <johan@kernel.org>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [v6 PATCH] RISC-V: Remove unsupported isa string info print
Date: Wed, 2 Oct 2019 09:53:39 +0800 [thread overview]
Message-ID: <20191002015338.GA28086@andestech.com> (raw)
In-Reply-To: <20191001101016.GB23507@infradead.org>
On Tue, Oct 01, 2019 at 03:10:16AM -0700, hch@infradead.org wrote:
> On Tue, Oct 01, 2019 at 08:22:37AM +0000, Atish Patra wrote:
> > riscv_of_processor_hartid() or seems to be a better candidate. We
> > already check if "rv" is present in isa string or not. I will extend
> > that to check for rv64i or rv32i. Is that okay ?
>
> I'd rather lift the checks out of that into a function that is called
> exactly once per hart on boot (and future cpu hotplug).
Sorry that I am a bit out of date on this. Is there any related
discussion about such checks? Just want to make sure if the check
stops here and will not go any further for extensions, Xs and Zs.
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-10-02 1:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 0:23 [v6 PATCH] RISC-V: Remove unsupported isa string info print Atish Patra
2019-10-01 7:02 ` Christoph Hellwig
2019-10-01 8:22 ` Atish Patra
2019-10-01 10:10 ` hch
2019-10-02 1:53 ` Alan Kao [this message]
2019-10-02 6:28 ` Atish Patra
2019-10-07 16:58 ` hch
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=20191002015338.GA28086@andestech.com \
--to=alankao@andestech.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=hch@infradead.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
/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