From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Qemu-devel] [PATCH] linux-headers: update to 3.11 Date: Tue, 03 Sep 2013 17:35:07 +0200 Message-ID: <522601AB.1050901@redhat.com> References: <1378196857-27541-1-git-send-email-aik@ozlabs.ru> <5225AC9A.2090601@ozlabs.ru> <5225BD32.8030001@siemens.com> <52260025.3050704@ozlabs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Peter Maydell , QEMU Developers , QEMU Trivial , Michael Tokarev , Gleb Natapov , kvm-devel To: Alexey Kardashevskiy Return-path: Received: from mx1.redhat.com ([209.132.183.28]:9334 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755801Ab3ICPfd (ORCPT ); Tue, 3 Sep 2013 11:35:33 -0400 In-Reply-To: <52260025.3050704@ozlabs.ru> Sender: kvm-owner@vger.kernel.org List-ID: 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 wrote: >>>>> Signed-off-by: Alexey Kardashevskiy >>>>> --- >>>>> >>>>> 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