From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrea Arcangeli Subject: Re: Build failure w/o mmu notifiers Date: Fri, 17 Oct 2008 21:25:06 +0200 Message-ID: <20081017192506.GU26399@duo.random> 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=us-ascii Cc: Sheng Yang , KVM list , Avi Kivity To: Alexander Graf Return-path: Received: from mx2.redhat.com ([66.187.237.31]:60606 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751318AbYJRK4h (ORCPT ); Sat, 18 Oct 2008 06:56:37 -0400 Content-Disposition: inline In-Reply-To: <16F9B349-9566-445E-9FF8-A1254AAFDA4F@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Hi Alexander, On Fri, Oct 17, 2008 at 08:36:08PM +0200, 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 is supposed to still build against older kernels that don't have mmu notifier functionality at all regardless of their build config. So it should build on latest kernel with kvm disabled too (as mentioned here, MMU_NOTIFIER isn't explicitly selectable, it gets set implicitly if kvm is selected), if it doesn't it's probably some glitch that needs fixing. Or perhaps if it's not a vanilla kernel you're building against and a third party patch interfering, just wondering. I'll try to reproduce with vanilla mainline to see if something broke, in any case you can post the build failure if the problem persists. Thanks! Andrea