From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <anthony@codemonkey.ws>
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 20:46:40 +0100 [thread overview]
Message-ID: <4F0DE720.3010203@siemens.com> (raw)
In-Reply-To: <4F0DE52B.8030105@codemonkey.ws>
On 2012-01-11 20:38, Anthony Liguori wrote:
> On 01/11/2012 01:32 PM, Alexander Graf wrote:
>>
>> On 11.01.2012, at 20:16, Jan Kiszka wrote:
>>
>>> Hi,
>>>
>>> I'm a bit unhappy about the current state of our supposed to be
>>> automatically sync'ed linux-headers directory in qemu. It has been
>>> updated several times against undefined kernel trees, means against
>>> neither a released version nor kvm.git. Now, if I run an update against
>>> kvm.git + some local change, I get a churn of removals. Same will happen
>>> when that local change ever goes upstream before the other stuff got
>>> finally committed.
>>
>> Yes, call me even more unhappy about it :(.
>
> May I suggest the following:
>
> 1) Have the header syncing script take a commit hash that's stored in git. Make
> script ensure that this has is in Linus' tree.
>
> 2) Maintain a patch on top of Linus' tree in qemu.git that the script would
> apply before actually syncing header files.
>
> That let's us track how we're differing from upstream in a more reliable fashion.
That sounds fairly complicated for a simple problem: Do not merge ABI
changes that aren't at least in kvm.git. There are also other reasons
for this, beside making the sync harder.
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: 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 20:46:40 +0100 [thread overview]
Message-ID: <4F0DE720.3010203@siemens.com> (raw)
In-Reply-To: <4F0DE52B.8030105@codemonkey.ws>
On 2012-01-11 20:38, Anthony Liguori wrote:
> On 01/11/2012 01:32 PM, Alexander Graf wrote:
>>
>> On 11.01.2012, at 20:16, Jan Kiszka wrote:
>>
>>> Hi,
>>>
>>> I'm a bit unhappy about the current state of our supposed to be
>>> automatically sync'ed linux-headers directory in qemu. It has been
>>> updated several times against undefined kernel trees, means against
>>> neither a released version nor kvm.git. Now, if I run an update against
>>> kvm.git + some local change, I get a churn of removals. Same will happen
>>> when that local change ever goes upstream before the other stuff got
>>> finally committed.
>>
>> Yes, call me even more unhappy about it :(.
>
> May I suggest the following:
>
> 1) Have the header syncing script take a commit hash that's stored in git. Make
> script ensure that this has is in Linus' tree.
>
> 2) Maintain a patch on top of Linus' tree in qemu.git that the script would
> apply before actually syncing header files.
>
> That let's us track how we're differing from upstream in a more reliable fashion.
That sounds fairly complicated for a simple problem: Do not merge ABI
changes that aren't at least in kvm.git. There are also other reasons
for this, beside making the sync harder.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-01-11 19:46 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 [this message]
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
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=4F0DE720.3010203@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--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.