All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@redhat.com>
To: davidm@hpl.hp.com
Cc: suresh.b.siddha@intel.com, jun.nakajima@intel.com,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: serious performance regression due to NX patch
Date: Sun, 11 Jul 2004 08:38:03 +0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0407110437310.26065@devserv.devel.redhat.com> (raw)
In-Reply-To: <200407100528.i6A5SF8h020094@napali.hpl.hp.com>


On Fri, 9 Jul 2004, David Mosberger wrote:

> The "No eXecute patch for x86" causes a serious exec() performance
> degradation on ia64 since it ends up incorrectly turning on the execute
> protection on all segments (since most ia64 binaries don't have a
> gnu_stack program-header).
> 
> The patch below fixes the problem by turning on VM_EXEC and VM_MAYEXEC
> only if VM_DATA_DEFAULT_FLAGS mentions them.  Note that on ia64, the
> value of VM_DATA_DEFAULT_FLAGS depends on the personality (to support
> x86 binaries) and hence I had to move the setting of "def_flags" down a
> bit to a point after SET_PERSONALITY() has been done.
> 
> Please apply.

ok, agreed. I'll check that it still does the right thing on x86.

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@redhat.com>
To: davidm@hpl.hp.com
Cc: suresh.b.siddha@intel.com, jun.nakajima@intel.com,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: serious performance regression due to NX patch
Date: Sun, 11 Jul 2004 04:38:03 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0407110437310.26065@devserv.devel.redhat.com> (raw)
In-Reply-To: <200407100528.i6A5SF8h020094@napali.hpl.hp.com>


On Fri, 9 Jul 2004, David Mosberger wrote:

> The "No eXecute patch for x86" causes a serious exec() performance
> degradation on ia64 since it ends up incorrectly turning on the execute
> protection on all segments (since most ia64 binaries don't have a
> gnu_stack program-header).
> 
> The patch below fixes the problem by turning on VM_EXEC and VM_MAYEXEC
> only if VM_DATA_DEFAULT_FLAGS mentions them.  Note that on ia64, the
> value of VM_DATA_DEFAULT_FLAGS depends on the personality (to support
> x86 binaries) and hence I had to move the setting of "def_flags" down a
> bit to a point after SET_PERSONALITY() has been done.
> 
> Please apply.

ok, agreed. I'll check that it still does the right thing on x86.

	Ingo

  reply	other threads:[~2004-07-11  8:38 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-10  5:28 serious performance regression due to NX patch David Mosberger
2004-07-10  5:28 ` David Mosberger
2004-07-11  8:38 ` Ingo Molnar [this message]
2004-07-11  8:38   ` Ingo Molnar
2004-07-11  9:39   ` Ingo Molnar
2004-07-11  9:39     ` Ingo Molnar
2004-07-11  9:52     ` Ingo Molnar
2004-07-11  9:52       ` Ingo Molnar
2004-07-11 10:02       ` Andrew Morton
2004-07-11 10:02         ` Andrew Morton
2004-07-11 12:19         ` Matthew Wilcox
2004-07-11 12:19           ` Matthew Wilcox
2004-07-11 10:22       ` Christoph Hellwig
2004-07-11 10:22         ` Christoph Hellwig
2004-07-11 12:38       ` Jakub Jelinek
2004-07-11 12:38         ` Jakub Jelinek
2004-07-12 18:08         ` Ingo Molnar
2004-07-12 18:08           ` Ingo Molnar
2004-07-12 18:24           ` Christoph Hellwig
2004-07-12 18:24             ` Christoph Hellwig
2004-07-12 18:29             ` Ingo Molnar
2004-07-12 18:29               ` Ingo Molnar
2004-07-12 19:10               ` David Mosberger
2004-07-12 19:10                 ` David Mosberger
2004-07-12 19:54                 ` Ingo Molnar
2004-07-12 19:54                   ` Ingo Molnar
2004-07-12 20:08                   ` David Mosberger
2004-07-12 20:08                     ` David Mosberger
2004-07-12 20:17           ` Linus Torvalds
2004-07-12 20:17             ` Linus Torvalds
2004-07-12 20:21             ` David Mosberger
2004-07-12 20:21               ` David Mosberger
2004-07-12 20:24             ` David Mosberger
2004-07-12 20:24               ` David Mosberger
2004-07-13  4:23               ` Ingo Molnar
2004-07-13  4:23                 ` Ingo Molnar
2004-07-13  5:23                 ` David Mosberger
2004-07-13  5:23                   ` David Mosberger
2004-07-13 16:05                 ` Mark Haverkamp
2004-07-13 16:05                   ` Mark Haverkamp
2004-07-13 16:49                   ` Daniel McNeil
2004-07-13 16:49                     ` Daniel McNeil
2004-07-14 18:36                     ` [PATCH] mmap PROT_NONE fix (was Re: serious performance regression Daniel McNeil
2004-07-14 18:36                       ` [PATCH] mmap PROT_NONE fix (was Re: serious performance regression due to NX patch) Daniel McNeil
2004-07-17  0:06                   ` serious performance regression due to NX patch David Mosberger
2004-07-17  0:06                     ` David Mosberger
2004-07-17  1:39                     ` Linus Torvalds
2004-07-17  1:39                       ` Linus Torvalds
2004-07-17  4:37                       ` David Mosberger
2004-07-17  4:37                         ` David Mosberger
2004-07-13  3:58             ` Ingo Molnar
2004-07-13  3:58               ` Ingo Molnar
2004-07-17  0:35     ` David Mosberger
2004-07-17  0:35       ` David Mosberger
     [not found] <2giKE-67F-1@gated-at.bofh.it>
     [not found] ` <2gIc8-6pd-29@gated-at.bofh.it>
     [not found]   ` <2gJ8a-72b-11@gated-at.bofh.it>
     [not found]     ` <2gJhY-776-21@gated-at.bofh.it>
2004-07-11 10:09       ` Andi Kleen
2004-07-11 11:56         ` Ingo Molnar
2004-07-11 12:43           ` Andi Kleen
     [not found]       ` <2gJrv-7kp-5@gated-at.bofh.it>
     [not found]         ` <2gLD2-qn-3@gated-at.bofh.it>
2004-07-11 13:38           ` Andi Kleen
2004-07-11 14:04             ` Matthew Wilcox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.58.0407110437310.26065@devserv.devel.redhat.com \
    --to=mingo@redhat.com \
    --cc=akpm@osdl.org \
    --cc=davidm@hpl.hp.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.