From: "Tian, Kevin" <kevin.tian@intel.com> To: "Liang, Cunming" <cunming.liang@intel.com>, "Michael S. Tsirkin" <mst@redhat.com> Cc: "Duyck, Alexander H" <alexander.h.duyck@intel.com>, "virtio-dev@lists.oasis-open.org" <virtio-dev@lists.oasis-open.org>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "netdev@vger.kernel.org" <netdev@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "virtualization@lists.linux-foundation.org" <virtualization@lists.linux-foundation.org>, "Wang, Xiao W" <xiao.w.wang@intel.com>, "ddutile@redhat.com" <ddutile@redhat.com>, "Tan, Jianfeng" <jianfeng.tan@intel.com>, "Wang, Zhihong" <zhihong.wang@intel.com>, Paolo Bonzini <pbonzini@redhat.com> Subject: RE: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware vhost backend Date: Wed, 11 Apr 2018 01:38:29 +0000 [thread overview] Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D1910E3505@SHSMSX101.ccr.corp.intel.com> (raw) In-Reply-To: <D0158A423229094DA7ABF71CF2FA0DA34E9226AF@SHSMSX104.ccr.corp.intel.com> > From: Liang, Cunming > Sent: Tuesday, April 10, 2018 10:24 PM > [...] > > > > As others said, we do not need to go overeboard. A couple of small > vendor- > > specific quirks in qemu isn't a big deal. > > It's quite challenge to identify it's small or not, there's no uniform metric. > > It's only dependent on QEMU itself, that's the obvious benefit. Tradeoff is > to build the entire device driver. We don't object to do that in QEMU, but > wanna make sure to understand the boundary size clearly. > It might be helpful if you can post some sample code using proposed framework - then people have a clear feeling about what size is talked about here and whether it falls into the concept of 'small quirks'. Thanks Kevin
WARNING: multiple messages have this Message-ID (diff)
From: "Tian, Kevin" <kevin.tian@intel.com> To: "Liang, Cunming" <cunming.liang@intel.com>, "Michael S. Tsirkin" <mst@redhat.com> Cc: "Duyck, Alexander H" <alexander.h.duyck@intel.com>, "virtio-dev@lists.oasis-open.org" <virtio-dev@lists.oasis-open.org>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "netdev@vger.kernel.org" <netdev@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "virtualization@lists.linux-foundation.org" <virtualization@lists.linux-foundation.org>, "Wang, Xiao W" <xiao.w.wang@intel.com>, "ddutile@redhat.com" <ddutile@redhat.com>, "Tan, Jianfeng" <jianfeng.tan@intel.com>, "Wang, Zhihong" <zhihong.wang@intel.com>, Paolo Bonzini <pbonzini@redhat.com> Subject: RE: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware vhost backend Date: Wed, 11 Apr 2018 01:38:29 +0000 [thread overview] Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D1910E3505@SHSMSX101.ccr.corp.intel.com> (raw) In-Reply-To: <D0158A423229094DA7ABF71CF2FA0DA34E9226AF@SHSMSX104.ccr.corp.intel.com> > From: Liang, Cunming > Sent: Tuesday, April 10, 2018 10:24 PM > [...] > > > > As others said, we do not need to go overeboard. A couple of small > vendor- > > specific quirks in qemu isn't a big deal. > > It's quite challenge to identify it's small or not, there's no uniform metric. > > It's only dependent on QEMU itself, that's the obvious benefit. Tradeoff is > to build the entire device driver. We don't object to do that in QEMU, but > wanna make sure to understand the boundary size clearly. > It might be helpful if you can post some sample code using proposed framework - then people have a clear feeling about what size is talked about here and whether it falls into the concept of 'small quirks'. Thanks Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2018-04-11 1:38 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-02 15:23 [RFC] vhost: introduce mdev based hardware vhost backend Tiwei Bie 2018-04-02 15:23 ` [virtio-dev] " Tiwei Bie 2018-04-10 2:52 ` Jason Wang 2018-04-10 2:52 ` [virtio-dev] " Jason Wang 2018-04-10 4:57 ` Tiwei Bie 2018-04-10 4:57 ` [virtio-dev] " Tiwei Bie 2018-04-10 7:25 ` Jason Wang 2018-04-10 7:25 ` Jason Wang 2018-04-10 7:25 ` [virtio-dev] " Jason Wang 2018-04-19 18:40 ` Michael S. Tsirkin 2018-04-19 18:40 ` Michael S. Tsirkin 2018-04-19 18:40 ` [virtio-dev] " Michael S. Tsirkin 2018-04-20 3:28 ` Tiwei Bie 2018-04-20 3:28 ` Tiwei Bie 2018-04-20 3:28 ` [virtio-dev] " Tiwei Bie 2018-04-20 3:50 ` Michael S. Tsirkin 2018-04-20 3:50 ` Michael S. Tsirkin 2018-04-20 3:50 ` [virtio-dev] " Michael S. Tsirkin 2018-04-20 3:50 ` Liang, Cunming 2018-04-20 3:50 ` [virtio-dev] " Liang, Cunming 2018-04-20 13:52 ` Michael S. Tsirkin 2018-04-20 13:52 ` Michael S. Tsirkin 2018-04-20 13:52 ` [virtio-dev] " Michael S. Tsirkin 2018-04-20 3:50 ` Liang, Cunming 2018-04-20 3:52 ` Jason Wang 2018-04-20 3:52 ` [virtio-dev] " Jason Wang 2018-04-20 3:52 ` Jason Wang 2018-04-20 14:12 ` Michael S. Tsirkin 2018-04-20 14:12 ` [virtio-dev] " Michael S. Tsirkin 2018-04-20 14:12 ` Michael S. Tsirkin 2018-04-10 7:51 ` [virtio-dev] " Paolo Bonzini 2018-04-10 7:51 ` Paolo Bonzini 2018-04-10 7:51 ` Paolo Bonzini 2018-04-10 9:23 ` Liang, Cunming 2018-04-10 13:36 ` Michael S. Tsirkin 2018-04-10 13:36 ` Michael S. Tsirkin 2018-04-10 13:36 ` Michael S. Tsirkin 2018-04-10 14:23 ` Liang, Cunming 2018-04-10 14:23 ` Liang, Cunming 2018-04-11 1:38 ` Tian, Kevin [this message] 2018-04-11 1:38 ` Tian, Kevin 2018-04-11 1:38 ` Tian, Kevin 2018-04-11 2:18 ` Jason Wang 2018-04-11 2:18 ` Jason Wang 2018-04-11 2:18 ` Jason Wang 2018-04-11 2:18 ` Jason Wang 2018-04-11 2:01 ` [virtio-dev] " Stefan Hajnoczi 2018-04-11 2:01 ` Stefan Hajnoczi 2018-04-11 2:01 ` Stefan Hajnoczi 2018-04-11 2:08 ` Jason Wang 2018-04-11 2:08 ` Jason Wang 2018-04-11 2:08 ` Jason Wang 2018-04-10 9:23 ` Liang, Cunming 2018-04-10 4:57 ` Tiwei Bie 2018-04-10 2:52 ` Jason Wang
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=AADFC41AFE54684AB9EE6CBC0274A5D1910E3505@SHSMSX101.ccr.corp.intel.com \ --to=kevin.tian@intel.com \ --cc=alexander.h.duyck@intel.com \ --cc=cunming.liang@intel.com \ --cc=ddutile@redhat.com \ --cc=jianfeng.tan@intel.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mst@redhat.com \ --cc=netdev@vger.kernel.org \ --cc=pbonzini@redhat.com \ --cc=virtio-dev@lists.oasis-open.org \ --cc=virtualization@lists.linux-foundation.org \ --cc=xiao.w.wang@intel.com \ --cc=zhihong.wang@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.