From: Daniel Walker <dwalker@mvista.com>
To: john cooper <john.cooper@timesys.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: RT and Signals
Date: 11 Apr 2005 11:37:36 -0700 [thread overview]
Message-ID: <1113244656.30553.55.camel@dhcp153.mvista.com> (raw)
In-Reply-To: <425ABC01.2020100@timesys.com>
On Mon, 2005-04-11 at 11:03, john cooper wrote:
> Daniel Walker wrote:
> > I'm not sure if this has changed at all in recent RT patches, but I've
> > noticed several issues popping up that are related to the timer
> > interrupt sending signals...
>
> I've also seen BUG asserts kicking in on PPC (40-04-ish) in
> signal delivery [actual receipt] paths. These have only been
> under fairly heavy load conditions and presumably is hitting
> an infrequent path in force_sig_info() IIRC. Haven't had the
> time yet to resolve these but they are on the list.
Ingo's solution was to remove the signal delivery from the timer
interrupt altogether. Which I don't know if that's acceptable. It seems
like there is a never ending stream of bugs related to this..
Daniel
prev parent reply other threads:[~2005-04-11 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 17:14 Daniel Walker
2005-04-11 18:03 ` john cooper
2005-04-11 18:37 ` Daniel Walker [this message]
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=1113244656.30553.55.camel@dhcp153.mvista.com \
--to=dwalker@mvista.com \
--cc=john.cooper@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®