Messages in this thread | | | Date | Thu, 10 Jun 2004 14:00:44 -0700 | From | "Randy.Dunlap" <> | Subject | Re: [PATCH][RFC] Spinlock-timeout |
| |
On Thu, 10 Jun 2004 21:24:30 +0200 Jan-Benedict Glaw wrote:
| On Thu, 2004-06-10 13:44:52 -0500, Jake Moilanen <moilanen@austin.ibm.com> | wrote in message <1086893091.3476.37.camel@dyn95394175.austin.ibm.com>: | > On Sat, 2004-06-05 at 15:51, Jan-Benedict Glaw wrote: | > > On Sat, 2004-06-05 15:31:26 -0500, Jake Moilanen <moilanen@austin.ibm.com> | > > wrote in message <1086467486.20906.59.camel@dhcp-client215.upt.austin.ibm.com>: | > > > Here's a patch that will BUG() when a spinlock is held for longer then X | > > > seconds. It is useful for catching deadlocks since not all archs have a | > > > NMI watchdog. | > > I like the idea. However, I don't like touching all arch's Kconfig | > > files. I think it's better to either put this into ./lib/Kconfig (well, | > > doesn't really fit there), ot (even better:) put it into the Debug | > > Kconfig file. | > | > I think you're right that lib/Kconfig would not be the right place, but | > I don't think there is a debug Kconfig. I tried keeping the Kconfig | | Not yet:) Somebody is working towards getting all the different debug | options into a central Kconfig file. This was on LKML some four weeks | ago... | | > additions w/ CONFIG_DEBUG_SPINLOCK. The other option is to make a debug | > Kconfig, but every arch seems pretty different in what they have for | > their debug section. | | As I said, it's been worked on:)
Yes, I'll make a new version soon....
-- ~Randy - 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/
| |