From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 1/4] kvm: Add support for querying supported cpu features
Date: Fri, 08 May 2009 15:50:19 -0500 [thread overview]
Message-ID: <4A049B0B.9030405@us.ibm.com> (raw)
In-Reply-To: <1241359444-8538-2-git-send-email-avi@redhat.com>
Avi Kivity wrote:
> kvm does not support all cpu features; add support for dunamically querying
> the supported feature set.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> kvm.h | 3 ++
> target-i386/kvm.c | 80 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 83 insertions(+), 0 deletions(-)
>
> diff --git a/kvm.h b/kvm.h
> index bd4e8d4..c134c45 100644
> --- a/kvm.h
> +++ b/kvm.h
> @@ -124,6 +124,9 @@ void kvm_arch_remove_all_hw_breakpoints(void);
>
> void kvm_arch_update_guest_debug(CPUState *env, struct kvm_guest_debug *dbg);
>
> +uint32_t kvm_arch_get_supported_cpuid(CPUState *env, uint32_t function,
> + int reg);
> +
> /* generic hooks - to be moved/refactored once there are more users */
>
> static inline void cpu_synchronize_state(CPUState *env, int modified)
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> index b534b2d..5f54ff5 100644
> --- a/target-i386/kvm.c
> +++ b/target-i386/kvm.c
> @@ -34,6 +34,86 @@
> do { } while (0)
> #endif
>
> +#ifdef KVM_CAP_EXT_CPUID
> +
> +static struct kvm_cpuid2 *try_get_cpuid(KVMState *s, int max)
> +{
> + struct kvm_cpuid2 *cpuid;
> + int r, size;
> +
> + size = sizeof(*cpuid) + max * sizeof(*cpuid->entries);
> + cpuid = (struct kvm_cpuid2 *)qemu_mallocz(size);
> + cpuid->nent = max;
> + r = kvm_ioctl(s, KVM_GET_SUPPORTED_CPUID, cpuid);
> + if (r < 0) {
> + if (r == -E2BIG) {
> + qemu_free(cpuid);
> + return NULL;
> + } else {
> + fprintf(stderr, "KVM_GET_SUPPORTED_CPUID failed: %s\n",
> + strerror(-r));
> + exit(1);
> + }
> + }
> + return cpuid;
> +}
> +
> +uint32_t kvm_arch_get_supported_cpuid(CPUState *env, uint32_t function, int reg)
> +{
> + struct kvm_cpuid2 *cpuid;
> + int i, max;
> + uint32_t ret = 0;
> + uint32_t cpuid_1_edx;
> +
> + if (!kvm_check_extension(KVM_CAP_EXT_CPUID)) {
> + return -1U;
> +
kvm_check_extension doesn't exist in upstream QEMU. It's a good idea
though so I added it in a previous commit. However, I changed the
signature to it to take a KVMState * as the first argument (which is
available in env->kvm_state). I updated this patch to pass the extra
's' parameter.
Regards,
Anthony Liguori
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-05-08 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 14:04 [Qemu-devel] [PATCH 0/4] Fix kvm cpuid reporting Avi Kivity
2009-05-03 14:04 ` [Qemu-devel] [PATCH 1/4] kvm: Add support for querying supported cpu features Avi Kivity
2009-05-08 20:50 ` Anthony Liguori [this message]
2009-05-08 21:09 ` [Qemu-devel] " Anthony Liguori
2009-05-09 8:41 ` Avi Kivity
2009-05-03 14:04 ` [Qemu-devel] [PATCH 2/4] Make x86 cpuid feature names available in file scope Avi Kivity
2009-05-03 14:04 ` [Qemu-devel] [PATCH 3/4] Fix x86 feature modifications for features that set multiple bits Avi Kivity
2009-05-03 14:04 ` [Qemu-devel] [PATCH 4/4] kvm: Trim cpu features not supported by kvm Avi Kivity
2009-05-12 11:52 ` Mark McLoughlin
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=4A049B0B.9030405@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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).