[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191002015338.GA28086@andestech.com>
Date: Wed, 2 Oct 2019 09:53:39 +0800
From: Alan Kao <alankao@...estech.com>
To: "hch@...radead.org" <hch@...radead.org>
CC: Atish Patra <Atish.Patra@....com>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"anup@...infault.org" <anup@...infault.org>,
"palmer@...ive.com" <palmer@...ive.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"johan@...nel.org" <johan@...nel.org>,
"paul.walmsley@...ive.com" <paul.walmsley@...ive.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>
Subject: Re: [v6 PATCH] RISC-V: Remove unsupported isa string info print
On Tue, Oct 01, 2019 at 03:10:16AM -0700, hch@...radead.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@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
Powered by blists - more mailing lists