> On Wed, Nov 17, 2010 at 06:33:13AM +0100, cinap_len...@gmx.de wrote: > > sorry for not being clear. what i ment was that qpc is for the last > > qlock we succeeded to acquire. its *not* the one we are spinning on. > > also, qpc is not set to nil on unlock. > > > Ok, so we set qpctry (qpcdbg?) to qpc before changing qpc? Irrespective > of whether qpc is set or nil? And should qunlock() clear qpc for safety, > or would this just make debugging more difficult?
no. you're very likely to nil out the new qpc if you do that. - erik
