From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] use upstream cpuid code
Date: Mon, 03 Aug 2009 17:06:28 +0300 [thread overview]
Message-ID: <4A76EEE4.5090403@redhat.com> (raw)
In-Reply-To: <20090803132226.GC4374@poweredge.glommer>
On 08/03/2009 04:22 PM, Glauber Costa wrote:
> On Mon, Aug 03, 2009 at 02:57:47PM +0300, Avi Kivity wrote:
>
>> On 07/28/2009 11:05 PM, Glauber Costa wrote:
>>
>>> use cpuid code from upstream. By doing that, we lose the following snippet
>>> in kvm_get_supported_cpuid():
>>>
>>> ret |= 1<< 12; /* MTRR */
>>> ret |= 1<< 16; /* PAT */
>>> ret |= 1<< 7; /* MCE */
>>> ret |= 1<< 14; /* MCA */
>>>
>>> A quick search in mailing lists says this code is not really necessary, and we're
>>> keeping it just for backwards compatibility. This is not that important, because
>>> we'd lose it anyway in the golden day in which we totally merge with qemu.
>>> Anyway, if it do _is_ important, we can send a patch to qemu with it.
>>>
>>>
>> It is important. Please don't introduce regressions (if you do,
>> introduce them in separate patches). The procedure to drop such
>> workarounds for kernel bugs is to verify that major distros have the
>> kernel fixes in their supported kernels.
>>
> Since this was introduced to fix a bug that did not even existed in Windows,
> I can't see what you mean by "distro kernels" here.
>
If qemu-kvm with this patch works on Fedora 10 (latest kernel) and the
equivalent opensuse and Ubuntu kernels, then we can safely remove the
bug workaround. If not, if we apply the patch we just cause users
needless pain.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-03 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 20:05 [PATCH] use upstream cpuid code Glauber Costa
2009-08-03 11:57 ` Avi Kivity
2009-08-03 13:22 ` Glauber Costa
2009-08-03 14:06 ` Avi Kivity [this message]
2009-08-03 14:12 ` Glauber Costa
2009-08-03 14:20 ` Avi Kivity
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=4A76EEE4.5090403@redhat.com \
--to=avi@redhat.com \
--cc=glommer@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