From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266573AbUGKL4w (ORCPT ); Sun, 11 Jul 2004 07:56:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266575AbUGKL4w (ORCPT ); Sun, 11 Jul 2004 07:56:52 -0400 Received: from mx1.redhat.com ([66.187.233.31]:10117 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S266573AbUGKL4v (ORCPT ); Sun, 11 Jul 2004 07:56:51 -0400 Date: Sun, 11 Jul 2004 07:56:10 -0400 (EDT) From: Ingo Molnar X-X-Sender: mingo@devserv.devel.redhat.com To: Andi Kleen cc: linux-kernel@vger.kernel.org, Andrew Morton Subject: Re: serious performance regression due to NX patch In-Reply-To: Message-ID: References: <2giKE-67F-1@gated-at.bofh.it> <2gIc8-6pd-29@gated-at.bofh.it> <2gJ8a-72b-11@gated-at.bofh.it> <2gJhY-776-21@gated-at.bofh.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 11 Jul 2004, Andi Kleen wrote: > > +#ifdef __i386__ > > Won't do on x86-64. well on x86-64 'non-executable' really means non-executable, and always did, right? (and this is completely separate from the issue of whether the process stack is executable or not. This is about x86 that didnt enforce the vma's protection bit.) Ingo