From: "Xie, Huawei" <huawei.xie@intel.com>
To: "Tao, Zhe" <zhe.tao@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vhost: fix mem share between VM and host
Date: Mon, 11 Apr 2016 06:22:12 +0000 [thread overview]
Message-ID: <C37D651A908B024F974696C65296B57B4C6DEAA3@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1460309332-21981-1-git-send-email-zhe.tao@intel.com>
On 4/11/2016 1:29 AM, Zhe Tao wrote:
>
> +/* Check the share memory in case the QEMU doesn't set the share option
> + * as on for the memory-backend-file object in the QEMU command line.
> + */
> +
> +int
> +vhost_check_mem_shared(struct vhost_device_ctx ctx)
> +{
> + struct virtio_net *dev;
> + struct vhost_virtqueue *vq;
> + int ret = 0;
> +
> + dev = get_device(ctx);
> + if ((dev == NULL) || (dev->mem == NULL))
> + return -1;
> +
> + /* check first virtqueue 0 rxq. */
> + vq = dev->virtqueue[VIRTIO_RXQ];
> + ret = vq->desc[0].next == 0 ? -1 : 0;
> +
> + if (ret)
> + RTE_LOG(ERR, VHOST_CONFIG,
> + "The mem is not shared between VM and host\n");
> +
> + return ret;
> +}
> +
Zhe: This is known to vhost-user users that share=on is a must-to-have
option. I think this isn't an issue.
It is OK if we could do some early check in vhost, however we couldn't
assume the value of vq->desc[0].next.
Check if there is other simple and reliable way.
next prev parent reply other threads:[~2016-04-11 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 17:28 Zhe Tao
2016-04-10 19:44 ` Thomas Monjalon
2016-04-11 6:22 ` Xie, Huawei [this message]
2016-04-11 16:41 ` Yuanhan Liu
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=C37D651A908B024F974696C65296B57B4C6DEAA3@SHSMSX101.ccr.corp.intel.com \
--to=huawei.xie@intel.com \
--cc=dev@dpdk.org \
--cc=zhe.tao@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).