From: Jeremy Hall <jhall@maoz.com>
To: Robert Love <rml@tech9.net>
Cc: Jeremy Hall <jhall@maoz.com>, linux-mm@kvack.org
Subject: Re: interrupt context
Date: Mon, 14 Apr 2003 17:09:00 -0400 (EDT) [thread overview]
Message-ID: <200304142109.h3EL90YY016047@sith.maoz.com> (raw)
In-Reply-To: <1050346609.3664.55.camel@localhost> from Robert Love at "Apr 14, 2003 02:56:50 pm"
In the new year, Robert Love wrote:
> On Mon, 2003-04-14 at 14:51, Jeremy Hall wrote:
>
> Note if SA_INTERRUPT flag was given to request_irq() then the interrupt
> is a "fast" interrupt and runs with all interrupts disabled on the local
> processor.
>
with 2.5.67-mm2, it is SA_INTERRUPT|SA_SHIRQ and looks like it can call
multiple interrupts at once. I am not sure what SA_SHIRQ does, but this
does not address the case where one CPU holds an interrupt for one card
and the other CPU holds the interrupt for the other card.
I moved the line
rme9652_write(rme9652, RME9652_irq_clear, 0);
to after the snd_pcm_period_elapsed calls in the hopes that they would be
run in interrupt context, but it did not make a difference. The backtrace
looks a little different, but it's still the same crash.
_J
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-04-14 21:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 18:51 interrupt context Jeremy Hall
2003-04-14 18:56 ` Robert Love
2003-04-14 19:32 ` Jeremy Hall
2003-04-14 19:35 ` Robert Love
2003-04-14 21:09 ` Jeremy Hall [this message]
2003-04-14 21:18 ` Robert Love
2003-04-14 21:48 ` Jeremy Hall
2003-04-14 22:57 ` Robert Love
2003-04-15 3:44 ` Jeremy Hall
2003-04-15 4:14 ` Jeremy Hall
2003-04-15 21:40 ` Robert Love
2003-04-15 23:02 ` Jeremy Hall
2003-04-16 3:41 ` Jeremy Hall
2008-03-23 21:44 Interrupt context Codrin Alexandru Grajdeanu
2008-03-24 21:00 ` Christopher Li
2008-03-25 1:34 ` Octavian Purdila
2008-03-25 2:57 ` Christopher Li
2008-03-26 12:43 ` Octavian Purdila
2008-03-26 21:53 ` Christopher Li
[not found] <CA+bLfK5FPqFvU2xy7xKdV4LkAvmY6GAPFrB-4UBzn-cOunQ6Xg@mail.gmail.com>
2012-10-05 8:51 ` interrupt context Iain Fraser
2012-10-05 9:32 ` Borislav Petkov
2012-10-05 10:20 ` Iain Fraser
2012-10-05 10:34 ` Borislav Petkov
2012-10-05 13:27 ` Theodore Ts'o
2012-10-05 14:03 ` Iain Fraser
2012-10-05 18:05 ` anish kumar
2012-10-05 18:15 ` Iain Fraser
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=200304142109.h3EL90YY016047@sith.maoz.com \
--to=jhall@maoz.com \
--cc=linux-mm@kvack.org \
--cc=rml@tech9.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.