From: Andi Kleen <ak@linux.intel.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Len Brown <len.brown@intel.com>,
Robert Moore <robert.moore@intel.com>
Subject: Re: [PATCH 2/4] acpi: add real mutex function calls
Date: Sat, 16 Aug 2008 00:16:15 +0200 [thread overview]
Message-ID: <48A6002F.6070706@linux.intel.com> (raw)
In-Reply-To: <1218831242-27618-3-git-send-email-dwalker@mvista.com>
Daniel Walker wrote:
> Instead of re-using semaphores for the mutex operation, I've
> added usage of the kernel mutex for the acpi os mutex
> implementation.
This still implies that we'll get lockdep warnings if the AML
does something dodgy with mutexes, right?
I don't like that. We cannot generally fix the AML, the only
way would be to time out on a deadlock and let it handle that.
Also it's not that we don't get enough ACPI reports already.
Is there a way to just turn lockdep always off for these mutexes?
-Andi
next prev parent reply other threads:[~2008-08-15 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 20:14 [PATCH 0/4] acpi semaphore removal v3 Daniel Walker
2008-08-15 20:14 ` [PATCH 1/4] add mutex_lock_timeout() Daniel Walker
2008-08-15 20:14 ` [PATCH 2/4] acpi: add real mutex function calls Daniel Walker
2008-08-15 20:14 ` [PATCH 3/4] acpi: add lockdep magic Daniel Walker
2008-08-15 20:14 ` [PATCH 4/4] acpi: semaphore removal Daniel Walker
2008-08-15 22:17 ` Andi Kleen
2008-08-16 0:18 ` Daniel Walker
2008-08-16 2:06 ` Andi Kleen
2008-08-16 4:15 ` Daniel Walker
2008-08-15 22:16 ` Andi Kleen [this message]
2008-08-15 23:10 ` [PATCH 2/4] acpi: add real mutex function calls Daniel Walker
2008-08-16 2:16 ` Andi Kleen
2008-08-16 4:11 ` Daniel Walker
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 18:59 [PATCH 1/4] mutex: add mutex_lock_timeout() Daniel Walker
2008-08-26 18:59 ` [PATCH 2/4] acpi: add real mutex function calls Daniel Walker
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=48A6002F.6070706@linux.intel.com \
--to=ak@linux.intel.com \
--cc=dwalker@mvista.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.moore@intel.com \
/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.