Re: [PATCH v8 2/4] mseal: add mseal syscall

2024-02-01 Thread Eric Biggers
On Wed, Jan 31, 2024 at 05:50:24PM +, jef...@chromium.org wrote: > [PATCH v8 2/4] mseal: add mseal syscall [...] > +/* > + * The PROT_SEAL defines memory sealing in the prot argument of mmap(). > + */ > +#define PROT_SEAL0x0400 /* _BITUL(26) */ > + > /* 0x01 - 0x03 are defined in

Re: [PATCH v4 7/9] riscv: vector: adjust minimum Vector requirement to ZVE32X

2024-04-18 Thread Eric Biggers
Hi Conor, On Thu, Apr 18, 2024 at 12:02:10PM +0100, Conor Dooley wrote: > +CC Eric, Jerry > > On Fri, Apr 12, 2024 at 02:49:03PM +0800, Andy Chiu wrote: > > Make has_vector take one argument. This argument represents the minimum > > Vector subextension that the following Vector actions assume. >

Re: [PATCH v4 7/9] riscv: vector: adjust minimum Vector requirement to ZVE32X

2024-04-18 Thread Eric Biggers
On Thu, Apr 18, 2024 at 05:53:55PM +0100, Conor Dooley wrote: > > If it would be useful to do so, we should be able to enable some of the code > > with a smaller VLEN and/or EEW once it has been tested in those > > configurations. > > Some of it should work, but some of it won't be able to work.

Re: [PATCH v4 7/9] riscv: vector: adjust minimum Vector requirement to ZVE32X

2024-04-18 Thread Eric Biggers
On Thu, Apr 18, 2024 at 10:32:03AM -0700, Eric Biggers wrote: > On Thu, Apr 18, 2024 at 05:53:55PM +0100, Conor Dooley wrote: > > > If it would be useful to do so, we should be able to enable some of the > > > code > > > with a smaller VLEN and/or EEW on

Re: [PATCH v4 7/9] riscv: vector: adjust minimum Vector requirement to ZVE32X

2024-04-18 Thread Eric Biggers
On Thu, Apr 18, 2024 at 07:26:00PM +0100, Conor Dooley wrote: > That's great if it does require that the version of the vector extension > must be standard. Higher quality spec than most if it does. But > "supported" in the context of riscv_isa_extension_available() means that > the hardware suppor

Re: [PATCH v2 05/17] vdso: Avoid call to memset() by getrandom

2024-08-27 Thread Eric Biggers
On Thu, Aug 22, 2024 at 09:13:13AM +0200, Christophe Leroy wrote: > With the current implementation, __cvdso_getrandom_data() calls > memset(), which is unexpected in the VDSO. > > Rewrite opaque data initialisation to avoid memset(). > > Signed-off-by: Christophe Leroy > --- > lib/vdso/getrand