From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: MINSTATE_START_SAVE_MIN_PHYS looking very confused
Date: Fri, 06 May 2005 12:08:37 +0000 [thread overview]
Message-ID: <17019.24133.738017.806202@napali.hpl.hp.com> (raw)
While working on the libunwind-enabled Linux kernel, I noticed that
MINSTATE_START_SAVE_MIN_PHYS is loking rather confused. Part of the
problem seems to have been introduced by rja's patch from last
December (it cause "r1" to be setup incorrectly when already in kerenl
mode). However, the bigger issue to me is: given that we have a
separate INIT stack, why bother distinguishing between an INIT that
hits user-level vs. one that hits the kernel. It's not possible to
handle nested INITs anyhow, so why not just simplify that code to
always switch to the INIT stack?
--david
next reply other threads:[~2005-05-06 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 12:08 David Mosberger [this message]
2005-05-06 12:25 ` MINSTATE_START_SAVE_MIN_PHYS looking very confused David Mosberger
2005-05-06 16:15 ` Russ Anderson
2005-05-09 13:34 ` David Mosberger
2005-05-10 4:38 ` Keith Owens
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=17019.24133.738017.806202@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--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