Hi Longman,
OK, so, you are from the point of view of the CPU (the lock word value it read last time)
doing state transition in the uncontended scenario:
[1]: Old lock word value (this CPU read it last time) ---> New lock word value
I'm from the point of view of the current lock word possible value that its state is
transited to the new lock word possible value (I don't think I'm the only one from
this point of view when reading the qspinlock code ;-).
[2]: Current lock word possible value ---> New lock word possible value
I'm fine to keep the view of [1] in the current code and get [2] as the backup.
I'll send out a v2 with just two minor comments' fixes.