staging: android: describe use of memory barrier on sync.c
Added comments describing the purpose of using write memory barrier in the context of sync_timeline_destory. Signed-off-by: Niv Yehezkel <executerx@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
77870a1b85
commit
296066093b
|
@ -92,6 +92,10 @@ static void sync_timeline_free(struct kref *kref)
|
||||||
void sync_timeline_destroy(struct sync_timeline *obj)
|
void sync_timeline_destroy(struct sync_timeline *obj)
|
||||||
{
|
{
|
||||||
obj->destroyed = true;
|
obj->destroyed = true;
|
||||||
|
/*
|
||||||
|
* Ensure timeline is marked as destroyed before
|
||||||
|
* changing timeline's fences status.
|
||||||
|
*/
|
||||||
smp_wmb();
|
smp_wmb();
|
||||||
|
|
||||||
/*
|
/*
|
||||||
|
|
Loading…
Reference in a new issue