From: "Cédric Le Goater" <clegoate@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: qemu-s390x@nongnu.org, David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v3 1/2] target/s390x/kvm: Turn KVM_CAP_SYNC_REGS into a hard requirement
Date: Tue, 24 Oct 2023 08:12:39 +0200 [thread overview]
Message-ID: <98b77982-e8df-40b3-9ebc-b4762f3141af@redhat.com> (raw)
In-Reply-To: <20231011080538.796999-2-thuth@redhat.com>
On 10/11/23 10:05, Thomas Huth wrote:
> Since we already require at least kernel 3.15 in the s390x KVM code,
> we can assume that the KVM_CAP_SYNC_REGS capability is always there.
> Thus turn this into a hard requirement now.
>
> Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Thanks,
C.
> ---
> target/s390x/kvm/kvm.c | 20 ++++++++++++++------
> 1 file changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/target/s390x/kvm/kvm.c b/target/s390x/kvm/kvm.c
> index bc5c56a305..b3e2eaa2eb 100644
> --- a/target/s390x/kvm/kvm.c
> +++ b/target/s390x/kvm/kvm.c
> @@ -337,21 +337,29 @@ int kvm_arch_get_default_type(MachineState *ms)
>
> int kvm_arch_init(MachineState *ms, KVMState *s)
> {
> + int required_caps[] = {
> + KVM_CAP_DEVICE_CTRL,
> + KVM_CAP_SYNC_REGS,
> + };
> +
> + for (int i = 0; i < ARRAY_SIZE(required_caps); i++) {
> + if (!kvm_check_extension(s, required_caps[i])) {
> + error_report("KVM is missing capability #%d - "
> + "please use kernel 3.15 or newer", required_caps[i]);
> + return -1;
> + }
> + }
> +
> object_class_foreach(ccw_machine_class_foreach, TYPE_S390_CCW_MACHINE,
> false, NULL);
>
> - if (!kvm_check_extension(kvm_state, KVM_CAP_DEVICE_CTRL)) {
> - error_report("KVM is missing capability KVM_CAP_DEVICE_CTRL - "
> - "please use kernel 3.15 or newer");
> - return -1;
> - }
> if (!kvm_check_extension(s, KVM_CAP_S390_COW)) {
> error_report("KVM is missing capability KVM_CAP_S390_COW - "
> "unsupported environment");
> return -1;
> }
>
> - cap_sync_regs = kvm_check_extension(s, KVM_CAP_SYNC_REGS);
> + cap_sync_regs = true;
> cap_async_pf = kvm_check_extension(s, KVM_CAP_ASYNC_PF);
> cap_mem_op = kvm_check_extension(s, KVM_CAP_S390_MEM_OP);
> cap_mem_op_extension = kvm_check_extension(s, KVM_CAP_S390_MEM_OP_EXTENSION);
next prev parent reply other threads:[~2023-10-24 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 8:05 [PATCH v3 0/2] target/s390x/kvm: Simplify the synchronization code Thomas Huth
2023-10-11 8:05 ` [PATCH v3 1/2] target/s390x/kvm: Turn KVM_CAP_SYNC_REGS into a hard requirement Thomas Huth
2023-10-24 6:12 ` Cédric Le Goater [this message]
2023-10-11 8:05 ` [PATCH v3 2/2] target/s390x/kvm: Simplify the GPRs, ACRs, CRs and prefix synchronization code Thomas Huth
2023-10-24 6:11 ` Cédric Le Goater
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=98b77982-e8df-40b3-9ebc-b4762f3141af@redhat.com \
--to=clegoate@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).