From: Steven Rostedt <rostedt@goodmis.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dwalker@mvista.com, Linus Torvalds <torvalds@osdl.org>,
kus Kusche Klaus <kus@keba.com>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why yield in coredump_wait? [was: Re: Resent: BUG in RT 45-01 when RT program dumps core]
Date: Thu, 19 May 2005 14:05:53 -0400 [thread overview]
Message-ID: <1116525953.4097.15.camel@localhost.localdomain> (raw)
In-Reply-To: <1116524583.21388.299.camel@localhost.localdomain>
On Thu, 2005-05-19 at 18:43 +0100, Alan Cox wrote:
> On Iau, 2005-05-19 at 18:25, Daniel Walker wrote:
> > I've seen a RT yield warning on this yield while running the FUSYN
> > tests .. I can't imagine why it's there either.
>
> Would it not make more sense to kick a task out of hard real time at the
> point it begins dumping core. The core dumping sequence was never
> something that thread intended to execute at real time priority
>
That's what I recommended in an earlier email. I figured I'd wait to
see Ingo's response before sending him any patches. The drop from RT
should probably be after the zap_threads, that way it can kill those
using the same mm right away. Which also goes to say, we should get rid
of that yield.
-- Steve
next prev parent reply other threads:[~2005-05-19 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:36 Resent: BUG in RT 45-01 when RT program dumps core kus Kusche Klaus
2005-05-19 11:56 ` Steven Rostedt
2005-05-19 12:38 ` Serge Noiraud
2005-05-19 13:12 ` Steven Rostedt
2005-05-19 13:37 ` Why yield in coredump_wait? [was: Re: Resent: BUG in RT 45-01 when RT program dumps core] Steven Rostedt
2005-05-19 15:47 ` Lee Revell
2005-05-19 16:03 ` Steven Rostedt
2005-05-19 17:25 ` Daniel Walker
2005-05-19 17:43 ` Alan Cox
2005-05-19 18:05 ` Steven Rostedt [this message]
2005-05-23 7:53 ` Ingo Molnar
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=1116525953.4097.15.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwalker@mvista.com \
--cc=kus@keba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®