qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, mlureau@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] Vhost: no more leak QEMU virtual addresses to user backend
Date: Thu, 21 Dec 2017 15:01:25 +0100	[thread overview]
Message-ID: <ee4d8ff5-6a67-6146-1516-1c242787054c@redhat.com> (raw)
In-Reply-To: <20171221055215-mutt-send-email-mst@kernel.org>



On 12/21/2017 04:53 AM, Michael S. Tsirkin wrote:
> On Wed, Dec 20, 2017 at 04:07:41PM +0000, Stefan Hajnoczi wrote:
>> On Tue, Dec 19, 2017 at 07:11:26PM +0100, Maxime Coquelin wrote:
>>> Before this series, QEMU process virtual addresses are sent to the
>>> user backend as user addresses.
>>>
>>> Passing these virtual addresses aren't useful, as the backend doesn't
>>> direct access to QEMU address space.
>>>
>>> It does make sense however for kernel backend, which can access QEMU
>>> address space.
>>>
>>> This series introduce a new enum set by the backend stating whether it
>>> prefers using QEMU Virtual addresses or Guest physical addresses as
>>> User address, and make vhost-user backend to use Guest physical
>>> addresses.
>>>
>>> Maxime Coquelin (3):
>>>    vhost-user: rename VhostUserMemory userspace_addr field to user_addr
>>>    vhost: introduce backend's user address type
>>>    vhost-user: no more leak QEMU virtual addresses to user backend
>>>
>>>   hw/virtio/vhost-backend.c         |  1 +
>>>   hw/virtio/vhost-user.c            |  6 ++++--
>>>   hw/virtio/vhost.c                 | 16 ++++++++++++----
>>>   include/hw/virtio/vhost-backend.h |  6 ++++++
>>>   4 files changed, 23 insertions(+), 6 deletions(-)
>>>
>>> -- 
>>> 2.14.3
>>>
>>
>> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> 
> This makes make check fail. Any idea why?
> 

That's interesting, it fails because the rings aren't initialized with
vhost-user-test (even without my series, but we don't notice).

It fails in vhost_virtqueue_start(), because vq->desc is NULL.

Adding some debug prints shows that vq->desc_phys, vq->avail_phys and 
vq->used_phys are all 0 for both queues.

So when using QEMU VAs as user addresses, vq->desc, vq->used and
vq->avail are translated to a non-NULL address, and it doesn't fail.

Only the multiqueue test returns non-zero and different addresses
between the rings.

I'm looking into it.

Regards,
Maxime

  reply	other threads:[~2017-12-21 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 18:11 [Qemu-devel] [PATCH 0/3] Vhost: no more leak QEMU virtual addresses to user backend Maxime Coquelin
2017-12-19 18:11 ` [Qemu-devel] [PATCH 1/3] vhost-user: rename VhostUserMemory userspace_addr field to user_addr Maxime Coquelin
2017-12-19 18:11 ` [Qemu-devel] [PATCH 2/3] vhost: introduce backend's user address type Maxime Coquelin
2017-12-19 18:11 ` [Qemu-devel] [PATCH 3/3] vhost-user: no more leak QEMU virtual addresses to user backend Maxime Coquelin
2017-12-20 16:07 ` [Qemu-devel] [PATCH 0/3] Vhost: " Stefan Hajnoczi
2017-12-21  3:53   ` Michael S. Tsirkin
2017-12-21 14:01     ` Maxime Coquelin [this message]
2017-12-21 14:16       ` Maxime Coquelin

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=ee4d8ff5-6a67-6146-1516-1c242787054c@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=mlureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).