From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <paulus@samba.org>
Cc: <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@redhat.com>, <torvalds@transmeta.com>,
<marcelo@conectiva.com.br>, <linux-ia64@linuxia64.org>
Subject: Re: alpha bug in signal handling
Date: Wed, 5 Dec 2001 22:15:50 +0100 [thread overview]
Message-ID: <20011205211550.28098@smtp.wanadoo.fr> (raw)
In-Reply-To: <15374.35262.151232.521493@argo.ozlabs.ibm.com>
In-Reply-To: <15374.35262.151232.521493@argo.ozlabs.ibm.com>
>
>I think David (Mosberger, not Miller :) is right here, and in fact
>this is also wrong on PPC at the moment. However, the worst case is
>that the reschedule or signal delivery will get delayed until the next
>interrupt on that cpu (max 1/HZ seconds). Since it is a pretty narrow
>window for the race I think it would be hard to observe the effect of
>the bug.
Yup, I found that some time ago. I though I even fixed it while hacking
on the return from exception path. The fix has probably been lost along
with some of that experimental stuff I was doing at that time though,
I remember you saying the problem wasn't that big.
Ben.
next prev parent reply other threads:[~2001-12-05 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jepu5xqnva.fsf@sykes.suse.de>
[not found] ` <15372.13000.922405.379605@napali.hpl.hp.com>
[not found] ` <20011204171426.B7982@redhat.com>
[not found] ` <15373.33622.236872.92057@napali.hpl.hp.com>
2001-12-05 3:00 ` alpha bug in signal handling Richard Henderson
2001-12-05 11:23 ` David S. Miller
2001-12-05 16:58 ` Richard Henderson
2001-12-05 20:17 ` David S. Miller
2001-12-05 20:55 ` Paul Mackerras
2001-12-05 21:15 ` Benjamin Herrenschmidt [this message]
2001-12-06 1:09 ` David S. Miller
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=20011205211550.28098@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=paulus@samba.org \
--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