From: Stephane Eranian <eranian@frankl.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: PAL entry point
Date: Wed, 17 Apr 2002 18:07:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905474@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905468@msgid-missing>
Christian,
On Wed, Apr 17, 2002 at 07:54:14AM -0700, David Mosberger wrote:
> >>>>> On Wed, 17 Apr 2002 15:09:51 +0200, Christian Hildner <christian.hildner@hob.de> said:
>
> Christian> Stephane, David, do you agree making the symbol
> Christian> pal_entry_point global (included in pal.S)? I would need
> Christian> access to the PAL routines directly from my program
> Christian> without using the provided functions.
>
> I'm not sure that's a good idea. PAL has very particular constraints
> on the environment in which it can be called in. Why aren't the
> normal entry points (ia64_pal_call_static(), ia64_pal_call_stacked(),
> ia64_pal_call_phys_static(), and ia64_pal_call_phys_stacked())
> sufficient?
I don't think it is a good idea because by itself knowing the entry
point value does not allow you to simply call it. If you look
at pal.S, you see that there is much more involved in calling
a PAL procedure, especially for those labeled physical/static.
So I agree with David, that we should instead export the 4 call
stubs that will allow you (with less effort) to call PAL.
--
-Stephane
next prev parent reply other threads:[~2002-04-17 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 14:54 [Linux-ia64] Re: PAL entry point David Mosberger
2002-04-17 18:07 ` Stephane Eranian [this message]
2002-04-22 6:03 ` Christian Hildner
2002-04-24 5:23 ` Christian Hildner
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-105590701905474@msgid-missing \
--to=eranian@frankl.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