On 12/2/11 5:05 AM, Andriy Gapon wrote:
on 02/12/2011 06:36 John Baldwin said the following:
Ah, ok (I had thought SCHEDULER_STOPPED was going to always be true when kdb was
active). But I think these two changes should cover critical_exit() ok.
I attempted to start a discussion about this a few times already :-)
Should we treat kdb context the same as SCHEDULER_STOPPED context (in the
current definition) ? That is, skip all locks in the same fashion?
There are pros and contras.
kdb should not block on locks, no. Most debugger commands should not go
near locks anyway unless they are intended to carefully modify the
existing system in a safe manner (such as the 'kill' command which
should only be using try locks and fail if it cannot safely post the
signal).
--
John Baldwin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
