From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Huang Ying <ying.huang@intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH -v2] Add MCE support to KVM
Date: Tue, 21 Apr 2009 16:16:04 -0500 [thread overview]
Message-ID: <49EE3794.1070904@codemonkey.ws> (raw)
In-Reply-To: <49EE304D.5060108@redhat.com>
Avi Kivity wrote:
>
> Example: SMP.
There was no KVM support in QEMU at the time when SMP was introduced.
Had there been, I see no reason not to do it in upstream QEMU.
> Example: vlan API.
You'll have to be more specific. Do you mean the up coming vlan API
refactoring? That absolutely should be happening in upstream QEMU.
>>> For this kind of work, we can provide kvm-userspace.git as a kind of
>>> playground where these experiments may be made. kvm-userspace.git
>>> exists to support kvm.git; while qemu.git has a life of its own and
>>> more stringent barriers to acceptance.
>>
>> As long as people are using kvm-userspace.git instead of qemu.git,
>> we're failing IMHO. If kvm-userspace.git is basically the equivalent
>> of the x86 git kernel tree, linux-next, or something like that, then
>> that's a good thing.
>
> That's definitely a long term goal, but qemu is not yet at a point
> where it is easy to implement new features efficiently. Once it
> reaches that state, kvm-userspace will become a simple staging ground
> (or even disappear entirely).
The simple fact is that right now, Fedora ships kvm-userspace and calls
it QEMU. It builds packages for non-KVM enabled boards. There is a
very large userspace that consumes packages derived from kvm-userspace.
Like it or not, kvm-userspace is not an experimental staging ground for
QEMU.
The only reasonable things to do IMHO is for as much as humanly possible
to be deferred to QEMU or for you to comes to terms with your role as a
defacto QEMU maintainer and start pushing back more on patch sets that
don't take into consideration TCG/non-KVM environments :-)
MCE is a perfect example of something that really has no reason to go in
via kvm-userspace since we have enough KVM support in upstream QEMU.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-04-21 21:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 7:29 [PATCH -v2] Add MCE support to KVM Huang Ying
2009-04-18 15:54 ` Anthony Liguori
2009-04-19 8:39 ` Avi Kivity
2009-04-21 16:06 ` Anthony Liguori
2009-04-21 16:19 ` Avi Kivity
2009-04-21 16:12 ` Anthony Liguori
2009-04-21 16:21 ` Avi Kivity
2009-04-21 19:55 ` Anthony Liguori
2009-04-21 20:00 ` Avi Kivity
2009-04-21 20:08 ` Anthony Liguori
2009-04-21 20:45 ` Avi Kivity
2009-04-21 21:16 ` Anthony Liguori [this message]
2009-04-22 5:57 ` Avi Kivity
2009-04-22 13:32 ` Anthony Liguori
2009-04-22 13:58 ` Avi Kivity
2009-04-22 2:32 ` Huang Ying
2009-04-20 1:19 ` Huang Ying
2009-04-20 3:57 ` Kyle Moffett
2009-04-20 5:04 ` Huang Ying
2009-04-20 5:30 ` Andi Kleen
2009-04-22 2:42 ` Gregory Haskins
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=49EE3794.1070904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.com \
/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.