From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Build failure w/o mmu notifiers Date: Sat, 18 Oct 2008 12:52:12 +0200 Message-ID: <48F9BFDC.6080108@redhat.com> References: <82FBE772-34D5-4F2B-8DEC-82E41F15FC06@suse.de> <20081017172511.GC22408@yukikaze> <7605E571-6852-4944-81F0-8B6DCC50CBEB@suse.de> <20081017181727.GB24525@yukikaze> <20081018072110.GA5667@nik-comp.linuxbox.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Sheng Yang , KVM list , Andrea Arcangeli , nikola.ciprich@linuxbox.cz To: Nikola Ciprich Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35716 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751188AbYJRKwl (ORCPT ); Sat, 18 Oct 2008 06:52:41 -0400 In-Reply-To: <20081018072110.GA5667@nik-comp.linuxbox.cz> Sender: kvm-owner@vger.kernel.org List-ID: Nikola Ciprich wrote: > Hi, > I've been stumbling to same problems building kernel packages for our distro - > I've made small patches which allow enabling MMU notifier and also preempt notifiers > on kernel with KVM disabled (to allow building external always fresh KVM). > I'm attaching those, hope it helps. > Actually, Avi, do You thing souch patches could be pushed upstream? It doesn't > hurt anything to have such a choice no? > More choices to confuse users; and these choices aren't helpful for ordinary builds (which don't have external modules). You can always select KVM and ignore the modules generated. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.