qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: yuanhan.liu@linux.intel.com, qemu-devel@nongnu.org,
	peterx@redhat.com, marcandre.lureau@gmail.com, wexu@redhat.com,
	vkaplans@redhat.com, jfreiman@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/6] vhost-user: Specify and implement device IOTLB support
Date: Thu, 1 Jun 2017 15:04:10 +0800	[thread overview]
Message-ID: <477d61d4-6654-b1fa-fd86-1876737c886e@redhat.com> (raw)
In-Reply-To: <a14b541b-ef48-9531-5697-4b5f213e53d9@redhat.com>



On 2017年05月31日 23:32, Maxime Coquelin wrote:
>>>> [0]:https://gitlab.com/mcoquelin/dpdk-next-virtio/commits/vhost_iotlb_proto_v2 
>>>>
>>>> [1]:https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg00095.html 
>>>>
>>> Overall, this looks good to me. I do think patch 3 isn't a good idea
>>> though, if slave wants something let it request it.
>>>
>>> Need to find out why does vhost in kernel want the used ring iotlb at
>>> start time - especially considering we aren't even guaranteed one entry
>>> covers the whole ring, and invalidates should affect all addresses at
>>> least in theory.
>>>
>>>
>>
>> The reason is probably we want to verify whether or not we could 
>> correctly access used ring in vhost_vq_init_access(). It was there 
>> since vhost_net is introduced. We can think to remove this limitation 
>> maybe.
>
> Even if we remove the limitation on Kernel side, we will still have to
> keep this workaround for compatibility with older kernels. Having done 
> the test, I can confirm it is currently necessary.
>
> Thanks,
> Maxime 

Right, it was probably too late for the change.

Thanks

  reply	other threads:[~2017-06-01  7:04 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
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 [this message]
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=477d61d4-6654-b1fa-fd86-1876737c886e@redhat.com \
    --to=jasowang@redhat.com \
    --cc=jfreiman@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@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).