On Tue, 12 Feb 2008, Andi Kleen wrote:I do agree that kgdb and watchdogs aren't like to work well together. And I don't think you can sanely expect to not have a "disable lockup detection" when you start poking around with kgdb. We also just have to expect that time will also stop while sometbody is messing around with kgdb. So I don't dispute that any kernel debugger will *always* be intrusive in those ways. That's pretty inevitable. I just think the code itself can try to avoid hooking into various places all over the map. Linus --
| Greg Kroah-Hartman | [PATCH 027/196] tifm: Convert from class_device to device for TI flash media |
| Kok, Auke | Re: Linux 2.6.21-rc1 |
| Trent Piepho | Re: [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Arjan van de Ven | Re: [GIT]: Networking |
| Ingo Molnar | Re: [PATCH 01/10] x86: add Kconfig entry for DMA-API debugging |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
