mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Serge Noiraud <serge.noiraud@bull.net>
Cc: kus Kusche Klaus <kus@keba.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Resent: BUG in RT 45-01 when RT program dumps core
Date: Thu, 19 May 2005 09:12:37 -0400	[thread overview]
Message-ID: <1116508357.15866.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1116506317.17833.34.camel@ibiza.btsn.frna.bull.fr>

On Thu, 2005-05-19 at 14:38 +0200, Serge Noiraud wrote:
> > Ingo,
> > 
> > Did you get my patch to fix the kstop_machine yielding problem?
> > 
> > -- Steve
> 
> Does it solve this problem ? is it the same ? I'm in RT 47-03.
> If yes, I'm interested in this patch.
> ...

Yes it does. Actually, all it does is allow kstopmachine to call yield
without the bug message.  I looked into the logic of kstopmachine, and
it is perfectly fine to call yield there. So I added a rt_yield function
to allow for places that it is OK for a RT task to call yield without
showing that message.

I found my patch here: (It's a -p0 patch)

http://seclists.org/lists/linux-kernel/2005/May/att-2111/rt-yeild.patch__charset_us-ascii


-- Steve




  reply	other threads:[~2005-05-19 13:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:36 kus Kusche Klaus
2005-05-19 11:56 ` Steven Rostedt
2005-05-19 12:38   ` Serge Noiraud
2005-05-19 13:12     ` Steven Rostedt [this message]
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
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=1116508357.15866.12.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=kus@keba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=serge.noiraud@bull.net \
    /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®