mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <ak@suse.de>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH for 2.6.18rc2] [1/7] i386/x86-64: Don't randomize stack top when...
Date: Tue, 25 Jul 2006 13:48:54 +0200	[thread overview]
Message-ID: <1153828134.8932.27.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200607251338.45215.ak@suse.de>



> > > the 8K was what Intel proposed for 2.4 quite a while ago and has been in
> > > use in linux for years and years... Can you explain why you are saying
> > > 7Kb? throwing away that 1Kb of cache associativity is unfortunate and
> > > shouldn't be done unless there's a good reason, so I'm quite interested
> > > in finding out your reason ;)
> >
> > Well that's what the Intel IA-32 optimization manual says:
> 
> The reason I allowed to disable it is that it is sometimes very useful
> for debugging if you can get 100% reproducible addresses.

that I fully agree with; if you say as user "hey I don't care about
anything but give me no randomization" we should give the user no
randomization.

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com


  reply	other threads:[~2006-07-25 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  9:06 Chuck Ebbert
2006-07-25 11:38 ` Andi Kleen
2006-07-25 11:48   ` Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-25  7:46 Chuck Ebbert
2006-07-25  8:12 ` 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=1153828134.8932.27.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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®