From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Why large stack frame for PAL call
Date: Tue, 29 Jun 2004 05:50:15 +0000 [thread overview]
Message-ID: <16609.791.65478.362755@napali.hpl.hp.com> (raw)
In-Reply-To: <200406271740.i5RHeaY24803@unix-os.sc.intel.com>
>>>>> On Sun, 27 Jun 2004 10:42:14 -0700, "Chen, Kenneth W" <kenneth.w.chen@intel.com> said:
Ken> Does anyone know why we need such large stack frame for PAL
Ken> static call? PAL isn't even suppose to touch any stack
Ken> register for static calling convention. Is it for legacy
Ken> reason or something?
Good question. I was able to track the source down to a patch that
was sent to me by Walt Drummond on Aug 11, 1999. The authors listed
in the relevant file (it was called palcall.S back then) were Don
Dugger and Walt Drummond (in this order), so my guess is the code was
originally written by Don. At that time, the primary target for Don
would have been SoftSDV. Perhaps it was to work around a bug in
SoftSDV, though I suspect it's just as likely that the code came about
by a misunderstood/misdocumented PAL-requirement.
Perhaps Don or Asit remember how this came about?
I also cannot find a requirement that would demand allocating 96
stacked registers before making a PAL call and I'd be in favor of
cleaning that up.
--david
next prev parent reply other threads:[~2004-06-29 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 17:42 Why large stack frame for PAL call Chen, Kenneth W
2004-06-29 5:50 ` David Mosberger [this message]
2004-06-29 14:11 ` n0ano
2004-06-29 15:13 ` Chen, Kenneth W
2004-06-29 16:20 ` Mallick, Asit K
2004-06-29 21:43 ` 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=16609.791.65478.362755@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