LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Two unclear places in lockdep-design.txt
@ 2007-02-15  2:36 Pavel Roskin
  0 siblings, 0 replies; only message in thread
From: Pavel Roskin @ 2007-02-15  2:36 UTC (permalink / raw)
  To: linux-kernel, Ingo Molnar

Hello, Ingo!

Many thanks for the lockdep validator!  It has helped me immensely.
However, lockdep-design.txt has been pretty hard to read for me.

It would be great if you find an opportunity to clarify two things in
the documentation.

1) What is a lock dependency?  What does "L1 -> L2" mean?  Does it mean
that L1 should be first or second to be acquired?

2) What is "ever held with hardirqs enabled"?  Does it mean that the
lock was used in the code where hardirqs were enabled, or that it _also_
didn't disable hardirqs by itself (e.g. by spin_lock_irq)?  I suspect
the later is the case.

I wish I could submit a patch for the documentation, but I still don't
understand much of the theory.  Still, I was able to interpret the error
messages in a way that allows me to fix the locking issues in some
drivers.

-- 
Regards,
Pavel Roskin


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-02-15  2:37 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-15  2:36 Two unclear places in lockdep-design.txt Pavel Roskin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).