From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] State of KVM bits in linux-headers
Date: Wed, 11 Jan 2012 14:16:56 -0600 [thread overview]
Message-ID: <4F0DEE38.6060100@codemonkey.ws> (raw)
In-Reply-To: <AD835CAF-820F-41EA-978D-1C7AED1B0BE3@suse.de>
On 01/11/2012 02:05 PM, Alexander Graf wrote:
>
> On 11.01.2012, at 20:59, Anthony Liguori wrote:
>
>> On 01/11/2012 01:53 PM, Alexander Graf wrote:
>>>
>>> On 11.01.2012, at 20:52, Anthony Liguori wrote:
>>>
>>>>> IIRC, we never had this problem with qemu-kvm - as the merges were
>>>>> coordinated with the kernel (subsystem) tree.
>>>>
>>>> Are you suggesting that kvm header updates go through uq/master? That seems reasonable to me and is certainly the least amount of change.
>>>
>>> So how about code that actually leverages the new headers?
>>
>> Shared KVM infrastructure should go through uq/master. So changes to kvm-all.c, linux-headers/* should go through uq/master.
>>
>> Target specific kvm changes should go through the appropriate submaintainers tree.
>
> So then if I add some target specific stuff to KVM,
That requires a header update?
> I have to
>
> * send pullreq to KVM
> * wait for that to be applied
> * post a patch to uq/master to update headers
Strictly from a QEMU perspective, we can't depend on APIs that aren't committed
upstream yet.
> * wait for that to merge back to qemu.git
> * send a pull request to qemu.git
Maybe we need to bring a stripped down version of Linux into qemu.git to make it
easier to simultaneously update both trees... ;-)
>
> right? And then after about 3 months we'll have the feature available ;).
You can always just get Acked-by's from the appropriate maintainers. That's
just as good as going through the tree.
Regards,
Anthony Liguori
>
> Alex
>
>
next prev parent reply other threads:[~2012-01-11 20:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 19:16 State of KVM bits in linux-headers Jan Kiszka
2012-01-11 19:16 ` [Qemu-devel] " Jan Kiszka
2012-01-11 19:32 ` Alexander Graf
2012-01-11 19:32 ` [Qemu-devel] " Alexander Graf
2012-01-11 19:38 ` Anthony Liguori
2012-01-11 19:45 ` Alexander Graf
2012-01-11 19:46 ` Jan Kiszka
2012-01-11 19:46 ` Jan Kiszka
2012-01-11 19:48 ` Alexander Graf
2012-01-11 19:48 ` Alexander Graf
2012-01-11 19:38 ` Jan Kiszka
2012-01-11 19:38 ` [Qemu-devel] " Jan Kiszka
2012-01-11 19:41 ` Anthony Liguori
2012-01-11 19:41 ` Anthony Liguori
2012-01-11 19:46 ` Alexander Graf
2012-01-11 19:48 ` Jan Kiszka
2012-01-11 19:48 ` Jan Kiszka
2012-01-11 19:52 ` Anthony Liguori
2012-01-11 19:52 ` Anthony Liguori
2012-01-11 19:53 ` Alexander Graf
2012-01-11 19:53 ` Alexander Graf
2012-01-11 19:59 ` Anthony Liguori
2012-01-11 20:05 ` Alexander Graf
2012-01-11 20:16 ` Anthony Liguori [this message]
2012-01-11 21:48 ` Alexander Graf
2012-01-11 21:48 ` [Qemu-devel] " Alexander Graf
2012-01-12 8:34 ` Avi Kivity
2012-01-12 8:34 ` Avi Kivity
2012-01-11 19:56 ` Jan Kiszka
2012-01-11 19:56 ` Jan Kiszka
2012-01-12 6:35 ` Gleb Natapov
2012-01-12 6:35 ` Gleb Natapov
2012-01-11 19:32 ` [RFC][PATCH] Update linux headers against kvm.git Jan Kiszka
2012-01-11 19:32 ` [Qemu-devel] " Jan Kiszka
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=4F0DEE38.6060100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.