[PATCH] powernv: Use _GLOBAL_TOC for opal wrappers
jk at ozlabs.org
Wed Oct 22 22:12:48 AEDT 2014
>> Currently, we can't call opal wrappers from modules when using the LE
>> ABIv2, which requires a TOC init.
> What happens if we try? Build failure or run time bug?
We'll get an arbitrary memory dereference (two, actually) in the opal
wrappers, when we try to load the opal entry point & return address from
the TOC, as r2 may not point to a valid TOC for the kernel.
>> This change uses the _GLOBAL_TOC() macro (rather than _GLOBAL) for the
>> opal wrappers, so that we can do non-local calls to them.
> Are we doing that now, or we would like to?
We'd like to; although we do EXPORT_SYMBOL on another wrapper
(opal_invalid_call()) already. From the call name though, I figure it's
not in any mission-critical usage :)
More information about the Linuxppc-dev