Messages in this thread | | | Date | Fri, 22 Apr 2011 09:41:40 +0800 | Subject | Re: [PATCH 1/7] lockdep: Print a nice description of an irq locking issue | From | Yong Zhang <> |
| |
On Thu, Apr 21, 2011 at 10:24 PM, Steven Rostedt <rostedt@goodmis.org> wrote: > On Thu, 2011-04-21 at 21:35 +0800, Yong Zhang wrote: >> On Thu, Apr 21, 2011 at 07:40:29AM -0400, Steven Rostedt wrote: > >> > I >> > could show the entire chain too. >> >> Sure :) > > I talked a little about this with Peter Zijlstra on IRC, and we agreed > that we'll keep this as is until we notice that kernel developers are > still confused with the output.
OK :)
> > The more advanced I make this output, the more likely I'll make a > mistake and show something that is not what actually happens. I wrote a > module to trigger each of these cases and the problems that lockdep can > detect grows exponentially as we make the output more specific. > > I probably should modify the lockdep selftests to add an option to show > the output as well as it triggers errors. This would allow me to make > sure the output still works.
This does make sense to keep things consistent if we have it.
> > But for now, I have other things to work on ;)
If you want, you can show more details on your ideas, maybe I could get some time to finish it :)
Thanks, Yong
-- Only stand for myself
| |