From: Avi Kivity <avi@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Store multiple cpuid entries for a single function
Date: Tue, 13 Jan 2009 11:27:07 +0200 [thread overview]
Message-ID: <496C5E6B.8010304@redhat.com> (raw)
In-Reply-To: <1231757365-15717-3-git-send-email-amit.shah@redhat.com>
Amit Shah wrote:
> CPUID functions 4, 0xb and 0xd behave differently for different values of ECX.
> Store these values if userspace passes them.
>
Userspace has no way of knowing whether the kernel contains this fix or not.
Use the SET_CPUID2 interface instead.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-13 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 10:49 CPUID handling: cleanups and support for storing subleaf values Amit Shah
2009-01-12 10:49 ` [PATCH] KVM: x86: Fix typos and whitespace errors Amit Shah
2009-01-12 10:49 ` [PATCH] KVM: x86: Store multiple cpuid entries for a single function Amit Shah
2009-01-12 20:39 ` Muli Ben-Yehuda
2009-01-13 5:23 ` Amit Shah
2009-01-13 9:27 ` Avi Kivity [this message]
2009-01-13 9:40 ` Amit Shah
2009-01-13 9:45 ` Avi Kivity
2009-01-13 9:58 ` Amit Shah
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=496C5E6B.8010304@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kvm@vger.kernel.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