All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cache colour task_structs
Date: 01 Nov 2001 02:43:20 +0100	[thread overview]
Message-ID: <p73668vqn9j.fsf@amdsim2.suse.de> (raw)
In-Reply-To: <3BE050AD.C6D7CE4B@colorfullife.com.suse.lists.linux.kernel> <E15z6HM-0005gW-00@the-village.bc.nu.suse.lists.linux.kernel>
In-Reply-To: Alan Cox's message of "1 Nov 2001 02:02:38 +0100"

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> 
> We need to perturb esp colour too. It might be the right way to do this
> is slab based kernel stacks, it might be that your code is cheaper than
> the cost of getting current the really hard way and we should just add
> random numbers to the initial esp of a task ?

You could do that even today (without slab task_struct) by using a 
random/coloured at fork time value for esp0.  This could just be a static
colour counter that is subtracted.

Just don't forget to teach ptrace and proc WCHAN and oops printing about it; 
they currently use hardcoded stack offsets. It'll also likely break kdb.

-Andi

       reply	other threads:[~2001-11-01  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3BE050AD.C6D7CE4B@colorfullife.com.suse.lists.linux.kernel>
     [not found] ` <E15z6HM-0005gW-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-11-01  1:43   ` Andi Kleen [this message]
2001-11-01  2:18     ` [PATCH] cache colour task_structs Davide Libenzi
2001-11-01  4:42     ` Keith Owens
2001-10-31 19:27 Manfred Spraul
2001-11-01  1:04 ` Alan Cox
2001-11-01 10:49   ` Manfred Spraul

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=p73668vqn9j.fsf@amdsim2.suse.de \
    --to=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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.