qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	"Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"stefanha@redhat.com" <stefanha@redhat.com>,
	"Zhoujian (jay)" <jianjay.zhou@huawei.com>,
	"pasic@linux.vnet.ibm.com" <pasic@linux.vnet.ibm.com>,
	longpeng <longpeng2@huawei.com>,
	"xin.zeng@intel.com" <xin.zeng@intel.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
	"jianfeng.tan@intel.com" <jianfeng.tan@intel.com>
Subject: Re: [Qemu-devel] [PATCH 3/4] cryptodev-vhost-user: add crypto session handler
Date: Wed, 29 Nov 2017 10:11:35 +0100	[thread overview]
Message-ID: <f06f4d8c-9dfb-1ce2-e3a8-d298573377f7@redhat.com> (raw)
In-Reply-To: <20171129060910-mutt-send-email-mst@kernel.org>

On 29/11/2017 05:10, Michael S. Tsirkin wrote:
>> " Interrupt mode for vhost-user is still not supported in current 
>> implementation. But we are evaluating the necessity now.
> 
> That's more or less a spec violation. Guest must get interrupts
> if it does not disable them. And it must notify host
> if host does not disable notifications.

I understood that as "the vhost-user server is always using poll mode
for the virtqueues" and cannot use e.g. ioeventfds.

Thanks,

Paolo

  reply	other threads:[~2017-11-29  9:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  9:03 [Qemu-devel] [PATCH 0/4] cryptodev: add vhost support Gonglei
2017-11-28  9:03 ` [Qemu-devel] [PATCH 1/4] cryptodev: add vhost-user as a new cryptodev backend Gonglei
2017-11-28  9:03 ` [Qemu-devel] [PATCH 2/4] cryptodev: add vhost support Gonglei
2017-11-28  9:03 ` [Qemu-devel] [PATCH 3/4] cryptodev-vhost-user: add crypto session handler Gonglei
2017-11-28 10:01   ` Paolo Bonzini
2017-11-28 10:43     ` Gonglei (Arei)
2017-11-28 10:45       ` Paolo Bonzini
2017-11-28 11:06         ` Gonglei (Arei)
2017-11-28 11:19           ` Paolo Bonzini
2017-11-29  2:33             ` Gonglei (Arei)
2017-11-29  4:10               ` Michael S. Tsirkin
2017-11-29  9:11                 ` Paolo Bonzini [this message]
2017-11-29 10:21                   ` Tan, Jianfeng
2017-11-28 19:15         ` Michael S. Tsirkin
2017-11-28  9:03 ` [Qemu-devel] [PATCH 4/4] cryptodev-vhost-user: set the key length Gonglei
2017-11-28 10:10 ` [Qemu-devel] [PATCH 0/4] cryptodev: add vhost support no-reply
2017-12-18  9:03 ` Gonglei (Arei)
2017-12-20 17:38   ` Michael S. Tsirkin
2017-12-21  0:51     ` Gonglei (Arei)
2017-12-21  4:28       ` Michael S. Tsirkin
2017-12-21  9:11       ` Paolo Bonzini
2017-12-21 14:25 ` Michael S. Tsirkin
2017-12-22  7:39   ` Gonglei (Arei)

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=f06f4d8c-9dfb-1ce2-e3a8-d298573377f7@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=jianfeng.tan@intel.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=longpeng2@huawei.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=roy.fan.zhang@intel.com \
    --cc=stefanha@redhat.com \
    --cc=weidong.huang@huawei.com \
    --cc=xin.zeng@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).