[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150206183205.GS21418@twins.programming.kicks-ass.net>
Date: Fri, 6 Feb 2015 19:32:05 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Peter Ujfalusi <peter.ujfalusi@...com>
Cc: Tony Lindgren <tony@...mide.com>, paul@...an.com,
linux-omap@...r.kernel.org, mingo@...hat.com,
linux-kernel@...r.kernel.org, balbi@...com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/2] ARM: omap2+: omap_hwmod: Fix false lockdep warning
On Fri, Feb 06, 2015 at 06:05:32PM +0200, Peter Ujfalusi wrote:
> Certainly looks much simpler, but it adds quite a bit of data to the
> omap_hwmod struct, and we have a _lot_ of them for omap2plus configuration.
>
> ls -al vmlinux
>
> w/o any the lockdep warning fixes:
> 110109168
>
> With my series applied:
> 110112031 (base + 2863)
>
> With setting individual lockdep class:
> 110114275 (base + 5107)
>
> I certainly like the lockdep_set_class() way since it is cleaner, but it adds
> almost double amount of bytes to the kernel.
Yeah, I've never really bothered with data too much, its a debug
feature. So lock_class_key is 8 bytes, and strictly speaking you could
union them over other fields, all we really need is unique addresses, we
don't actually use the storage.
--
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