Re: [patch 3/5] Dont map PAL memory if physicall calls are going to be made

[Horms <horms@verge.net.au>]

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. 

I was thinking that making the SAL calls physical would do this,
but perhaps it is not sufficient.

http://marc.theaimsgroup.com/?l=linux-ia64&m\x116159434527220&w=2
http://marc.theaimsgroup.com/?l=linux-ia64&m\x116159434413928&w=2

> 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().
> 
> In addition, it looks like slave cpus still call efi_map_pal_code()
> to map PAL - see start_secondary().

Thanks, I will look into that code and get back to you.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/