mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Eric Lammerts <eric@lammerts.org>
Cc: arjan@infradead.org, davej@redhat.com, davem@davemloft.net,
	pmarques@grupopie.com, linux-kernel@vger.kernel.org
Subject: Re: Slowdown with randomize_va_space in 2.6.12.2
Date: Fri, 29 Jul 2005 18:20:29 -0700	[thread overview]
Message-ID: <20050729182029.68748c9f.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0507292040530.1819@vivaldi.madbase.net>

Eric Lammerts <eric@lammerts.org> wrote:
>
> 
> On Thu, 7 Jul 2005, Arjan van de Ven wrote:
> > On Wed, 2005-07-06 at 18:12 -0700, Andrew Morton wrote:
> > > Dave Jones <davej@redhat.com> wrote:
> > > > On Transmeta CPUs that probably triggers a retranslation of
> > > > x86->native bytecode, if it thinks it hasn't seen code at that
> > > > address before.
> > >
> > > ouch.   What do we do?  Default to off?  Default to off on xmeta?
> >
> > off-on-xmeta would be my preference; I'll cook up a patch for that.
> 
> It would be nice if a fix for this could get in before 2.6.13 comes
> out.

I agree.

> What about this patch?
> 

It has the virtue of simplicity.  Arjan, were you planning on anything
fancier?

> 
> --- linux-2.6.13-rc4/arch/i386/kernel/cpu/transmeta.c.orig	2005-06-17 15:48:29.000000000 -0400
> +++ linux-2.6.13-rc4/arch/i386/kernel/cpu/transmeta.c	2005-07-29 20:46:54.000000000 -0400
> @@ -76,6 +76,10 @@
>  #define USER686 (X86_FEATURE_TSC|X86_FEATURE_CX8|X86_FEATURE_CMOV)
>          if ( c->x86 == 5 && (c->x86_capability[0] & USER686) == USER686 )
>  		c->x86 = 6;
> +
> +	/* randomize_va_space slows us down enormously;
> +	   it probably triggers retranslation of x86->native bytecode */
> +	randomize_va_space = 0;
>  }
> 
>  static void transmeta_identify(struct cpuinfo_x86 * c)

  reply	other threads:[~2005-07-30  1:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 14:23 Paulo Marques
2005-07-06 19:57 ` David S. Miller
2005-07-06 20:53   ` Dave Jones
2005-07-06 20:58     ` David S. Miller
2005-07-07  1:12     ` Andrew Morton
2005-07-07  2:07       ` David S. Miller
2005-07-07  4:11         ` pmarques
2005-07-07  6:37       ` Arjan van de Ven
2005-07-07  6:41         ` Andrew Morton
2005-07-07  6:46           ` Arjan van de Ven
2005-07-30  0:53         ` Eric Lammerts
2005-07-30  1:20           ` Andrew Morton [this message]
2005-07-30 11:49             ` Arjan van de Ven
2005-07-30 11:55             ` Arjan van de Ven
2005-07-06 21:00   ` Arjan van de Ven

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=20050729182029.68748c9f.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eric@lammerts.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®