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. -- Andriy GaponReceived on Fri Dec 02 2011 - 09:06:01 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:21 UTC