From: Jason Wang <jasowang@redhat.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] a question for control queue
Date: Wed, 14 Jan 2015 16:04:31 +0800 [thread overview]
Message-ID: <54B6230F.7030202@redhat.com> (raw)
In-Reply-To: <F52918179C57134FAEC9EA62FA2F9625119547D0@shsmsx102.ccr.corp.intel.com>
On 01/09/2015 02:41 PM, Ouyang, Changchun wrote:
>
> Hi all,
>
> I have a question about the control queue in qemu,
>
> When the qemu have configured the control queue, and guest also
> negotiated the control queue successfully with qemu,
>
> Will the qemu will let vhost know guest try to use control queue to
> send some commands?
>
Currently not. Vhost is only in charge of data path so control virtqueue
is still handled by qemu. So the filtering does not even work if vhost
is used. The plan is let management (libvirt) to be notified when guest
want to do filtering. And then libvirt can configure the filter of host
devices.
>
>
>
> Or could the vhost also setup the control queue to communicate
> directly with control queue on guest?
>
Technically, we can.
>
> How to do that?
>
Just do like what we did for rx virtqueue and tx virtqueue. But I see
several issues:
- For security reason, qemu was usually run as non-privileged process.
This means vhost kernel thread does not have the privilege to configure
filter in host.
- Vhost kernel thread know little about the backend (which could be
tun/macvtap or even packet socket).
But for vhost-user implementation, it may make sense but I'm not sure.
>
> Hope anyone could shed some lights on this question.
>
> Thanks in advance!
>
>
>
> Thanks
>
> Changchun
>
prev parent reply other threads:[~2015-01-14 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 6:41 [Qemu-devel] a question for control queue Ouyang, Changchun
2015-01-14 8:04 ` Jason Wang [this message]
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=54B6230F.7030202@redhat.com \
--to=jasowang@redhat.com \
--cc=changchun.ouyang@intel.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).