From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "quintela@redhat.com" <quintela@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for May 03rd
Date: Tue, 03 May 2011 16:10:13 +0200 [thread overview]
Message-ID: <4DC00CC5.9020800@siemens.com> (raw)
In-Reply-To: <4DBFFE26.5040707@codemonkey.ws>
On 2011-05-03 15:07, Anthony Liguori wrote:
> On 05/03/2011 08:04 AM, Jan Kiszka wrote:
>> On 2011-05-03 12:21, Juan Quintela wrote:
>>>
>>> Please send in any agenda items you are interested in covering.
>>>
>>
>> Provided there will be more topics:
>> - import kvm headers into qemu, drop #ifdef maze
>
> This has come up a few times in the past.
>
> The opposition tends to be that it would make feature development harder
> because you couldn't easily point QEMU at a different set of kernel headers.
There should be no need to worry, even if for those bits that will
continue to change more frequently. I've included a hopefully easy to
use update mechanism.
>
> These days, so few things change in the KVM interface though that maybe
> it's not the end of the world.
PowerPC and future KVM arch will go through the same changes that x86
should be through now. So I would prefer to avoid the mistakes we made
for the latter.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
"quintela@redhat.com" <quintela@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for May 03rd
Date: Tue, 03 May 2011 16:10:13 +0200 [thread overview]
Message-ID: <4DC00CC5.9020800@siemens.com> (raw)
In-Reply-To: <4DBFFE26.5040707@codemonkey.ws>
On 2011-05-03 15:07, Anthony Liguori wrote:
> On 05/03/2011 08:04 AM, Jan Kiszka wrote:
>> On 2011-05-03 12:21, Juan Quintela wrote:
>>>
>>> Please send in any agenda items you are interested in covering.
>>>
>>
>> Provided there will be more topics:
>> - import kvm headers into qemu, drop #ifdef maze
>
> This has come up a few times in the past.
>
> The opposition tends to be that it would make feature development harder
> because you couldn't easily point QEMU at a different set of kernel headers.
There should be no need to worry, even if for those bits that will
continue to change more frequently. I've included a hopefully easy to
use update mechanism.
>
> These days, so few things change in the KVM interface though that maybe
> it's not the end of the world.
PowerPC and future KVM arch will go through the same changes that x86
should be through now. So I would prefer to avoid the mistakes we made
for the latter.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-03 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 10:21 KVM call agenda for May 03rd Juan Quintela
2011-05-03 10:21 ` [Qemu-devel] " Juan Quintela
2011-05-03 13:04 ` Jan Kiszka
2011-05-03 13:04 ` [Qemu-devel] " Jan Kiszka
2011-05-03 13:07 ` Anthony Liguori
2011-05-03 13:07 ` Anthony Liguori
2011-05-03 14:10 ` Jan Kiszka [this message]
2011-05-03 14:10 ` Jan Kiszka
2011-05-03 14:02 ` Jes Sorensen
2011-05-03 14:02 ` Jes Sorensen
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=4DC00CC5.9020800@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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.