From: "Michael S. Tsirkin" <mst@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: peterx@redhat.com, marcandre.lureau@gmail.com,
vkaplans@redhat.com, jasowang@redhat.com, wexu@redhat.com,
yuanhan.liu@linux.intel.com, qemu-devel@nongnu.org,
jfreiman@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 3/6] vhost: extend ring information update for IOTLB to all rings
Date: Tue, 30 May 2017 21:12:35 +0300 [thread overview]
Message-ID: <20170530210905-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170526142858.19931-4-maxime.coquelin@redhat.com>
On Fri, May 26, 2017 at 04:28:55PM +0200, Maxime Coquelin wrote:
> Vhost-kernel backend need
needs
> to receive IOTLB entry for used ring
> information early, which is done by triggering a miss event on
> its address.
>
> This patch extends this behaviour to all rings information, to be
> compatible with vhost-user backend design.
Why does vhost-user need it though?
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> v2:
> - Revert back to existing behaviour, i.e. only send IOTLB updates
> at ring enablement time, not at ring address setting time (mst).
> - Extend IOTLB misses to all ring addresses, not only used ring.
>
> hw/virtio/vhost.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
> index 6eddb09..7867034 100644
> --- a/hw/virtio/vhost.c
> +++ b/hw/virtio/vhost.c
> @@ -1552,11 +1552,15 @@ int vhost_dev_start(struct vhost_dev *hdev, VirtIODevice *vdev)
> if (vhost_dev_has_iommu(hdev)) {
> hdev->vhost_ops->vhost_set_iotlb_callback(hdev, true);
>
> - /* Update used ring information for IOTLB to work correctly,
> - * vhost-kernel code requires for this.*/
> + /*
> + * Update rings information for IOTLB to work correctly,
> + * vhost-kernel and vhost-user codes require for this.
Better just say "Update ring info for vhost iotlb."
The rest isn't really informative.
> + */
> for (i = 0; i < hdev->nvqs; ++i) {
> struct vhost_virtqueue *vq = hdev->vqs + i;
> vhost_device_iotlb_miss(hdev, vq->used_phys, true);
> + vhost_device_iotlb_miss(hdev, vq->desc_phys, true);
> + vhost_device_iotlb_miss(hdev, vq->avail_phys, true);
So I don't remember why does vhost in kernel want miss on used
at start time.
Jason, could you comment on this please?
> }
> }
> return 0;
> --
> 2.9.4
next prev parent reply other threads:[~2017-05-30 18:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 14:28 [Qemu-devel] [PATCH v2 0/6] vhost-user: Specify and implement device IOTLB support Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 1/6] vhost: propagate errors in vhost_device_iotlb_miss() Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 2/6] vhost: rework IOTLB messaging Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 3/6] vhost: extend ring information update for IOTLB to all rings Maxime Coquelin
2017-05-30 18:12 ` Michael S. Tsirkin [this message]
2017-05-30 21:06 ` Maxime Coquelin
2017-05-30 21:11 ` Maxime Coquelin
2017-05-31 15:20 ` Maxime Coquelin
2017-06-01 13:55 ` Michael S. Tsirkin
2017-06-01 13:54 ` Michael S. Tsirkin
2017-05-31 8:48 ` Jason Wang
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 4/6] vhost-user: add vhost_user to hold the chr Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 5/6] vhost-user: add slave-req-fd support Maxime Coquelin
2017-05-30 18:17 ` Michael S. Tsirkin
2017-05-30 21:26 ` Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 6/6] spec/vhost-user spec: Add IOMMU support Maxime Coquelin
2017-05-30 18:08 ` Michael S. Tsirkin
2017-05-30 16:15 ` [Qemu-devel] [PATCH v2 0/6] vhost-user: Specify and implement device IOTLB support Maxime Coquelin
2017-05-30 18:20 ` Michael S. Tsirkin
2017-05-31 8:33 ` Jason Wang
2017-05-31 15:32 ` Maxime Coquelin
2017-06-01 7:04 ` Jason Wang
2017-06-01 8:39 ` Maxime Coquelin
2017-06-01 13:59 ` Michael S. Tsirkin
2017-06-02 5:53 ` Jason Wang
2017-06-02 15:24 ` Michael S. Tsirkin
2017-06-05 8:51 ` Jason Wang
2017-06-05 15:08 ` Michael S. Tsirkin
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=20170530210905-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreiman@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkaplans@redhat.com \
--cc=wexu@redhat.com \
--cc=yuanhan.liu@linux.intel.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).