From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Dmitry Torokhov" <dtor@insightbb.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Matt Mackall" <mpm@selenic.com>,
rlove@rlove.org, linux-kernel@vger.kernel.org,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: 2.6.21-mm2: HDAPS? BUG: at kernel/mutex.c:311
Date: Sat, 12 May 2007 11:15:43 +0530 [thread overview]
Message-ID: <a781481a0705112245u356759dcm9a550e432ed178fd@mail.gmail.com> (raw)
In-Reply-To: <200705120112.52859.dtor@insightbb.com>
Hi Dmitry,
On 5/12/07, Dmitry Torokhov <dtor@insightbb.com> wrote:
> On Friday 11 May 2007 20:53, Andrew Morton wrote:
> > Ho hum. I suppose a suitable workaround would be to convert hdaps_mtx back
> > into a semaphore. ug.
>
> Actually I was looking for victimes^Wvolunteers to test the patch below.
> It gets rid of _trylock business.
Ah! You just beat me here, and your patch is definitely better.
I was wondering why this driver wanted to use a mutex (previously the
semaphore) to synchronize between process and interrupt context in the
first place. Most of the code in here uses synchronous delays so never
sleeps anyway, but then unfortunately it does a weird
repeated-waiting-hardware-status-register-check thingy in its .probe()
which meant a straightforward mutex -> spinlock wasn't possible.
So then made a patch pushing off the poll to keventd workqueue, when
I saw your mail that does exactly the same, but wrapped about in the
generic input-polldev infrastructure! It's barely 12 days old in mainline --
no wonder I didn't know about it. Seems to be good-looking code!
Thanks,
Satyam
next prev parent reply other threads:[~2007-05-12 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 0:21 Matt Mackall
2007-05-12 0:53 ` Andrew Morton
2007-05-12 1:17 ` Andrew Morton
2007-05-12 5:12 ` Dmitry Torokhov
2007-05-12 5:45 ` Satyam Sharma [this message]
2007-05-14 2:57 ` Dmitry Torokhov
2007-05-14 3:40 ` Satyam Sharma
2007-05-26 20:43 ` Cédric Augonnet
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=a781481a0705112245u356759dcm9a550e432ed178fd@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dtor@insightbb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=rlove@rlove.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
all inboxes | Powered by JetHome®