Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030285AbWAXB1q (ORCPT ); Mon, 23 Jan 2006 20:27:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030287AbWAXB1q (ORCPT ); Mon, 23 Jan 2006 20:27:46 -0500 Received: from kanga.kvack.org ([66.96.29.28]:60056 "EHLO kanga.kvack.org") by vger.kernel.org with ESMTP id S1030285AbWAXB1p (ORCPT ); Mon, 23 Jan 2006 20:27:45 -0500 Date: Mon, 23 Jan 2006 20:23:31 -0500 From: Benjamin LaHaise To: Andi Kleen Cc: Ray Bryant , Dave McCracken , Robin Holt , Hugh Dickins , Linux Kernel , Linux Memory Management Subject: Re: [PATCH/RFC] Shared page tables Message-ID: <20060124012331.GK1008@kvack.org> References: <200601240139.46751.ak@suse.de> <200601231853.54948.raybry@mpdtxmail.amd.com> <200601240210.04337.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601240210.04337.ak@suse.de> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1006 Lines: 20 On Tue, Jan 24, 2006 at 02:10:03AM +0100, Andi Kleen wrote: > The randomization is not for cache coloring, but for security purposes > (except for the old very small stack randomization that was used > to avoid conflicts on HyperThreaded CPUs). I would be surprised if the > mmap made much difference because it's page aligned and at least > on x86 the L2 and larger caches are usually PI. Actually, does this even affect executable segments? Iirc, prelinking already results in executables being mapped at the same physical offset across binaries in a given system. An strace seems to confirm that. -ben -- "Ladies and gentlemen, I'm sorry to interrupt, but the police are here and they've asked us to stop the party." Don't Email: . - 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/