[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALs-HstVAGX476SGi_+ct7xxWrBeSE=nGVqckGjm9xo06K-Mww@mail.gmail.com>
Date: Fri, 7 Apr 2023 16:13:23 -0700
From: Evan Green <evan@...osinc.com>
To: Paul Walmsley <paul@...an.com>
Cc: Palmer Dabbelt <palmer@...osinc.com>, slewis@...osinc.com,
vineetg@...osinc.com, heiko@...ech.de,
Conor Dooley <conor@...nel.org>,
Conor Dooley <conor.dooley@...rochip.com>,
Heiko Stuebner <heiko.stuebner@...ll.eu>,
Albert Ou <aou@...s.berkeley.edu>,
Andrew Bresticker <abrestic@...osinc.com>,
Arnd Bergmann <arnd@...db.de>,
Bagas Sanjaya <bagasdotme@...il.com>,
Celeste Liu <coelacanthus@...look.com>,
Guo Ren <guoren@...nel.org>, Jonathan Corbet <corbet@....net>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Tobias Klauser <tklauser@...tanz.ch>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v5 2/6] RISC-V: Add a syscall for HW probing
On Wed, Apr 5, 2023 at 6:57 AM Paul Walmsley <paul@...an.com> wrote:
>
> On Mon, 27 Mar 2023, Evan Green wrote:
>
> > We don't have enough space for these all in ELF_HWCAP{,2} and there's no
> > system call that quite does this, so let's just provide an arch-specific
> > one to probe for hardware capabilities. This currently just provides
> > m{arch,imp,vendor}id, but with the key-value pairs we can pass more in
> > the future.
> >
> > Co-developed-by: Palmer Dabbelt <palmer@...osinc.com>
> > Signed-off-by: Palmer Dabbelt <palmer@...osinc.com>
> > Signed-off-by: Evan Green <evan@...osinc.com>
> > Reviewed-by: Conor Dooley <conor.dooley@...rochip.com>
> > Reviewed-by: Heiko Stuebner <heiko.stuebner@...ll.eu>
> > Tested-by: Heiko Stuebner <heiko.stuebner@...ll.eu>
>
> Folks are already building RISC-V systems with cores that have different
> feature sets inside the same Linux system image - just like some ARM
> vendors are - so it makes sense to pass this information onto userspace.
>
> By the way, Evan, did you intend to update the copyright dates to include
> 2023?
Updated in v6.
>
> Beyond that,
>
> Reviewed-by: Paul Walmsley <paul.walmsley@...ive.com>
Thanks, Paul!
-Evan
Powered by blists - more mailing lists