From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Questions on the stack for IA64
Date: Tue, 13 Apr 2004 17:24:45 +0000 [thread overview]
Message-ID: <200404131724.i3DHOiF18600@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040413051722.84368.qmail@web61202.mail.yahoo.com>
>>>>> Luck, Tony wrote on Tuesday, April 13, 2004 9:26 AM
> >Rahul Chaturvedi wrote on Monday, April 12, 2004 10:17 PM
> >d.) The pfs register seems to point to a location in
> >0xcxxxxxxxxxxxxxxx. Shouldn't this point to some
> >accessible memory location (from usermode)?
>
> someone else can take this one?
ar.pfs is not a memory address pointer. See section 3.1.8.10 of
ia64 software developer's manual, volume 1 for proper way to
decode that register (FYI, bit [63-62] is previous privilege
level, which is 3 in the above case).
- Ken
next prev parent reply other threads:[~2004-04-13 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 5:17 Questions on the stack for IA64 Rahul Chaturvedi
2004-04-13 16:25 ` Luck, Tony
2004-04-13 17:24 ` Chen, Kenneth W [this message]
2004-04-14 5:05 ` Rahul Chaturvedi
2004-04-14 5:19 ` David Mosberger
2004-04-14 5:29 ` Ian Wienand
2004-04-14 5:34 ` Rahul Chaturvedi
2004-04-14 16:06 ` Luck, Tony
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=200404131724.i3DHOiF18600@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.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