From: Atish Patra <atishp@atishpatra.org> To: Atish Patra <atishp@rivosinc.com> Cc: KVM General <kvm@vger.kernel.org>, Anup Patel <anup@brainfault.org>, Damien Le Moal <damien.lemoal@wdc.com>, devicetree <devicetree@vger.kernel.org>, Jisheng Zhang <jszhang@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>, "linux-kernel@vger.kernel.org List" <linux-kernel@vger.kernel.org>, linux-riscv <linux-riscv@lists.infradead.org>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com>, Rob Herring <robh+dt@kernel.org>, kvm-riscv@lists.infradead.org Subject: Re: [PATCH 2/2] RISC-V: KVM: Restrict the extensions that can be disabled Date: Wed, 20 Apr 2022 00:42:50 -0700 [thread overview] Message-ID: <CAOnJCU+EPHxD7MqbswKMy=gZhmyyXMiezqaw1+D1h+O+pbYR2w@mail.gmail.com> (raw) In-Reply-To: <20220420013258.3639264-3-atishp@rivosinc.com> On Tue, Apr 19, 2022 at 6:33 PM Atish Patra <atishp@rivosinc.com> wrote: > > Currently, the config reg register allows to disable all allowed > single letter ISA extensions. It shouldn't be the case as vmm > shouldn't be able disable base extensions (imac). /s/able/able to/ > These extensions should always be enabled as long as they are enabled > in the host ISA. > > Signed-off-by: Atish Patra <atishp@rivosinc.com> > --- > arch/riscv/kvm/vcpu.c | 21 +++++++++++++-------- > 1 file changed, 13 insertions(+), 8 deletions(-) > > diff --git a/arch/riscv/kvm/vcpu.c b/arch/riscv/kvm/vcpu.c > index 2e25a7b83a1b..14dd801651e5 100644 > --- a/arch/riscv/kvm/vcpu.c > +++ b/arch/riscv/kvm/vcpu.c > @@ -38,12 +38,16 @@ const struct kvm_stats_header kvm_vcpu_stats_header = { > sizeof(kvm_vcpu_stats_desc), > }; > > -#define KVM_RISCV_ISA_ALLOWED (riscv_isa_extension_mask(a) | \ > - riscv_isa_extension_mask(c) | \ > - riscv_isa_extension_mask(d) | \ > - riscv_isa_extension_mask(f) | \ > - riscv_isa_extension_mask(i) | \ > - riscv_isa_extension_mask(m)) > +#define KVM_RISCV_ISA_DISABLE_ALLOWED (riscv_isa_extension_mask(d) | \ > + riscv_isa_extension_mask(f)) > + > +#define KVM_RISCV_ISA_DISABLE_NOT_ALLOWED (riscv_isa_extension_mask(a) | \ > + riscv_isa_extension_mask(c) | \ > + riscv_isa_extension_mask(i) | \ > + riscv_isa_extension_mask(m)) > + > +#define KVM_RISCV_ISA_ALLOWED (KVM_RISCV_ISA_DISABLE_ALLOWED | \ > + KVM_RISCV_ISA_DISABLE_NOT_ALLOWED) > > static void kvm_riscv_reset_vcpu(struct kvm_vcpu *vcpu) > { > @@ -217,9 +221,10 @@ static int kvm_riscv_vcpu_set_reg_config(struct kvm_vcpu *vcpu, > switch (reg_num) { > case KVM_REG_RISCV_CONFIG_REG(isa): > if (!vcpu->arch.ran_atleast_once) { > - vcpu->arch.isa = reg_val; > + /* Ignore the disable request for these extensions */ > + vcpu->arch.isa = reg_val | KVM_RISCV_ISA_DISABLE_NOT_ALLOWED; > vcpu->arch.isa &= riscv_isa_extension_base(NULL); > - vcpu->arch.isa &= KVM_RISCV_ISA_ALLOWED; > + vcpu->arch.isa &= KVM_RISCV_ISA_DISABLE_ALLOWED; > kvm_riscv_vcpu_fp_reset(vcpu); > } else { > return -EOPNOTSUPP; > -- > 2.25.1 > Sorry. I forgot to add the fixes tag. Fixes: 92ad82002c39 (RISC-V: KVM: Implement KVM_GET_ONE_REG/KVM_SET_ONE_REG ioctls) -- Regards, Atish
WARNING: multiple messages have this Message-ID (diff)
From: Atish Patra <atishp@atishpatra.org> To: Atish Patra <atishp@rivosinc.com> Cc: KVM General <kvm@vger.kernel.org>, Anup Patel <anup@brainfault.org>, Damien Le Moal <damien.lemoal@wdc.com>, devicetree <devicetree@vger.kernel.org>, Jisheng Zhang <jszhang@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>, "linux-kernel@vger.kernel.org List" <linux-kernel@vger.kernel.org>, linux-riscv <linux-riscv@lists.infradead.org>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com>, Rob Herring <robh+dt@kernel.org>, kvm-riscv@lists.infradead.org Subject: Re: [PATCH 2/2] RISC-V: KVM: Restrict the extensions that can be disabled Date: Wed, 20 Apr 2022 00:42:50 -0700 [thread overview] Message-ID: <CAOnJCU+EPHxD7MqbswKMy=gZhmyyXMiezqaw1+D1h+O+pbYR2w@mail.gmail.com> (raw) In-Reply-To: <20220420013258.3639264-3-atishp@rivosinc.com> On Tue, Apr 19, 2022 at 6:33 PM Atish Patra <atishp@rivosinc.com> wrote: > > Currently, the config reg register allows to disable all allowed > single letter ISA extensions. It shouldn't be the case as vmm > shouldn't be able disable base extensions (imac). /s/able/able to/ > These extensions should always be enabled as long as they are enabled > in the host ISA. > > Signed-off-by: Atish Patra <atishp@rivosinc.com> > --- > arch/riscv/kvm/vcpu.c | 21 +++++++++++++-------- > 1 file changed, 13 insertions(+), 8 deletions(-) > > diff --git a/arch/riscv/kvm/vcpu.c b/arch/riscv/kvm/vcpu.c > index 2e25a7b83a1b..14dd801651e5 100644 > --- a/arch/riscv/kvm/vcpu.c > +++ b/arch/riscv/kvm/vcpu.c > @@ -38,12 +38,16 @@ const struct kvm_stats_header kvm_vcpu_stats_header = { > sizeof(kvm_vcpu_stats_desc), > }; > > -#define KVM_RISCV_ISA_ALLOWED (riscv_isa_extension_mask(a) | \ > - riscv_isa_extension_mask(c) | \ > - riscv_isa_extension_mask(d) | \ > - riscv_isa_extension_mask(f) | \ > - riscv_isa_extension_mask(i) | \ > - riscv_isa_extension_mask(m)) > +#define KVM_RISCV_ISA_DISABLE_ALLOWED (riscv_isa_extension_mask(d) | \ > + riscv_isa_extension_mask(f)) > + > +#define KVM_RISCV_ISA_DISABLE_NOT_ALLOWED (riscv_isa_extension_mask(a) | \ > + riscv_isa_extension_mask(c) | \ > + riscv_isa_extension_mask(i) | \ > + riscv_isa_extension_mask(m)) > + > +#define KVM_RISCV_ISA_ALLOWED (KVM_RISCV_ISA_DISABLE_ALLOWED | \ > + KVM_RISCV_ISA_DISABLE_NOT_ALLOWED) > > static void kvm_riscv_reset_vcpu(struct kvm_vcpu *vcpu) > { > @@ -217,9 +221,10 @@ static int kvm_riscv_vcpu_set_reg_config(struct kvm_vcpu *vcpu, > switch (reg_num) { > case KVM_REG_RISCV_CONFIG_REG(isa): > if (!vcpu->arch.ran_atleast_once) { > - vcpu->arch.isa = reg_val; > + /* Ignore the disable request for these extensions */ > + vcpu->arch.isa = reg_val | KVM_RISCV_ISA_DISABLE_NOT_ALLOWED; > vcpu->arch.isa &= riscv_isa_extension_base(NULL); > - vcpu->arch.isa &= KVM_RISCV_ISA_ALLOWED; > + vcpu->arch.isa &= KVM_RISCV_ISA_DISABLE_ALLOWED; > kvm_riscv_vcpu_fp_reset(vcpu); > } else { > return -EOPNOTSUPP; > -- > 2.25.1 > Sorry. I forgot to add the fixes tag. Fixes: 92ad82002c39 (RISC-V: KVM: Implement KVM_GET_ONE_REG/KVM_SET_ONE_REG ioctls) -- Regards, Atish _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-04-20 7:43 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-20 1:32 [PATCH 0/2] Miscellenous ISA string fixup Atish Patra 2022-04-20 1:32 ` Atish Patra 2022-04-20 1:32 ` [PATCH 1/2] RISC-V: KVM: Remove 's' & 'u' as valid ISA extension Atish Patra 2022-04-20 1:32 ` Atish Patra 2022-04-20 7:43 ` Atish Patra 2022-04-20 7:43 ` Atish Patra 2022-04-20 8:46 ` Anup Patel 2022-04-20 8:46 ` Anup Patel 2022-04-20 1:32 ` [PATCH 2/2] RISC-V: KVM: Restrict the extensions that can be disabled Atish Patra 2022-04-20 1:32 ` Atish Patra 2022-04-20 7:42 ` Atish Patra [this message] 2022-04-20 7:42 ` Atish Patra 2022-04-20 8:47 ` Anup Patel 2022-04-20 8:47 ` Anup Patel
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAOnJCU+EPHxD7MqbswKMy=gZhmyyXMiezqaw1+D1h+O+pbYR2w@mail.gmail.com' \ --to=atishp@atishpatra.org \ --cc=anup@brainfault.org \ --cc=atishp@rivosinc.com \ --cc=damien.lemoal@wdc.com \ --cc=devicetree@vger.kernel.org \ --cc=jszhang@kernel.org \ --cc=krzysztof.kozlowski@canonical.com \ --cc=kvm-riscv@lists.infradead.org \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=robh+dt@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.