From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 3/5] Dont map PAL memory if physicall calls are going to be made
Date: Wed, 13 Dec 2006 02:00:40 +0000 [thread overview]
Message-ID: <20061213020039.GC22902@verge.net.au> (raw)
In-Reply-To: <20061023090334.467483535@tabatha.lab.ultramonkey.org>
On Tue, Oct 24, 2006 at 02:47:38PM -0500, Jack Steiner wrote:
> On Mon, Oct 23, 2006 at 05:48:43PM +0900, Horms wrote:
> > There seems to be no reason to map the PAL code into memory if
> > physical calls are going to be made.
>
>
> If you don't map PAL, I assume that all PAL calls are going to be made in
> physical addressing mode. However, I don't see any code that actually forces
> PAL calls to be made in physical addressing mode. Is that your intent?
> Don't you also need to save the PAL start address as a physical address.
> See the call to ia64_pal_handler_init().
Thanks. On furtuther investigation I think that this patch is bogus.
I will remove it from the series.
> In addition, it looks like slave cpus still call efi_map_pal_code()
> to map PAL - see start_secondary().
Just for the record, that itself is easy enough to get around by
checking for efi.mapped in efi_map_pal_code() or start_secondary().
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
prev parent reply other threads:[~2006-12-13 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 8:48 [patch 3/5] Dont map PAL memory if physicall calls are going to be made Horms
2006-10-24 19:47 ` Jack Steiner
2006-10-25 7:12 ` Horms
2006-12-13 2:00 ` Horms [this message]
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=20061213020039.GC22902@verge.net.au \
--to=horms@verge.net.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