Nick Piggin writes: > This is an interesting one for me. AFAIKS it is possible to use lwsync for > a full barrier after a successful ll/sc operation, right? (or stop me here > if I'm wrong).
An lwsync would order subsequent loads after the lwarx/ldarx, and subsequent stores after the stcwx./stcdx., which should be good enough. > isync followed by a branch I guess does something like puts a bubble > into the pipeline until the branch retires? So it is probably always > going to cost some cycles. I don't know about "retires", but isync is going to stop following instructions from executing until the outcome of the branch is known. On machines that don't have lwsync we will still want to use isync (since the other alternative would be the full heavyweight sync). Your patch doesn't seem to do that. Paul. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev