David is correct..this is something I need for a TRACK-like application. Performance numbers aren't that important here, just information on what processes are running, what state they're in, etc. Exactly the kind of things you'd see if you did a TRACK <userid> CMS command.
Many thinks to the list readers for their suggestions, both on and off list. It appears that I can find what I want by first looking in the "_lowcore" area (Linux/include/asm-s390/lowcore.h, just as DB has suggested....) and follow the task list from the current_task pointer.
Thanks again, everybody.
DJ Houston
David Boyes wrote:
On Wednesday, 02/02/2005 at 08:07 CST, Dave Jones <[EMAIL PROTECTED]> wrote:
I apologize for wording my request poorly. What I'm really after is the task or process structure and how to locate the "task list" in memory.....
Somehow I suspect a TRACK add-on in progress....
For 64-bit and 31-bit? I think peeking into Linux control blocks is a Bad Idea. It will be a never-ending battle to be able to find all the pointers, and to detect the layout of the control blocks.
Some of the code in ksymoops might help here, although as you say, it's a moving target. ksymoops has a lot of the important structures defined, and would at least give you a starting point for figuring out what ended up where. You'd then need to figure out where the stack started, and start walking frames from there.
You should also look at the kernel header files (different from the normal /usr/include).
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
