From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
kvm@vger.kernel.org, qemu-devel@nongnu.org, qemu-arm@nongnu.org,
"Haibo Xu" <haibo.xu@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] target/arm/kvm: Check supported feature per accelerator (not per vCPU)
Date: Thu, 18 Jun 2020 12:59:31 +0200 [thread overview]
Message-ID: <38dc2adb-d567-cd45-21bd-f68cebbab98a@redhat.com> (raw)
In-Reply-To: <20200618085726.ti2hny6554l4l5kt@kamzik.brq.redhat.com>
On 18/06/20 10:57, Andrew Jones wrote:
>> If it's a test that the feature is enabled (e.g. via -cpu) then I agree.
>> For something that ends up as a KVM_CHECK_EXTENSION or KVM_ENABLE_CAP on
>> the KVM fd, however, I think passing an AccelState is better.
> I can live with that justification as long as we don't support
> heterogeneous VCPU configurations. And, if that ever happens, then I
> guess we'll be reworking a lot more than just the interface of these
> cpu feature probes.
Yes, and anyway configuring "what is allowed" would be separate from
checking "what is supported".
Thanks,
next prev parent reply other threads:[~2020-06-18 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 13:08 [PATCH] target/arm/kvm: Check supported feature per accelerator (not per vCPU) Philippe Mathieu-Daudé
2020-06-17 13:29 ` no-reply
2020-06-17 15:23 ` Andrew Jones
2020-06-17 17:37 ` Paolo Bonzini
2020-06-18 8:57 ` Andrew Jones
2020-06-18 10:59 ` Paolo Bonzini [this message]
2020-06-18 9:22 ` Andrew Jones
2020-06-18 10:17 ` Philippe Mathieu-Daudé
2020-06-18 10:59 ` Paolo Bonzini
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=38dc2adb-d567-cd45-21bd-f68cebbab98a@redhat.com \
--to=pbonzini@redhat.com \
--cc=drjones@redhat.com \
--cc=haibo.xu@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).