From: "Michael S. Tsirkin" <mst@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: Jason Wang <jasowang@redhat.com>,
wexu@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jfreimann@redhat.com
Subject: Re: [RFC v2] virtio: support packed ring
Date: Tue, 17 Apr 2018 15:17:41 +0300 [thread overview]
Message-ID: <20180417151654-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180417025133.7t7exmizgolr565z@debian>
On Tue, Apr 17, 2018 at 10:51:33AM +0800, Tiwei Bie wrote:
> On Tue, Apr 17, 2018 at 10:11:58AM +0800, Jason Wang wrote:
> > On 2018年04月13日 15:15, Tiwei Bie wrote:
> > > On Fri, Apr 13, 2018 at 12:30:24PM +0800, Jason Wang wrote:
> > > > On 2018年04月01日 22:12, Tiwei Bie wrote:
> [...]
> > > > > +static int detach_buf_packed(struct vring_virtqueue *vq, unsigned int head,
> > > > > + void **ctx)
> > > > > +{
> > > > > + struct vring_packed_desc *desc;
> > > > > + unsigned int i, j;
> > > > > +
> > > > > + /* Clear data ptr. */
> > > > > + vq->desc_state[head].data = NULL;
> > > > > +
> > > > > + i = head;
> > > > > +
> > > > > + for (j = 0; j < vq->desc_state[head].num; j++) {
> > > > > + desc = &vq->vring_packed.desc[i];
> > > > > + vring_unmap_one_packed(vq, desc);
> > > > > + desc->flags = 0x0;
> > > > Looks like this is unnecessary.
> > > It's safer to zero it. If we don't zero it, after we
> > > call virtqueue_detach_unused_buf_packed() which calls
> > > this function, the desc is still available to the
> > > device.
> >
> > Well detach_unused_buf_packed() should be called after device is stopped,
> > otherwise even if you try to clear, there will still be a window that device
> > may use it.
>
> This is not about whether the device has been stopped or
> not. We don't have other places to re-initialize the ring
> descriptors and wrap_counter. So they need to be set to
> the correct values when doing detach_unused_buf.
>
> Best regards,
> Tiwei Bie
find vqs is the time to do it.
--
MST
next prev parent reply other threads:[~2018-04-17 12:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 14:12 [RFC v2] virtio: support packed ring Tiwei Bie
2018-04-10 2:55 ` Jason Wang
2018-04-10 3:21 ` Tiwei Bie
2018-04-13 4:30 ` Jason Wang
2018-04-13 7:15 ` Tiwei Bie
2018-04-17 2:11 ` Jason Wang
2018-04-17 2:17 ` Michael S. Tsirkin
2018-04-17 2:24 ` Jason Wang
2018-04-17 2:37 ` Michael S. Tsirkin
2018-04-17 2:51 ` Tiwei Bie
2018-04-17 12:17 ` Michael S. Tsirkin [this message]
2018-04-17 12:47 ` Tiwei Bie
2018-04-17 14:04 ` Michael S. Tsirkin
2018-04-17 14:56 ` Tiwei Bie
2018-04-17 15:54 ` Michael S. Tsirkin
2018-04-18 1:17 ` Tiwei Bie
2018-04-13 15:22 ` Michael S. Tsirkin
2018-04-14 11:22 ` Tiwei Bie
2018-04-23 5:42 ` Jason Wang
2018-04-23 9:29 ` Tiwei Bie
2018-04-24 0:54 ` Jason Wang
2018-04-24 1:05 ` Michael S. Tsirkin
2018-04-24 1:14 ` Jason Wang
2018-04-24 1:16 ` Tiwei Bie
2018-04-24 1:29 ` Michael S. Tsirkin
2018-04-24 1:37 ` Tiwei Bie
2018-04-24 1:43 ` Michael S. Tsirkin
2018-04-24 1:49 ` Tiwei Bie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180417151654-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tiwei.bie@intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).