From: Daniel Jacobowitz <dan@debian.org>
To: Mark Gross <mgross@unix-os.sc.intel.com>
Cc: linux-kernel@vger.kernel.org, mark.gross@intel.com,
mark@thegnar.org, vamsi@in.ibm.com, efocht@ess.nec.de
Subject: Re: [PATCH] multithreaded coredumps for elf exeecutables for O(1) scheduler
Date: Fri, 10 May 2002 15:06:51 -0400 [thread overview]
Message-ID: <20020510190650.GA1722@nevyn.them.org> (raw)
In-Reply-To: <200205101624.g4AGOSw16928@unix-os.sc.intel.com>
On Fri, May 10, 2002 at 09:24:14AM -0400, Mark Gross wrote:
>
> Attached is my current patch for creating multithreaded core dump files,
> that works with the O(1) scheduler.
>
> This is a continuation of the work posted by Vamsi Krishna back on 3/21/02.
> I'm sorry for the delay. The problem of suspending the other thread
> processes for the duration of the core dump was a challenging problem with
> the O(1) scheduler.
>
> Most of the patch is the same as that posted on 3/21/02 with some minor
> fixes and the rebasing to the 2.5.14 kernel. The interesting bits are in
> the additions to sched.c to pause and resume the thread processes under the
> O(1) scheduler.
>
> Here I'm leveraging the work of Eric Foct for the process migration, to
> temporarily migrate the thread processes I need suspended to a "phantom
> runqueue". This is just an additional run queue that has no cpu. When I'm
> finish with the core dump I migrate them off the phantom run queue and
> continue processing whatever exit processing they do.
>
> I tried a number of approaches to process pausing that didn't quite work
> before I settled on the attached implementation.
That's a very interesting approach... I like it.
> This work has been unit test on a 2 way and 4 way SMP systems with no
> lockups so far. YMMV.
>
> Note: GDB 5.x will work with the core files created with this patch, provided
> the libpthread that gets loaded at gdb debug time is stripped of symbols.
>
> Run strip on your libpthread so files and things should work fine for you.
Or use GDB 5.2.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-10 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 13:24 [PATCH] multithreaded coredumps for elf exeecutables for O(1) scheduler Mark Gross
2002-05-10 19:06 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 17:13 Manfred Spraul
2002-05-10 15:13 ` Mark Gross
2002-05-13 7:35 ` Vamsi Krishna S.
2002-05-13 14:25 ` Mark Gross
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=20020510190650.GA1722@nevyn.them.org \
--to=dan@debian.org \
--cc=efocht@ess.nec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=mark@thegnar.org \
--cc=mgross@unix-os.sc.intel.com \
--cc=vamsi@in.ibm.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