Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934058AbYBHGfL (ORCPT ); Fri, 8 Feb 2008 01:35:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752691AbYBHGe7 (ORCPT ); Fri, 8 Feb 2008 01:34:59 -0500 Received: from courier.cs.helsinki.fi ([128.214.9.1]:41440 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752146AbYBHGe6 (ORCPT ); Fri, 8 Feb 2008 01:34:58 -0500 Message-ID: <47ABF7D5.7040406@cs.helsinki.fi> Date: Fri, 08 Feb 2008 08:33:57 +0200 From: Pekka Enberg User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Christoph Lameter CC: Vegard Nossum , Linux Kernel Mailing List , Ingo Molnar , Andi Kleen , Richard Knutsson Subject: Re: [PATCH 1/2] kmemcheck v3 References: <47AB79D4.2070605@gmail.com> <19f34abd0802071412m569e4993kffb4a3af163fa16c@mail.gmail.com> <47ABF715.60407@cs.helsinki.fi> In-Reply-To: <47ABF715.60407@cs.helsinki.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 17 Pekka Enberg wrote: > No. We need to not track the whole page to avoid recursive faults. So > for kmemcheck we absolutely do need cache_cache but we can, of course, > hide that under a alloc_cache() function that only uses the extra cache > when CONFIG_KMEMCHECK is enabled? Btw, one option is to have a new _page flag_ so that we no longer need to look inside struct kmem_cache in the page fault handler. Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/