From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "Zhang, Xiantao" <xiantao.zhang@intel.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Avi Kivity <avi@redhat.com>, Chris Wright <chrisw@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Mar 23
Date: Thu, 25 Mar 2010 10:43:48 +0100 [thread overview]
Message-ID: <4BAB3054.9030708@redhat.com> (raw)
In-Reply-To: <4BAB2F6B.5010400@web.de>
On 03/25/10 10:39, Jan Kiszka wrote:
> Zhang, Xiantao wrote:
>> For ia64 part, maybe we can keep the current qemu-kvm.git for the users. And it is not a must to push it into Qemu upstream.
>> Xiantao
>>
>
> Does it still build& work? Does someone test it at least infrequently?
> Or are there users?
>
> There were a few changes recently due to cleanups and/or switches to
> upstream code. There will be more in the future. And at some point heavy
> work will be needed when there are no more qemu-kvm* files. That could
> be a point ia64 breaks forever unless someone jumps in.
>
> BTW, I'm also carrying ia64 bits in kvm-kmod. I never compiled them
> (except for the "make headers_install" which throws tons of warnings at
> me), I'm just keeping them for now to enforce architecture separation in
> case someone once wishes to add another arch to this wrapper.
I think the end result will be that an older version of qemu-kvm will be
around, and if someone decides to pick up on it, they will have to work
from that. At this point I only see some of the Japanese vendors
potentially being interested, but I think they have mostly been looking
at Xen/ia64. Then again, I have no idea what the state is for Xen/ia64
patches for QEMU, in theory a lot of it should be shared.
As long as the bits are sitting in the tree without disturbing other
parts, then I just think we should let them sit there.
Cheers,
Jes
next prev parent reply other threads:[~2010-03-25 9:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 6:11 KVM call agenda for Mar 23 Chris Wright
2010-03-23 8:40 ` Juan Quintela
2010-03-23 13:25 ` Juan Quintela
2010-03-23 9:31 ` Jan Kiszka
2010-03-23 9:52 ` Avi Kivity
2010-03-23 10:50 ` Jan Kiszka
2010-03-23 10:57 ` Avi Kivity
2010-03-23 11:13 ` Jan Kiszka
2010-03-23 12:29 ` Avi Kivity
2010-03-23 12:45 ` Anthony Liguori
2010-03-23 12:51 ` Avi Kivity
2010-03-23 12:56 ` [Qemu-devel] " Jes Sorensen
2010-03-25 1:31 ` Zhang, Xiantao
2010-03-25 9:39 ` Jan Kiszka
2010-03-25 9:43 ` Jes Sorensen [this message]
2010-03-26 18:48 ` Chris Wright
2010-03-23 12:40 ` Anthony Liguori
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=4BAB3054.9030708@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=xiantao.zhang@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.