From: "David S. Miller" <davem@redhat.com>
To: paulus@samba.org
Cc: rth@redhat.com, davidm@hpl.hp.com, schwab@suse.de,
linux-ia64@linuxia64.org, marcelo@conectiva.com.br,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: alpha bug in signal handling
Date: Wed, 05 Dec 2001 17:09:53 -0800 (PST) [thread overview]
Message-ID: <20011205.170953.08321842.davem@redhat.com> (raw)
In-Reply-To: <15374.35262.151232.521493@argo.ozlabs.ibm.com>
In-Reply-To: <20011204190048.B8179@redhat.com> <20011205.032304.102576056.davem@redhat.com> <15374.35262.151232.521493@argo.ozlabs.ibm.com>
From: Paul Mackerras <paulus@samba.org>
Date: Thu, 6 Dec 2001 07:55:26 +1100 (EST)
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.
I understand now, thanks. I've fixed up sparc64.
So it's a latency problem, not a correctness problem.
prev parent reply other threads:[~2001-12-06 1:10 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
2001-12-06 1:09 ` David S. Miller [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=20011205.170953.08321842.davem@redhat.com \
--to=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=paulus@samba.org \
--cc=rth@redhat.com \
--cc=schwab@suse.de \
--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