From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Re: [PATCH 0/5] bios: >4G updates Date: Wed, 15 Oct 2008 19:46:49 +0200 Message-ID: <48F62C89.8070109@redhat.com> References: <1222273063.16470.157.camel@lappy> <1222358913.8138.245.camel@2710p.home> <48DFA094.6040208@redhat.com> <48E22A32.7060007@redhat.com> <48E257E7.8000600@redhat.com> <1222809578.9495.24.camel@2710p.home> <48E4BFB6.5020204@redhat.com> <20081012225006.GA23256@morn.localdomain> <20081013064513.GN11435@redhat.com> <48F4BAC8.9090505@redhat.com> <20081015004146.GA10286@morn.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , Alex Williamson , kvm-devel To: "Kevin O'Connor" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:43101 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751055AbYJORqz (ORCPT ); Wed, 15 Oct 2008 13:46:55 -0400 In-Reply-To: <20081015004146.GA10286@morn.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: Kevin O'Connor wrote: >> Kevin, will you accept qemu-specific and kvm-specific patches to >> SeaBIOS? I'd like to avoid permanent deltas. >> > > Yes. > > Thanks. > There is already code specific to qemu and coreboot. I don't see any > issues with having a CONFIG_KVM build option. > Most kvm specific patches would actually be fairly generic features that haven't been upstreamed yet. The only truly kvm specific patch would be tpr patching, which qemu doesn't need. -- error compiling committee.c: too many arguments to function