From: Jan Kiszka <jan.kiszka@web.de>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.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:39:55 +0100 [thread overview]
Message-ID: <4BAB2F6B.5010400@web.de> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A3846627DA7@shzsmsx502.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
Zhang, Xiantao wrote:
> Jes Sorensen wrote:
>> On 03/23/10 13:45, Anthony Liguori wrote:
>>> I don't think we can pull in:
>>>
>>> - extboot
>>> - ia64
>>> - in-kernel pit[1]
>>> - associated command line options
>>> - device passthrough
>>>
>>> The question is, if we dropped those things, would people actually
>>> use qemu.git instead of qemu-kvm.git. If the answer is "no", what
>>> set of things do we need in order for people to focus on qemu.git
>>> instead of qemu-kvm.git.
>> I am not sure if anyone is still actively working on ia64. According
>> to the qemu-kvm.git logs, there hasn't been any real ia64 changes to
>> the code since my last commit in June of last year and then a couple
>> of minor configure bits.
>>
>> IMHO we can just let it rot - not sure if Xiantao is still interested?
> 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.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-03-25 9:40 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 [this message]
2010-03-25 9:43 ` Jes Sorensen
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=4BAB2F6B.5010400@web.de \
--to=jan.kiszka@web.de \
--cc=Jes.Sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--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.