From: Richard Henderson <rth@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: 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, 5 Dec 2001 08:58:08 -0800 [thread overview]
Message-ID: <20011205085808.A8634@redhat.com> (raw)
In-Reply-To: <20011204171426.B7982@redhat.com> <15373.33622.236872.92057@napali.hpl.hp.com> <20011204190048.B8179@redhat.com> <20011205.032304.102576056.davem@redhat.com>
In-Reply-To: <20011205.032304.102576056.davem@redhat.com>; from davem@redhat.com on Wed, Dec 05, 2001 at 03:23:04AM -0800
On Wed, Dec 05, 2001 at 03:23:04AM -0800, David S. Miller wrote:
> I don't understand why this is even necessary.
>
> What if the interrupt comes in on another processor. How does this
> return from trap behavior avoid that interrupt modifying the signal
> and/or scheduling state wrt. the current cpu's task?
It doesn't. But it also prevents the IPI from being recognized
until we are back in userland. Apparently DMT had a test case
that failed without disabling interrupts; I didn't see it myself.
r~
next prev parent reply other threads:[~2001-12-05 17:00 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 [this message]
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
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=20011205085808.A8634@redhat.com \
--to=rth@redhat.com \
--cc=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=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