public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] switch_stack position
Date: Thu, 14 Dec 2000 06:44:29 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205836@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205821@msgid-missing>

On Wed, 13 Dec 2000 22:36:46 -0800, 
David Mosberger <davidm@hpl.hp.com> wrote:
>  Keith> One pointer in struct thread, one pointer in switch_stack, ~
>  Keith> 15 instructions (2-3 extra bundles) to set the pointers
>  Keith> during save_switch_stack, load_switch_stack and copy_thread.
>  Keith> Is that too big a change?
>
>It's not the amount of work the change that's involved, it's that the
>change makes no sense whatsoever.  Surely you can find a better
>solution?

I need to look at an arbitrary process and determine its stack state
accurately.  If you can think of an method which does not require
tracking the switch_stack (or current top of stack, it is almost the
same thing) for all processes, let me know.  I looked at this for a
couple of weeks without finding a better solution.



  parent reply	other threads:[~2000-12-14  6:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13  5:03 [Linux-ia64] switch_stack position Keith Owens
2000-12-14  2:56 ` David Mosberger
2000-12-14  3:46 ` Keith Owens
2000-12-14  4:39 ` David Mosberger
2000-12-14  5:13 ` Keith Owens
2000-12-14  6:21 ` David Mosberger
2000-12-14  6:31 ` Keith Owens
2000-12-14  6:36 ` David Mosberger
2000-12-14  6:44 ` Keith Owens [this message]
2000-12-14  6:56 ` David Mosberger
2000-12-14  7:08 ` Keith Owens
2000-12-14  7:20 ` David Mosberger
2000-12-14  7:30 ` Keith Owens
2000-12-14  7:40 ` David Mosberger

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=marc-linux-ia64-105590678205836@msgid-missing \
    --to=kaos@ocs.com.au \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox