From: Catalin Vasile <catalinvasile92@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [virtio] qemu vs vhost virtqueue consumer
Date: Tue, 7 Apr 2015 11:10:07 +0300 [thread overview]
Message-ID: <CAOMf8tqhTjPHWKVH7Ndxdq4P6LCpp2AZ8A-cj0KpNy-+RPNtkA@mail.gmail.com> (raw)
I am using the virtio-net vhost-net model to make another virtio/vhost solution.
I can't seem to find how does one make a virtqueue to only be consumed
by vhost when adding notifiers to vhost.
virtio_add_queue() seems to always ask for a valid handle for qemu,
and I don't see any disable function primitives called in either vhost
or virtio part in qemu.
I then thought the qemu part checks a flag every time a message
appears, and it stops it from popping data from the virtqueue, but I
don't see that either.
How does the virtio/vhost-net solution make sure qemu doesn't consume
data from a virtqueue destined for vhost?
next reply other threads:[~2015-04-07 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 8:10 Catalin Vasile [this message]
2015-04-07 8:51 ` [Qemu-devel] [virtio] qemu vs vhost virtqueue consumer Greg Kurz
2015-04-07 8:53 ` Catalin Vasile
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=CAOMf8tqhTjPHWKVH7Ndxdq4P6LCpp2AZ8A-cj0KpNy-+RPNtkA@mail.gmail.com \
--to=catalinvasile92@gmail.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).