| commit | b0a5b83ee0fce9dbf8ff5fe1f8c9ae7dfafe458c | |
| author | Ingo Molnar <mingo@elte.hu> | |
| Tue, 16 Jun 2009 14:11:14 +0000 (16 16:11 +0200) | ||
| committer | Joerg Roedel <joerg.roedel@amd.com> | |
| Wed, 17 Jun 2009 14:26:04 +0000 (17 16:26 +0200) | ||
| tree | f36980eeb5eb2205478a523769b6730a19d9a3cf | treesnapshot (tar.gz zip) |
| parent | c79ee4e466dd12347f112e2af306dca35198458f | commitdiff |
dma-debug: Put all hash-chain locks into the same lock class
Alan Cox reported that lockdep runs out of its stack-trace entries
with certain configs:
BUG: MAX_STACK_TRACE_ENTRIES too low
This happens because there are 1024 hash buckets, each with a
separate lock. Lockdep puts each lock into a separate lock class and
tracks them independently.
But in reality we never take more than one of the buckets, so they
really belong into a single lock-class. Annotate the has bucket lock
init accordingly.
[ Impact: reduce the lockdep footprint of dma-debug ]
Reported-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Alan Cox reported that lockdep runs out of its stack-trace entries
with certain configs:
BUG: MAX_STACK_TRACE_ENTRIES too low
This happens because there are 1024 hash buckets, each with a
separate lock. Lockdep puts each lock into a separate lock class and
tracks them independently.
But in reality we never take more than one of the buckets, so they
really belong into a single lock-class. Annotate the has bucket lock
init accordingly.
[ Impact: reduce the lockdep footprint of dma-debug ]
Reported-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
| lib/dma-debug.c | diffblobblamehistory |