From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Peter Maydell <peter.maydell@linaro.org>,
kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11
Date: Tue, 03 Sep 2013 17:35:07 +0200 [thread overview]
Message-ID: <522601AB.1050901@redhat.com> (raw)
In-Reply-To: <52260025.3050704@ozlabs.ru>
Il 03/09/2013 17:28, Alexey Kardashevskiy ha scritto:
> On 09/03/2013 08:42 PM, Jan Kiszka wrote:
>> On 2013-09-03 11:32, Alexey Kardashevskiy wrote:
>>> On 09/03/2013 07:29 PM, Peter Maydell wrote:
>>>> On 3 September 2013 09:27, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>>>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>>>> ---
>>>>>
>>>>> I need this update as VFIO on PPC64/pseries got in upstream kernel
>>>>> and this is required by VFIO-SPAPR bits in QEMU. Others may find this
>>>>> update useful too :)
>>>>> ---
>>>>> linux-headers/asm-arm64/kvm.h | 168 ++++++++++++++++++++++++++++++++++++
>>>>> linux-headers/asm-arm64/kvm_para.h | 1 +
>>>>> linux-headers/asm-mips/kvm.h | 81 +++++++++--------
>>>>> linux-headers/linux/kvm.h | 3 +
>>>>> linux-headers/linux/vfio.h | 42 ++++++++-
>>>>> linux-headers/linux/virtio_config.h | 3 +
>>>>> 6 files changed, 254 insertions(+), 44 deletions(-)
>>>>> create mode 100644 linux-headers/asm-arm64/kvm.h
>>>>> create mode 100644 linux-headers/asm-arm64/kvm_para.h
>>>>
>>>> I think this should go in via the KVM tree, not trivial.
>>>
>>> I do not mind, it just went through the trivial tree last time, that's it.
>>
>> This shouldn't be routed through trivial in general as things broke too
>> often in this area.
>
> Sorry for my ignorance, but this is The Kernel, it is already there, broken
> or not, even if it is broken, qemu cannot stay isolated, no?
> This is a mechanical change, no more.
It's a matter of keeping things bisectable. If we can detect a
breakage, we can first work around it, and then apply the header update.
And if we don't detect it, maintainers usually send pull requests when
they have time to work on breakage caused by their patches.
Paolo
next prev parent reply other threads:[~2013-09-03 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 8:27 [Qemu-devel] [PATCH] linux-headers: update to 3.11 Alexey Kardashevskiy
2013-09-03 9:29 ` Peter Maydell
2013-09-03 9:32 ` Alexey Kardashevskiy
2013-09-03 10:42 ` Jan Kiszka
2013-09-03 15:28 ` Alexey Kardashevskiy
2013-09-03 15:34 ` Peter Maydell
2013-09-03 15:47 ` Alexey Kardashevskiy
2013-09-03 15:55 ` Peter Maydell
2013-09-03 15:58 ` Alex Williamson
2013-09-03 16:03 ` Peter Maydell
2013-09-03 16:12 ` Alex Williamson
2013-09-03 15:35 ` Paolo Bonzini [this message]
2013-09-05 3:16 ` Alexey Kardashevskiy
2013-09-05 6:07 ` Paolo Bonzini
2013-09-18 3:04 ` Alexey Kardashevskiy
2013-09-18 4:51 ` Gleb Natapov
2013-09-12 16:31 ` Paolo Bonzini
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=522601AB.1050901@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).