From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759585AbYDAU6w (ORCPT ); Tue, 1 Apr 2008 16:58:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752870AbYDAU6o (ORCPT ); Tue, 1 Apr 2008 16:58:44 -0400 Received: from mga09.intel.com ([134.134.136.24]:56333 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753132AbYDAU6n (ORCPT ); Tue, 1 Apr 2008 16:58:43 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.25,589,1199692800"; d="scan'208";a="311731595" Message-ID: <47F2A202.1040900@linux.intel.com> Date: Tue, 01 Apr 2008 13:58:42 -0700 From: Arjan van de Ven User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Thomas_Hellstr=F6m?= CC: Andi Kleen , Dave Airlie , linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com Subject: Re: [PATCH] x86: create array based interface to change page attribute References: <1206940788.7250.13.camel@clockmaker.usersys.redhat.com> <87myof8ief.fsf@basil.nowhere.org> <47F098E8.1050605@tungstengraphics.com> <20080331083816.GC29105@one.firstfloor.org> <47F0A988.7010707@tungstengraphics.com> <20080331091829.GD29105@one.firstfloor.org> <47F0C6C2.2000004@tungstengraphics.com> <47F10C62.7040500@linux.intel.com> <47F11443.7050302@tungstengraphics.com> <47F11616.3020403@linux.intel.com> <47F11ED3.40803@tungstengraphics.com> In-Reply-To: <47F11ED3.40803@tungstengraphics.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thomas Hellström wrote: > Given this problem, the previously mentioned use-case, and the fact that > we mostly really use user-space mappings, > Is there a possibility we could add the following functions to Dave's > patch (provided they would work as intended, of course, namely > invalidate / bring back the kernel mapping). sadly there are multiple mappings, both in theory and practice. Especially the _np / _p functions specifically work on only the mapping you specify. For this to work we would need to somehow make a "mark all mappings NP, but please only do the kernel ones" kind of thing. The semantics of that are... lets say messy at best.