From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: quintela@redhat.com, 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 08:07:50 -0500 [thread overview]
Message-ID: <4DBFFE26.5040707@codemonkey.ws> (raw)
In-Reply-To: <4DBFFD57.4070909@siemens.com>
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.
These days, so few things change in the KVM interface though that maybe
it's not the end of the world.
Regards,
Anthony Liguori
>
> Otherwise, we can also discuss this based on the patch I'm preparing ATM.
>
> Jan
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for May 03rd
Date: Tue, 03 May 2011 08:07:50 -0500 [thread overview]
Message-ID: <4DBFFE26.5040707@codemonkey.ws> (raw)
In-Reply-To: <4DBFFD57.4070909@siemens.com>
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.
These days, so few things change in the KVM interface though that maybe
it's not the end of the world.
Regards,
Anthony Liguori
>
> Otherwise, we can also discuss this based on the patch I'm preparing ATM.
>
> Jan
>
next prev parent reply other threads:[~2011-05-03 13:07 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 [this message]
2011-05-03 13:07 ` Anthony Liguori
2011-05-03 14:10 ` Jan Kiszka
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=4DBFFE26.5040707@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--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.