From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH STABLE 0/3] Backport kvm cpuid feature trimming to stable
Date: Tue, 19 May 2009 19:18:13 +0300 [thread overview]
Message-ID: <4A12DBC5.3010506@redhat.com> (raw)
In-Reply-To: <5d6222a80905190736m416e3512m326be22cdc5dc77d@mail.gmail.com>
(restored cc list)
Glauber Costa wrote:
> On Tue, May 19, 2009 at 2:02 AM, Avi Kivity <avi@redhat.com> wrote:
>
>> Glauber Costa wrote:
>>
>>> subject self explanatory
>>>
>>>
>> Right, so you have free space here to provide the motivation for the
>> backport. It's a large change and it isn't immediately obvious that it's
>> stable branch material.
>>
>>
>
> This does not introduce any new features.
> Users expects the guest not to have any cpuid features that the host
> cannot honnor. There has been multiple bug reports regarding this in
> the past of Fedora users. I imagine other users have seen it too.
>
If it hits users then it's obviously important. Note though that Mark
found some bugs there, so we need to either backport Mark's patches or
look for a simpler workaround.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-19 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 1:56 [Qemu-devel] [PATCH STABLE 0/3] Backport kvm cpuid feature trimming to stable Glauber Costa
2009-05-19 1:56 ` [Qemu-devel] [PATCH STABLE 1/3] Make x86 cpuid feature names available in file scope Glauber Costa
2009-05-19 1:57 ` [Qemu-devel] [PATCH STABLE 2/3] Fix x86 feature modifications for features that set multiple bits Glauber Costa
2009-05-19 1:57 ` [Qemu-devel] [PATCH STABLE 3/3] kvm: Trim cpu features not supported by kvm Glauber Costa
2009-05-19 5:02 ` [Qemu-devel] [PATCH STABLE 0/3] Backport kvm cpuid feature trimming to stable Avi Kivity
[not found] ` <5d6222a80905190736m416e3512m326be22cdc5dc77d@mail.gmail.com>
2009-05-19 16:18 ` Avi Kivity [this message]
2009-05-19 17:02 ` Glauber Costa
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=4A12DBC5.3010506@redhat.com \
--to=avi@redhat.com \
--cc=glommer@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.