Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760692AbYAYVmT (ORCPT ); Fri, 25 Jan 2008 16:42:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756960AbYAYVmG (ORCPT ); Fri, 25 Jan 2008 16:42:06 -0500 Received: from terminus.zytor.com ([198.137.202.10]:35921 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755971AbYAYVmF (ORCPT ); Fri, 25 Jan 2008 16:42:05 -0500 Message-ID: <479A5689.80505@zytor.com> Date: Fri, 25 Jan 2008 13:37:13 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Jeremy Fitzhardinge CC: Ingo Molnar , LKML , Andi Kleen , Jan Beulich , Eduardo Pereira Habkost , Ian Campbell , William Irwin , Linus Torvalds Subject: Re: [PATCH 11 of 11] x86: defer cr3 reload when doing pud_clear() References: In-Reply-To: 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: 891 Lines: 22 Jeremy Fitzhardinge wrote: > PAE mode requires that we reload cr3 in order to guarantee that > changes to the pgd will be noticed by the processor. This means that > in principle pud_clear needs to reload cr3 every time. However, > because reloading cr3 implies a tlb flush, we want to avoid it where > possible. It only matters (for a processor which supports PGE) if we actually use the namespace in between. > In huge_pmd_unshare, it is followed by flush_tlb_range, which always > results in a full cr3-reload tlb flush. This one makes me nervous, as it feels like a side effect of implementation, and not a guarantee by design. -hpa -- 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/