> On 05 Aug 2001 11:29:00 +0200,
> kaih@khms.westfalen.de (Kai Henningsen) wrote:
> >kaos@ocs.com.au (Keith Owens) wrote on 02.08.01 in <22165.996722560@kao2.melbourne.sgi.com>:
> >
> >> The IA64 use of descriptors for function pointers has bitten ksymoops.
> >> For those not familiar with IA64, &func points to a descriptor
> >> containing { &code, &data_context }.
> >
> >That sounds suspiciously like what I remember from PPC. How is this solved
> >on the PPC side?
>
> Best guess, without access to a PPC box, is that it is not solved. Any
> arch where function pointers go via a descriptor will have this
> problem.
>
> PPC users, does /proc/ksyms contain the address of the function code or
> the address of a descriptor which points to the code? It is easy to
> tell, if function entries in /proc/ksyms are close together (8-128
> bytes apart) and do not match the addresses in System.map then PPC has
> the same problem as IA64. If this is true, what is the layout of a PPC
> function descriptor so I can handle that case as well?
It's an address of a function. Verified by matching with the system map.
I'm not sure where to look for what you need, however. I've checked the
ppc arch specific code, but it's not apparent to me what I'm looking for
(sorry, I'm still learning about the kernel's structure). If you can
suggest what/where to look I'll dig it up for you.
-- Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com> "Cats are just autistic Dogs" -- Dr. Tony Attwood- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/