From: Richard Henderson <rth@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: alpha bug in signal handling
Date: Wed, 05 Dec 2001 16:58:08 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805622@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805617@msgid-missing>
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 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 11:23 [Linux-ia64] Re: alpha bug in signal handling 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=marc-linux-ia64-105590698805622@msgid-missing \
--to=rth@redhat.com \
--cc=linux-ia64@vger.kernel.org \
/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