From: Paolo Bonzini <pbonzini@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>, Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, alex.williamson@redhat.com, ddutile@redhat.com,
alexander.h.duyck@intel.com, virtio-dev@lists.oasis-open.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, dan.daly@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com,
jianfeng.tan@intel.com, xiao.w.wang@intel.com
Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware vhost backend
Date: Tue, 10 Apr 2018 09:51:43 +0200 [thread overview]
Message-ID: <7ee31a12-a370-fc43-82a6-2235f598e970@redhat.com> (raw)
In-Reply-To: <20180410045723.rftsb7l4l3ip2ioi@debian>
On 10/04/2018 06:57, Tiwei Bie wrote:
>> So you just move the abstraction layer from qemu to kernel, and you still
>> need different drivers in kernel for different device interfaces of
>> accelerators. This looks even more complex than leaving it in qemu. As you
>> said, another idea is to implement userspace vhost backend for accelerators
>> which seems easier and could co-work with other parts of qemu without
>> inventing new type of messages.
>
> I'm not quite sure. Do you think it's acceptable to
> add various vendor specific hardware drivers in QEMU?
I think so. We have vendor-specific quirks, and at some point there was
an idea of using quirks to implement (vendor-specific) live migration
support for assigned devices.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>, Jason Wang <jasowang@redhat.com>
Cc: alexander.h.duyck@intel.com, virtio-dev@lists.oasis-open.org,
kvm@vger.kernel.org, mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, xiao.w.wang@intel.com,
ddutile@redhat.com, jianfeng.tan@intel.com,
zhihong.wang@intel.com
Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware vhost backend
Date: Tue, 10 Apr 2018 09:51:43 +0200 [thread overview]
Message-ID: <7ee31a12-a370-fc43-82a6-2235f598e970@redhat.com> (raw)
In-Reply-To: <20180410045723.rftsb7l4l3ip2ioi@debian>
On 10/04/2018 06:57, Tiwei Bie wrote:
>> So you just move the abstraction layer from qemu to kernel, and you still
>> need different drivers in kernel for different device interfaces of
>> accelerators. This looks even more complex than leaving it in qemu. As you
>> said, another idea is to implement userspace vhost backend for accelerators
>> which seems easier and could co-work with other parts of qemu without
>> inventing new type of messages.
>
> I'm not quite sure. Do you think it's acceptable to
> add various vendor specific hardware drivers in QEMU?
I think so. We have vendor-specific quirks, and at some point there was
an idea of using quirks to implement (vendor-specific) live migration
support for assigned devices.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>, Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, alex.williamson@redhat.com, ddutile@redhat.com,
alexander.h.duyck@intel.com, virtio-dev@lists.oasis-open.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, dan.daly@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com,
jianfeng.tan@intel.com, xiao.w.wang@intel.com
Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware vhost backend
Date: Tue, 10 Apr 2018 09:51:43 +0200 [thread overview]
Message-ID: <7ee31a12-a370-fc43-82a6-2235f598e970@redhat.com> (raw)
In-Reply-To: <20180410045723.rftsb7l4l3ip2ioi@debian>
On 10/04/2018 06:57, Tiwei Bie wrote:
>> So you just move the abstraction layer from qemu to kernel, and you still
>> need different drivers in kernel for different device interfaces of
>> accelerators. This looks even more complex than leaving it in qemu. As you
>> said, another idea is to implement userspace vhost backend for accelerators
>> which seems easier and could co-work with other parts of qemu without
>> inventing new type of messages.
>
> I'm not quite sure. Do you think it's acceptable to
> add various vendor specific hardware drivers in QEMU?
I think so. We have vendor-specific quirks, and at some point there was
an idea of using quirks to implement (vendor-specific) live migration
support for assigned devices.
Paolo
---------------------------------------------------------------------
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-10 7:53 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 ` Paolo Bonzini [this message]
2018-04-10 7:51 ` [virtio-dev] " 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
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=7ee31a12-a370-fc43-82a6-2235f598e970@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=ddutile@redhat.com \
--cc=jasowang@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=tiwei.bie@intel.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: link
Be 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.