From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Alexander Graf <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] State of KVM bits in linux-headers
Date: Wed, 11 Jan 2012 13:41:38 -0600 [thread overview]
Message-ID: <4F0DE5F2.7090001@codemonkey.ws> (raw)
In-Reply-To: <4F0DE54F.1050700@siemens.com>
On 01/11/2012 01:38 PM, Jan Kiszka wrote:
>>
>>> I would like to see us avoiding this in the future. Headers update
>>> patches should mention the source and should not be merged until the ABI
>>> changes actually made it at least into kvm.git. Same applies, of course,
>>> to the functional changes related to that ABI. Otherwise we risk quite
>>> some mess on everyone's side.
>>
>> I agree.
>>
>>> Another thing: KVM_CAP_PPC_HIOR has been removed again from the kernel
>>> and also the header. Is there real free space now or will the cap
>>> reappear? If there should better be a placeholder, let's add it (to the
>>> kernel).
>>
>> I will reappear with ONE_REG semantics.
>>
>
> OK.
>
> Then please clean up now so that update-linux-headers.sh can be used
> again by "normal" developers. :)
Before we did submodules and had a responsive BIOS maintainer, we maintained
patches within qemu.git for our external dependencies. I think that's a good
strategy here too. It's a little painful, but not entirely awful.
At least it makes it possible for you to (hopefully) trivial rebase a patch if
something is still in limbo.
Regards,
Anthony Liguori
>
> Jan
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Alexander Graf <agraf@suse.de>, kvm <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] State of KVM bits in linux-headers
Date: Wed, 11 Jan 2012 13:41:38 -0600 [thread overview]
Message-ID: <4F0DE5F2.7090001@codemonkey.ws> (raw)
In-Reply-To: <4F0DE54F.1050700@siemens.com>
On 01/11/2012 01:38 PM, Jan Kiszka wrote:
>>
>>> I would like to see us avoiding this in the future. Headers update
>>> patches should mention the source and should not be merged until the ABI
>>> changes actually made it at least into kvm.git. Same applies, of course,
>>> to the functional changes related to that ABI. Otherwise we risk quite
>>> some mess on everyone's side.
>>
>> I agree.
>>
>>> Another thing: KVM_CAP_PPC_HIOR has been removed again from the kernel
>>> and also the header. Is there real free space now or will the cap
>>> reappear? If there should better be a placeholder, let's add it (to the
>>> kernel).
>>
>> I will reappear with ONE_REG semantics.
>>
>
> OK.
>
> Then please clean up now so that update-linux-headers.sh can be used
> again by "normal" developers. :)
Before we did submodules and had a responsive BIOS maintainer, we maintained
patches within qemu.git for our external dependencies. I think that's a good
strategy here too. It's a little painful, but not entirely awful.
At least it makes it possible for you to (hopefully) trivial rebase a patch if
something is still in limbo.
Regards,
Anthony Liguori
>
> Jan
>
next prev parent reply other threads:[~2012-01-11 19:41 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 [this message]
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
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=4F0DE5F2.7090001@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--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.