From: linkerndbg@gmail.com (linkerndbg)
To: kernelnewbies@lists.kernelnewbies.org
Subject: reading a core's current task from memory
Date: Sun, 5 Jun 2011 16:38:03 +0200 [thread overview]
Message-ID: <BANLkTinUqGz9_YWCr9954R=OZB3++cFwkw@mail.gmail.com> (raw)
Hi dear list members,
I'm maintaining a Linux kernel debugger through jtag that has been
doing quite well on unicore/SH4 systems so far, now I'd like to
support ARM/SMP systems and do some improvements: I'm looking for a
simple way to know which is the current task executing on one each
core by accessing memory from jtag. Knowing a core's current when it
is running kernel core is easy as the sp registers gives direct access
to the current thread_info, now suppose a core is running a usermode
code page, then sp and pc are virtual memory.
through the jtag interface I can access any symbol which offset I know
from the vmlinux symbol table, and any field which offset is not
dependent of the configure options for a given kernel version. Sadly I
can't easily access the per_cpu runqueues and the rq->curr field this
way.
I'd be grateful for any suggestion as of how to do !
many thanks,
M.
reply other threads:[~2011-06-05 14:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTinUqGz9_YWCr9954R=OZB3++cFwkw@mail.gmail.com' \
--to=linkerndbg@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).