Re:32-bit x86 Position Independent Code – It's That Bad
by caf on Wednesday April 15, 2015 @06:17AM
(#9379949)
You don't need to run mincore() on target pids - you just need to write a tool that opens(O_RDONLY) and mmaps(PROT_READ) each library file, then calls mincore() on each page in the mapping to find out which pages of the library are loaded shared.
The results of mincore() in one process with a shared mapping of a file are enough to tell you how much of that file is loaded shared system-wide.
Re:32-bit x86 Position Independent Code – It's That Bad
by zvrba on Thursday April 16, 2015 @03:06AM
(#9386330)
Just found out that physical page information is exposed through /proc: https://www.kernel.org/doc/Documentation/vm/pagemap.txt
Re:32-bit x86 Position Independent Code – It's That Bad
by zvrba on Wednesday April 15, 2015 @06:34AM
(#9379992)
Ah, good point! Though I think I'll do a dlopen on each file to mimic whatever the loader usually does. I'll do it as a weekend-project :)
Unless there's a tool which makes this extremely simple (maybe Intel's pin?), I believe that writing a kernel module is simpler. The module's init function tallies up the pages and writes out the result into the kernel log. Then the module exits.