From: Adrian Cox <adrian@humboldt.co.uk>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Thomas Sailer <sailer@scs.ch>, linux-kernel@vger.kernel.org
Subject: Re: via82cxxx_audio locking problems
Date: Fri, 21 Sep 2001 08:50:01 +0100 [thread overview]
Message-ID: <3BAAF129.1090104@humboldt.co.uk> (raw)
In-Reply-To: <Pine.LNX.3.96.1010920112905.26319I-100000@mandrakesoft.mandrakesoft.com>
Jeff Garzik wrote:
> On Thu, 20 Sep 2001, Thomas Sailer wrote:
>> Dropping and reacquiring syscall_sem around interruptible_sleep_on
>> in via_dsp_do_read, via_dsp_do_write and via_dsp_drain_playback
>> should solve the problem. Does anyone see a problem with this?
> Is there a possibility of do_read being re-entered during that window?
> I agree its a problem but the solution sounds racy?
What's probably needed is one semaphore to lock read/write and ioctls
that look at the playback engine, and another semaphore to lock accesses
to the AC97 codec. That may be simpler to implement than dropping and
releasing the syscall_sem.
--
Adrian Cox http://www.humboldt.co.uk/
next prev parent reply other threads:[~2001-09-21 7:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 8:39 via82cxxx_audio locking problems Thomas Sailer
2001-09-20 11:33 ` Nicholas Knight
2001-09-20 12:07 ` Adrian Cox
2001-09-20 12:24 ` Nicholas Knight
2001-09-20 13:40 ` André Dahlqvist
2001-09-20 13:41 ` Thomas Sailer
2001-09-21 9:27 ` Thomas Sailer
2001-09-21 12:06 ` André Dahlqvist
2001-09-21 13:01 ` Lockups fixed! (Was: via82cxxx_audio locking problems) André Dahlqvist
2001-09-20 16:33 ` via82cxxx_audio locking problems Jeff Garzik
2001-09-21 7:50 ` Adrian Cox [this message]
2001-09-21 8:36 ` David Chow
2001-09-21 8:50 ` David Chow
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=3BAAF129.1090104@humboldt.co.uk \
--to=adrian@humboldt.co.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sailer@scs.ch \
/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