[PATCH 11/12] ppc64: Move fwnmi vectors into trampoline area

[Michael Ellerman]

On Tue, 30 Aug 2005 16:09, Milton D. Miller II wrote:
> Michael Ellerman wrote:
> > The fwnmi vectors can be anywhere < 32 MB, so we need to use a trampoline
> > for them too. We've got plenty of room below 0x3000, so just plonk them
> > in there and the existing trampoline code will do what we want. If we
> > ever run out of space below 0x3000 we can change the code to patch the
> > fwnmi vectors explictly.
>
> 1) Addresses below 0x3000 are reserved by the (processor?) architecture
> to add interrupt vectors.  This patch might collide with them.

Yeah it's reserved up to 0x3000 in the green book. My reasoning was that when 
a chip comes out that uses those addresses we'll know about it and we can 
move the fwmni vectors some where else, in the meantime it's just empty 
space.

> 2) Without making sure the old and new vecotors are at the same place,
> the call may not succeed.
>
> 3) We are going to call rtas to register these vectors again.
>
> I would much prefer we test that rtas handles us calling register again
> with a different address to move the vector addresses.

Do you mean the old and new vectors should be in the same place, or different 
places? If they're in the same place then perhaps we don't even need to 
re-register them?

cheers

-- 
Michael Ellerman
IBM OzLabs

email: michael:ellerman.id.au
inmsg: mpe:jabber.org
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://ozlabs.org/pipermail/linuxppc64-dev/attachments/20050830/c96a7b45/attachment.pgp