From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: swapping with MMU Notifiers V2 Date: Mon, 11 Feb 2008 10:20:37 +0200 Message-ID: <47B00555.3040501@qumranet.com> References: <20080129145021.GJ7233@v2.random> <20080130185735.GS7233@v2.random> <47A16F99.8060502@qumranet.com> <20080131101519.GG7185@v2.random> <47A1A43D.6020203@qumranet.com> <20080131125842.GL7185@v2.random> <20080131185629.GP7185@v2.random> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net To: Andrea Arcangeli Return-path: In-Reply-To: <20080131185629.GP7185@v2.random> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Andrea Arcangeli wrote: > On Thu, Jan 31, 2008 at 01:58:42PM +0100, Andrea Arcangeli wrote: > >> It might also be something stale in the buildsystem (perhaps a distcc >> of ccache glitch?), I also cleared 1G of ccache just to be sure in >> > > My build problem might have been related to the fact the > kvm-userland/kernel/include directory isn't used by the kernel build > system while building the external module. I did the kvm modifications > to the kvm.git, synching from kvm.git to kvm-userland.git and then > building the external module against a third tree that happen to have > the kvm_* headers too but slightly different. I thought the > kvm-userland/kernel/include directory was used but apparently it isn't > anymore because the way it gets priority is a bit fragile. > It is used; for example it supplies headers that don't exist on older kernels. The problem is likely more subtle. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/