[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190910060010.GA6027@infradead.org>
Date: Mon, 9 Sep 2019 23:00:10 -0700
From: "hch@...radead.org" <hch@...radead.org>
To: Atish Patra <Atish.Patra@....com>
Cc: "hch@...radead.org" <hch@...radead.org>,
"anup@...infault.org" <anup@...infault.org>,
"paul.walmsley@...ive.com" <paul.walmsley@...ive.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"palmer@...ive.com" <palmer@...ive.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"johan@...nel.org" <johan@...nel.org>
Subject: Re: [v5 PATCH] RISC-V: Fix unsupported isa string info.
On Fri, Sep 06, 2019 at 11:27:57PM +0000, Atish Patra wrote:
> > Agreed. May be something like this ?
> >
> > Let's say f/d is enabled in kernel but cpu doesn't support it.
> > "unsupported isa" will only appear if there are any unsupported isa.
> >
> > processor : 3
> > hart : 4
> > isa : rv64imac
> > unsupported isa : fd
> > mmu : sv39
> > uarch : sifive,u54-mc
> >
> > May be I am just trying over optimize one corner case :) :).
> > /proc/cpuinfo should just print all the isa string. That's it.
> >
>
> Ping ?
Yes, I agree with the "dumb" reporting of all capabilities.
Powered by blists - more mailing lists