From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
kvm@vger.kernel.org
Cc: anup@brainfault.org, atishp@atishpatra.org, ajones@ventanamicro.com
Subject: Re: [PATCH v3 00/10] RISC-V: KVM: change get_reg/set_reg error codes
Date: Thu, 3 Aug 2023 11:56:32 -0300 [thread overview]
Message-ID: <b7ac5ba8-63f0-ca47-aa64-cb634e0fb33b@ventanamicro.com> (raw)
In-Reply-To: <20230803140022.399333-1-dbarboza@ventanamicro.com>
On 8/3/23 11:00, Daniel Henrique Barboza wrote:
> Hi,
>
> This version has changes in the document patch, as suggested by Andrew
> in v2. It also has a new patch (patch 9) that handles error code changes
> in vcpu_vector.c.
I forgot to include a diff that Andrew mentioned in his v2 review:
diff --git a/arch/riscv/kvm/vcpu_onereg.c b/arch/riscv/kvm/vcpu_onereg.c
index c88b0c7f7f01..6ca90c04ba61 100644
--- a/arch/riscv/kvm/vcpu_onereg.c
+++ b/arch/riscv/kvm/vcpu_onereg.c
@@ -506,7 +506,7 @@ static int riscv_vcpu_get_isa_ext_multi(struct kvm_vcpu *vcpu,
unsigned long i, ext_id, ext_val;
if (reg_num > KVM_REG_RISCV_ISA_MULTI_REG_LAST)
- return -EINVAL;
+ return -ENOENT;
for (i = 0; i < BITS_PER_LONG; i++) {
ext_id = i + reg_num * BITS_PER_LONG;
@@ -529,7 +529,7 @@ static int riscv_vcpu_set_isa_ext_multi(struct kvm_vcpu *vcpu,
unsigned long i, ext_id;
if (reg_num > KVM_REG_RISCV_ISA_MULTI_REG_LAST)
- return -EINVAL;
+ return -ENOENT;
for_each_set_bit(i, ®_val, BITS_PER_LONG) {
ext_id = i + reg_num * BITS_PER_LONG;
@@ -644,7 +644,7 @@ int kvm_riscv_vcpu_set_reg(struct kvm_vcpu *vcpu,
break;
}
- return -EINVAL;
+ return -ENOENT;
}
int kvm_riscv_vcpu_get_reg(struct kvm_vcpu *vcpu,
I'll send a v4 including it. Thanks,
Daniel
>
> Patches rebased on top of kvm_riscv_queue.
>
> Changes from v2:
> - patch 9 (new):
> - change kvm error codes for vector registers
> - patch 10 (former 9):
> - rewrite EBUSY doc to mention that the error code indicates that it
> is not allowed to change the reg val after the vcpu started.
> - v2 link: https://lore.kernel.org/kvm/20230801222629.210929-1-dbarboza@ventanamicro.com/
>
> Andrew Jones (1):
> RISC-V: KVM: Improve vector save/restore errors
>
> Daniel Henrique Barboza (9):
> RISC-V: KVM: return ENOENT in *_one_reg() when reg is unknown
> RISC-V: KVM: use ENOENT in *_one_reg() when extension is unavailable
> RISC-V: KVM: do not EOPNOTSUPP in set_one_reg() zicbo(m|z)
> RISC-V: KVM: do not EOPNOTSUPP in set KVM_REG_RISCV_TIMER_REG
> RISC-V: KVM: use EBUSY when !vcpu->arch.ran_atleast_once
> RISC-V: KVM: avoid EBUSY when writing same ISA val
> RISC-V: KVM: avoid EBUSY when writing the same machine ID val
> RISC-V: KVM: avoid EBUSY when writing the same isa_ext val
> docs: kvm: riscv: document EBUSY in KVM_SET_ONE_REG
>
> Documentation/virt/kvm/api.rst | 2 +
> arch/riscv/kvm/aia.c | 4 +-
> arch/riscv/kvm/vcpu_fp.c | 12 +++---
> arch/riscv/kvm/vcpu_onereg.c | 68 +++++++++++++++++++++++-----------
> arch/riscv/kvm/vcpu_sbi.c | 16 ++++----
> arch/riscv/kvm/vcpu_timer.c | 11 +++---
> arch/riscv/kvm/vcpu_vector.c | 60 ++++++++++++++++--------------
> 7 files changed, 104 insertions(+), 69 deletions(-)
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-08-03 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 14:00 [PATCH v3 00/10] RISC-V: KVM: change get_reg/set_reg error codes Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 01/10] RISC-V: KVM: return ENOENT in *_one_reg() when reg is unknown Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 02/10] RISC-V: KVM: use ENOENT in *_one_reg() when extension is unavailable Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 03/10] RISC-V: KVM: do not EOPNOTSUPP in set_one_reg() zicbo(m|z) Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 04/10] RISC-V: KVM: do not EOPNOTSUPP in set KVM_REG_RISCV_TIMER_REG Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 05/10] RISC-V: KVM: use EBUSY when !vcpu->arch.ran_atleast_once Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 06/10] RISC-V: KVM: avoid EBUSY when writing same ISA val Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 07/10] RISC-V: KVM: avoid EBUSY when writing the same machine ID val Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 08/10] RISC-V: KVM: avoid EBUSY when writing the same isa_ext val Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 09/10] RISC-V: KVM: Improve vector save/restore errors Daniel Henrique Barboza
2023-08-03 14:00 ` [PATCH v3 10/10] docs: kvm: riscv: document EBUSY in KVM_SET_ONE_REG Daniel Henrique Barboza
2023-08-03 14:56 ` Daniel Henrique Barboza [this message]
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=b7ac5ba8-63f0-ca47-aa64-cb634e0fb33b@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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: 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