lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <1616f9d2-5530-1266-6734-b5d64cb20658@redhat.com> Date: Fri, 8 Oct 2021 09:24:58 +0200 From: Paolo Bonzini <pbonzini@...hat.com> To: Atish Patra <atish.patra@....com>, linux-kernel@...r.kernel.org Cc: Anup Patel <anup.patel@....com>, Kefeng Wang <wangkefeng.wang@...wei.com>, kvm-riscv@...ts.infradead.org, kvm@...r.kernel.org, linux-riscv@...ts.infradead.org, Palmer Dabbelt <palmer@...belt.com>, Paul Walmsley <paul.walmsley@...ive.com>, Vincent Chen <vincent.chen@...ive.com> Subject: Re: [PATCH v3 1/5] RISC-V: Mark the existing SBI v0.1 implementation as legacy On 08/10/21 05:20, Atish Patra wrote: > The existing SBI specification impelementation follows v0.1 or legacy > specification. The latest specification known as v0.2 allows more > scalability and performance improvements. > > Rename the existing implementation as legacy and provide a way to allow > future extensions. > > Signed-off-by: Atish Patra<atish.patra@....com> > --- > arch/riscv/include/asm/kvm_vcpu_sbi.h | 29 +++++ > arch/riscv/kvm/vcpu_sbi.c | 149 ++++++++++++++++++++------ > 2 files changed, 148 insertions(+), 30 deletions(-) > create mode 100644 arch/riscv/include/asm/kvm_vcpu_sbi.h It's bikeshedding I know, but still: every time somebody calls something "legacy", a kitten dies. Please use kvm_sbi_ext_0_1_handler and vcpu_sbi_ext_0_1. Paolo
Powered by blists - more mailing lists