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: Tue, 15 Apr 2003 23:41:36 -0400 (EDT) [thread overview]
Message-ID: <200304160341.h3G3fa4E028180@sith.maoz.com> (raw)
In-Reply-To: <1050442843.3664.165.camel@localhost> from Robert Love at "Apr 15, 2003 05:40:44 pm"
With the tasklet version, I now have a different problem and don't fully
understand how we got here.
Both CPUs are in snd_pcm_stop, which is a macro. gdb has a hard time with
this and can't reference some of the preprocessor code.
snd_pcm_stop is running for the same card but on different CPUs. How'd
that happen? I thought the tasklet wouldn't run ... oh but it only blocks
itself from running on the local CPU twice
nice
Do I need to use spin_lock_irqsave or spin_lock to protect itself from
running concurrently on different CPUs?
_J
In the new year, Robert Love wrote:
> On Mon, 2003-04-14 at 23:44, Jeremy Hall wrote:
>
> > My quandery is where to put the lock so that both cards will use it. I
> > need a layer that is visible to both and don't fully understand the alsa
> > architecture enough to know where to put it.
>
> OK, I understand you now. :)
>
> What is the relationship between the two things that are conflicting?
>
> Robert Love
>
--
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>
prev parent reply other threads:[~2003-04-16 3:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 18:51 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
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 [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=200304160341.h3G3fa4E028180@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox