Two fixes for 2.4.19-pre5-ac3
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Alan Cox
Quoted 6 lines
The system call tracking is only used to associate a particular EIP with a particular offset in some binary image. There's no other efficient method to capture the
mmap()calls for these images, for everything running.ptrace()is only really useful for a small number of processes, and is slow. Offline post-analysis isn't possible. There is no API for getting access to this information.Ok, so you have a real reason for dealing with it
pice (another kernel debugger) needs it also, it's not only oprofile.
I think it is a bad idea to remove it. It just means that these programs will access it via System.map instead of an exported symbol. It doesn't change anything, just makes life harder for some people.
Quoted 3 lines
Lets see if we can sort out AFS and the like then come back to that one. I think you may have a valid point. If 2.5 has
EXPORT_SYMBOL_INTERNALit gets a lot easier.
That doesn't help the oprofile users who want to use it in 2.4 now.
-Andi