From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] State of KVM bits in linux-headers Date: Wed, 11 Jan 2012 13:41:38 -0600 Message-ID: <4F0DE5F2.7090001@codemonkey.ws> References: <4F0DE028.4050707@siemens.com> <4F0DE54F.1050700@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , qemu-devel , kvm To: Jan Kiszka Return-path: Received: from mail-gx0-f174.google.com ([209.85.161.174]:63547 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752176Ab2AKTlo (ORCPT ); Wed, 11 Jan 2012 14:41:44 -0500 Received: by ggdk6 with SMTP id k6so557476ggd.19 for ; Wed, 11 Jan 2012 11:41:42 -0800 (PST) In-Reply-To: <4F0DE54F.1050700@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 >