From: Paolo Bonzini <pbonzini@redhat.com>
To: Atish Patra <atish.patra@wdc.com>, linux-kernel@vger.kernel.org
Cc: Anup Patel <anup.patel@wdc.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
kvm-riscv@lists.infradead.org, kvm@vger.kernel.org,
linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Vincent Chen <vincent.chen@sifive.com>
Subject: Re: [PATCH v3 1/5] RISC-V: Mark the existing SBI v0.1 implementation as legacy
Date: Fri, 8 Oct 2021 09:24:58 +0200 [thread overview]
Message-ID: <1616f9d2-5530-1266-6734-b5d64cb20658@redhat.com> (raw)
In-Reply-To: <20211008032036.2201971-2-atish.patra@wdc.com>
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@wdc.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
next prev parent reply other threads:[~2021-10-08 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 3:20 [PATCH v3 0/5] Add SBI v0.2 support for KVM Atish Patra
2021-10-08 3:20 ` [PATCH v3 1/5] RISC-V: Mark the existing SBI v0.1 implementation as legacy Atish Patra
2021-10-08 7:24 ` Paolo Bonzini [this message]
2021-10-25 7:53 ` Anup Patel
2021-10-08 3:20 ` [PATCH v3 2/5] RISC-V: Reorganize SBI code by moving legacy SBI to its own file Atish Patra
2021-10-08 3:20 ` [PATCH v3 3/5] RISC-V: Add SBI v0.2 base extension Atish Patra
2021-10-08 3:20 ` [PATCH v3 4/5] RISC-V: Add v0.1 replacement SBI extensions defined in v02 Atish Patra
2021-10-08 3:20 ` [PATCH v3 5/5] RISC-V: Add SBI HSM extension in KVM Atish Patra
2021-10-08 15:02 ` Sean Christopherson
2021-10-11 8:02 ` Atish Patra
2021-10-11 14:32 ` Sean Christopherson
2021-10-11 22:50 ` Atish Patra
2021-10-12 16:46 ` Sean Christopherson
2021-10-10 9:34 ` [PATCH v3 0/5] Add SBI v0.2 support for KVM Guo Ren
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=1616f9d2-5530-1266-6734-b5d64cb20658@redhat.com \
--to=pbonzini@redhat.com \
--cc=anup.patel@wdc.com \
--cc=atish.patra@wdc.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=vincent.chen@sifive.com \
--cc=wangkefeng.wang@huawei.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®