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:51:00 +0200 Message-ID: <48F9BF94.6070608@redhat.com> References: <82FBE772-34D5-4F2B-8DEC-82E41F15FC06@suse.de> <20081017172511.GC22408@yukikaze> <7605E571-6852-4944-81F0-8B6DCC50CBEB@suse.de> <20081017181727.GB24525@yukikaze> <16F9B349-9566-445E-9FF8-A1254AAFDA4F@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Sheng Yang , KVM list , Andrea Arcangeli To: Alexander Graf Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35689 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751039AbYJRKv0 (ORCPT ); Sat, 18 Oct 2008 06:51:26 -0400 In-Reply-To: <16F9B349-9566-445E-9FF8-A1254AAFDA4F@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Alexander Graf wrote: > > So if I don't select kvm in the kernel (either as module or compiled > in) I can't build an external module providing kvm's functionality? > That doesn't seem really useful to me... > The external module hackball should detect that you don't have CONFIG_MMU_NOTIFIERS set and supply some compatibility glue. What error are you seeing? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.