On Wed, 2 Feb 2005 08:07:18 -0600, 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.....

> I also don't want to have to install and start any software package on
> the Linux side, if I can help it.

I've been in that dump...  indeed, I tried to debug Linux problems
with dumpscan and vmdumbtl etc. Perry explained that I should write my
macro's such that they will automagically work in TRACK and others as
well. Which makes sense.

As others explained, control block layout in Linux changes.
Compatibility in Linux is on source level, not on control block level.
When you recompile the kernel to include some options, the layout of
the control blocks may change. Fortunately we run the kernel in NSS
and as long as I am the one who generates the NSS, I can keep the
corresponding copy of kerntypes with that NSS. You then take the
output of objdump -g kerntypes and feed that through a pipeline to
generate the control block definitions for your dump tool. You also
write the macro for track and xastor that will format control blocks
in virtual machine memory with the blockdef files to please the human
eye. You also use the System.map for that kernel to find kernel
variables and routines. Portions of this work are not done yet (for
example because of long field names, mixed case, and lack of time).

For some versions of Linux that I looked at, the struct task_struct
entries are chained off the current task at X'0C40'  (note that a
virtual UP also does prefixing).  I suppose that would be the place to
start. I have mainly been looking into memory usage rather than CPU
usage, but you would also find that there (and remember that Linux'
observation of time does not always match the truth as we know it on
VM).

Rob
--
Rob van der Heij                  rvdheij @ gmail.com

----------------------------------------------------------------------
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

Reply via email to