[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwfsz6e5oQAdZw-YyYzwJXCPjKJKiLEXxn7ujU7KWX97Q@mail.gmail.com>
Date: Tue, 2 Jul 2013 17:54:30 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Maarten Lankhorst <maarten.lankhorst@...onical.com>,
Dave Airlie <airlied@...il.com>
Subject: Re: [GIT PULL] core/mutexes changes for v3.11: W/W mutex support
On Mon, Jul 1, 2013 at 1:22 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> Please pull the latest core-mutexes-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-mutexes-for-linus
>
> HEAD: 166989e366ffa66108b2f37b870e66b85b2185ad locking-selftests: Handle unexpected failures more strictly
>
> This tree adds support for wound/wait style locks, which the graphics guys
> would like to make use of in the TTM graphics subsystem.
So I pulled this, but I'm not particularly happy with how this (very
unusual) lock pollutes <linux/mutex.h> that pretty much every single
file ends up including.
So I'd really prefer to see the ww_mutex() support split up into
<linux/ww_mutex.h>, rather than making the compiler have to parse and
remember that stuff when 99.99% of all files do not care about it or
need it.
Hmm?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists