From: "Vamsi Krishna S ." <vamsi@in.ibm.com>
To: "Gross, Mark" <mark.gross@intel.com>
Cc: "'Erich Focht'" <efocht@ess.nec.de>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org,
"'Bharata B Rao'" <bharata@in.ibm.com>
Subject: Re: PATCH Multithreaded core dump support for the 2.5.14 (and 15) kernel.
Date: Wed, 15 May 2002 12:07:22 +0530 [thread overview]
Message-ID: <20020515120722.A17644@in.ibm.com> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C057B485B@orsmsx111.jf.intel.com>
Erich,
To respond to your specific question, if a thread happens to be in
kernel mode when some other thread is dumping core (capturing
register state of other threads, to be more accurate) then
we would capture the _user mode_ register of that thread from the
bottom of it's kernel stack. GDB will show back trace untill the
thread entered kernel (int 0x80), eip will be pointing to the
instruction after the system call (return address).
--
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5262355 Extn: 3959
Internet: vamsi@in.ibm.com
On Tue, May 14, 2002 at 09:38:28AM -0700, Gross, Mark wrote:
> See attached unit test code. its not very pretty...
>
> These are NOT exhaustive tests, yet they are a reasonable attempt at unit
> testing / exercising the feature to check for stability issues. My stress
> test was to induce core dumps in these test programs while running the IBM
> chat room benchmark. The XMM.c program was written by Rao Bharata as part
> of the 2.4.17 tcore testing. I don't remember who wrote test.c, but ptest.c
> is my fault.
>
> I know that the i386 elf core file note sections only contain the class of
> register data that's restored by __switch_to. So I suppose a kernel thread,
> like the migration_thread, or ksoftirq "could" dump core and GDB could do a
> bt on such a dump. However; these note sections only contain any data that
> can be accessed from a non-privileged processor modes and your mileage will
> vary.
>
> --mgross
>
> > -----Original Message-----
> > From: Erich Focht [mailto:efocht@ess.nec.de]
> > Sent: Tuesday, May 14, 2002 8:36 AM
> > To: mark.gross@intel.com
> > Cc: Linus Torvalds; linux-kernel@vger.kernel.org; Vamsi Krishna S .
> > Subject: Re: PATCH Multithreaded core dump support for the 2.5.14 (and
> > 15) kernel.
> >
> >
> > Hi Mark!
> >
> > Thanks for sending the new patch, I'd be interested in the
> > testprograms :-)
> >
> > BTW: any idea what happens when a thread which is suspended
> > happens to be in
> > kernel mode? Guess this could be possible with 2.5.X... Does
> > gdb handle that?
> >
> > Regards,
> > Erich
> >
> > On Monday 13 May 2002 21:17, you wrote:
> > > The following patch for 2.5.14 kernel, applies cleanly to the 2.5.15
> > > kernel.
> > >
> > > This work has been tested on the 2.5.14 kernel using a few pthread
> > > applications to dump core, from SIGQUIT and SIGSEV. This
> > unit test has been
> > > done on both 2 and 4 way systems. Further, some stress
> > testing has been
> > > done where, the core files have been created while the
> > system is under
> > > schedule stress from the chat room benchmark running while
> > creating the
> > > core files. This implementation seems to be quit stable
> > under a busy
> > > scheduler, YMMV. These test programs are available uppon request ;)
> >
> >
next prev parent reply other threads:[~2002-05-15 6:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 16:38 PATCH Multithreaded core dump support for the 2.5.14 (and 15) kernel Gross, Mark
2002-05-15 6:37 ` Vamsi Krishna S . [this message]
2002-05-15 14:04 ` Pavel Machek
2002-05-15 20:53 ` Mark Gross
2002-05-16 10:11 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 15:44 Gross, Mark
2002-05-17 12:26 Erich Focht
[not found] <59885C5E3098D511AD690002A5072D3C057B485B@orsmsx111.jf.intel.com.suse.lists.linux.kernel>
[not found] ` <20020515120722.A17644@in.ibm.com.suse.lists.linux.kernel>
[not found] ` <20020515140448.C37@toy.ucw.cz.suse.lists.linux.kernel>
[not found] ` <200205152353.g4FNrew30146@unix-os.sc.intel.com.suse.lists.linux.kernel>
2002-05-16 12:54 ` Andi Kleen
2002-05-16 14:13 ` Mark Gross
2002-05-16 17:27 ` Andi Kleen
2002-05-16 17:36 ` Daniel Jacobowitz
2002-05-16 18:08 ` Mark Gross
2002-05-16 21:32 ` Alan Cox
2002-05-16 21:24 ` Robert Love
2002-05-16 18:40 ` Mark Gross
2002-05-13 19:17 Mark Gross
2002-05-14 15:35 ` Erich Focht
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=20020515120722.A17644@in.ibm.com \
--to=vamsi@in.ibm.com \
--cc=bharata@in.ibm.com \
--cc=efocht@ess.nec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=torvalds@transmeta.com \
/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