search for: ktsan

...M +0000, Mark Rutland wrote: > > For several reasons, it would be beneficial to kill off ACCESS_ONCE() > > tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, > > more obviously document their intended behaviour, and are necessary for tools > > like KTSAN to work correctly (as otherwise reads and writes cannot be > > instrumented separately). > > > > While it's possible to script the bulk of this tree-wide conversion, some cases > > such as the virtio code, require some manual intervention. This series moves > > th...

...M +0000, Mark Rutland wrote: > > For several reasons, it would be beneficial to kill off ACCESS_ONCE() > > tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, > > more obviously document their intended behaviour, and are necessary for tools > > like KTSAN to work correctly (as otherwise reads and writes cannot be > > instrumented separately). > > > > While it's possible to script the bulk of this tree-wide conversion, some cases > > such as the virtio code, require some manual intervention. This series moves > > th...

For several reasons, it would be beneficial to kill off ACCESS_ONCE() tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, more obviously document their intended behaviour, and are necessary for tools like KTSAN to work correctly (as otherwise reads and writes cannot be instrumented separately). While it's possible to script the bulk of this tree-wide conversion, some cases such as the virtio code, require some manual intervention. This series moves the virtio and vringh code over to {READ,WRITE}_ONCE...

For several reasons, it would be beneficial to kill off ACCESS_ONCE() tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, more obviously document their intended behaviour, and are necessary for tools like KTSAN to work correctly (as otherwise reads and writes cannot be instrumented separately). While it's possible to script the bulk of this tree-wide conversion, some cases such as the virtio code, require some manual intervention. This series moves the virtio and vringh code over to {READ,WRITE}_ONCE...

...4, 2016 at 10:25:11AM +0000, Mark Rutland wrote: > For several reasons, it would be beneficial to kill off ACCESS_ONCE() > tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, > more obviously document their intended behaviour, and are necessary for tools > like KTSAN to work correctly (as otherwise reads and writes cannot be > instrumented separately). > > While it's possible to script the bulk of this tree-wide conversion, some cases > such as the virtio code, require some manual intervention. This series moves > the virtio and vringh code...

...k Rutland wrote: >>> For several reasons, it would be beneficial to kill off ACCESS_ONCE() >>> tree-wide, in favour of {READ,WRITE}_ONCE(). These work with aggregate types, >>> more obviously document their intended behaviour, and are necessary for tools >>> like KTSAN to work correctly (as otherwise reads and writes cannot be >>> instrumented separately). >>> >>> While it's possible to script the bulk of this tree-wide conversion, some cases >>> such as the virtio code, require some manual intervention. This series moves &...