From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linhaifeng <haifeng.lin@huawei.com>
Cc: qemu-devel@nongnu.org, n.nikolaev@virtualopensystems.com,
jerry.lilijun@huawei.com
Subject: [Qemu-devel] vhost-user: VHOST_SET_MEM_TABLE, VHOST_SET_VRING_CALL need a reply?
Date: Wed, 17 Sep 2014 11:38:15 +0300 [thread overview]
Message-ID: <20140917083815.GA10450@redhat.com> (raw)
Reply-To:
Thinking about the vhost-user protocol, VHOST_SET_MEM_TABLE
is used to update the memory mappings.
So shouldn't we want for response?
Otherwise e.g. guest can start using the memory
that vhost-user can't access.
Similarly, with an IOMMU vhost-user might access memory it shouldn't.
VHOST_SET_VRING_CALL is used for MSI-X masking.
Again, after vector is masted by switching the call fd,
backend shouldn't assert the old one.
Thoughts?
next reply other threads:[~2014-09-17 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 8:38 Michael S. Tsirkin [this message]
2014-09-17 9:39 ` [Qemu-devel] vhost-user: VHOST_SET_MEM_TABLE, VHOST_SET_VRING_CALL need a reply? Linhaifeng
2014-09-17 9:56 ` Michael S. Tsirkin
2014-09-18 0:45 ` Linhaifeng
2014-09-18 5:16 ` Michael S. Tsirkin
2014-09-18 12:39 ` Linhaifeng
2014-09-18 12:54 ` Michael S. Tsirkin
2014-09-18 2:39 ` Linhaifeng
2014-09-18 5:19 ` 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=20140917083815.GA10450@redhat.com \
--to=mst@redhat.com \
--cc=haifeng.lin@huawei.com \
--cc=jerry.lilijun@huawei.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
/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).