On Sat, Jan 29, 2022 at 2:10 AM Peter Maydell <peter.mayd...@linaro.org> wrote: > > On Fri, 21 Jan 2022 at 09:42, Alistair Francis > <alistair.fran...@opensource.wdc.com> wrote: > > > > From: LIU Zhiwei <zhiwei_...@c-sky.com> > > > > We need not specially process vtype when XLEN changes. > > > > Signed-off-by: LIU Zhiwei <zhiwei_...@c-sky.com> > > Reviewed-by: Richard Henderson <richard.hender...@linaro.org> > > Reviewed-by: Alistair Francis <alistair.fran...@wdc.com> > > Message-id: 20220120122050.41546-16-zhiwei_...@c-sky.com > > Signed-off-by: Alistair Francis <alistair.fran...@wdc.com> > > Odd thing I noticed looking at this code: as far as I can see we > may set env->vill to 1 in the vsetvl helper, but there is nowhere > that we set it to 0, so once it transitions to 1 it's stuck there > until the system is reset. Is this really right?
This is really confusing. It implies that you can't set vill from software, but that just seems to be confusing wording. Reading https://lists.riscv.org/g/tech-vector-ext/topic/reliably_set_vtype_vill/86745728 it seems that this is a QEMU bug and the guest should be able to set the bit as part of vsetvl @LIU Zhiwei are you able to fix this up? Alistair
