[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ilqsl5ba.fsf@redhat.com>
Date: Fri, 29 Apr 2022 09:25:13 +0200
From: Cornelia Huck <cohuck@...hat.com>
To: Jason Wang <jasowang@...hat.com>
Cc: mst <mst@...hat.com>, linux-kernel <linux-kernel@...r.kernel.org>,
virtualization <virtualization@...ts.linux-foundation.org>,
Stefano Garzarella <sgarzare@...hat.com>,
eperezma <eperezma@...hat.com>, Cindy Lu <lulu@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...nel.org>,
Marc Zyngier <maz@...nel.org>,
Halil Pasic <pasic@...ux.ibm.com>
Subject: Re: [PATCH V3 3/9] virtio: introduce config op to synchronize vring
callbacks
On Fri, Apr 29 2022, Jason Wang <jasowang@...hat.com> wrote:
> On Thu, Apr 28, 2022 at 5:13 PM Cornelia Huck <cohuck@...hat.com> wrote:
>>
>> On Mon, Apr 25 2022, Jason Wang <jasowang@...hat.com> wrote:
>>
>> > This patch introduces new virtio config op to vring
>> > callbacks. Transport specific method is required to make sure the
>> > write before this function is visible to the vring_interrupt() that is
>>
>> Which kind of writes? I.e., what is the scope?
>
> Any writes before synchronize_cbs(). Is something like the following better?
>
> The function guarantees that all memory operations before it are
> visible to the vring_interrupt() that is called after it.
Maybe "all memory operations on the queue"?
Powered by blists - more mailing lists