Messages in this thread | | | Date | Fri, 22 Jul 2011 15:34:37 -0700 | Subject | Re: [PATCH v3 2/2] Make hard lockup detection use timestamps | From | ZAK Magnus <> |
| |
On Fri, Jul 22, 2011 at 12:53 PM, Don Zickus <dzickus@redhat.com> wrote:
> So I played with the hardlockup case and I kinda like the timestamp thing. > It seems to give useful data. In fact I feel like I can shrink the > hardlockup window, run some tests and see where the latencies are in a > system. The patch itself I think is ok, I'll review on Monday or Tuesday > when I get some more free time. > > However, I ran the softlockup case and the output was a mess. I think > rcu_sched stalls were being detected and as a result it was NMI dumping > stack traces for all cpus. I can't tell if it was your patch or some > uncovered bug. > > I'll dig into on Monday. Not sure if you were able to see that. > > Thanks, > Don > I'm not sure what you mean. One problem could be the wording I used. For the soft stalls I just called it LOCKUP, mostly to be very showy in order to cover that case where it's unclear what exactly is happening. This doesn't do much to distinguish soft and hard lockups, and I see LOCKUP otherwise seems to refer to hard lockup, so maybe that's misleading. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |