From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Date: Sat, 02 May 2009 07:52:36 +0000 Subject: Re: qemu-kvm.git now live Message-Id: <49FBFBC4.10905@redhat.com> List-Id: References: <49F08BD0.6000706@redhat.com> <1240955602.24625.57.camel@slate.austin.ibm.com> <49F78134.30904@codemonkey.ws> <1240957999.24625.60.camel@slate.austin.ibm.com> <49F81054.4010102@redhat.com> <1241214678.32624.176.camel@slate.austin.ibm.com> In-Reply-To: <1241214678.32624.176.camel-EGjIuKC2qUdB0N6nvOmcJFaTQe2KTcn/@public.gmane.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Hollis Blanchard Cc: Anthony Liguori , KVM list , kvm-ppc , Glauber Costa Hollis Blanchard wrote: >> In that case it's sufficient to have the build system use the upstream >> kvm integration (CONFIG_KVM) rather than the qemu-kvm integration (USE_KVM). >> > > OK, I give up... how is this supposed to work? Nobody ever sets > CONFIG_KVM or KVM_UPSTREAM, but there are a couple tests for it. Glauber > once sent a patch related to that, but I don't see how it helps. > KVM_UPSTREAM is just a marker to let us know which parts of upstream qemu/kvm integration conflict with qemu-kvm.git. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: qemu-kvm.git now live Date: Sat, 02 May 2009 10:52:36 +0300 Message-ID: <49FBFBC4.10905@redhat.com> References: <49F08BD0.6000706@redhat.com> <1240955602.24625.57.camel@slate.austin.ibm.com> <49F78134.30904@codemonkey.ws> <1240957999.24625.60.camel@slate.austin.ibm.com> <49F81054.4010102@redhat.com> <1241214678.32624.176.camel@slate.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , KVM list , kvm-ppc , Glauber Costa To: Hollis Blanchard Return-path: In-Reply-To: <1241214678.32624.176.camel-EGjIuKC2qUdB0N6nvOmcJFaTQe2KTcn/@public.gmane.org> Sender: kvm-ppc-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: kvm.vger.kernel.org Hollis Blanchard wrote: >> In that case it's sufficient to have the build system use the upstream >> kvm integration (CONFIG_KVM) rather than the qemu-kvm integration (USE_KVM). >> > > OK, I give up... how is this supposed to work? Nobody ever sets > CONFIG_KVM or KVM_UPSTREAM, but there are a couple tests for it. Glauber > once sent a patch related to that, but I don't see how it helps. > KVM_UPSTREAM is just a marker to let us know which parts of upstream qemu/kvm integration conflict with qemu-kvm.git. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html