[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 06/10] device-core: use atomic_set on .realized property

From: Paolo Bonzini
Subject: Re: [PATCH 06/10] device-core: use atomic_set on .realized property
Date: Wed, 30 Sep 2020 19:44:57 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

On 30/09/20 16:31, Maxim Levitsky wrote:
>> +
>> +        qatomic_set(&dev->realized, value);
>> +        /*
>> +         * Ensure that concurrent users see this update prior to
>> +         * any other changes done by unrealize.
>> +         */
>> +        smp_wmb();
> I''l probably never fully understand where to use read/write/full barrier.
> If I understand corrctly, read barrier prevents reads done by this thread to 
> be reordered,
> by the CPU and write barrier prevents writes done by this CPU to be 
> re-ordered.

I must say that the above is not really satisfactory.  The right thing
to do would be to say which changes are done by unrealize; then you
should make sure that *after* reading something that unrealize could
undo you check if dev->realized is still true.

scsi_device_find is one such case, but I'm not convinced it is enough.


> Both (depending on the macro) usually imply compiler barrier (to avoid 
> compilier re-ordering
> stuff...)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]