-dev@lists.oasis-open.org;linux-ker...@vger.kernel.org;
k...@vger.kernel.org;virtualizat...@lists.linux-foundation.org;
net...@vger.kernel.org; Daly, Dan; Wang, Zhihong
; Tan, Jianfeng; Wang, Xiao
W
Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware vhost
backend
On Tue, Apr
@lists.oasis-
open.org; linux-ker...@vger.kernel.org; k...@vger.kernel.org;
virtualizat...@lists.linux-foundation.org; net...@vger.kernel.org; Daly, Dan
; Liang, Cunming ; Wang,
Zhihong ; Tan, Jianfeng ;
Wang, Xiao W
Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware
vhost backend
On Tue, Apr 10, 2018 at 09:23:53AM +, Liang, Cunming wrote:
> If QEMU is going to build a user space driver framework there, we're open
> mind on that, even leveraging DPDK as the underlay library. Looking forward
> to more others' comments from community.
There is already an NVMe VFIO drive
> 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 o
; virtio-dev@lists.oasis-open.org; linux-ker...@vger.kernel.org;
> k...@vger.kernel.org; virtualizat...@lists.linux-foundation.org;
> net...@vger.kernel.org; Daly, Dan ; Wang, Zhihong
> ; Tan, Jianfeng ; Wang, Xiao
> W
> Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardw
; > Zhihong ; Tan, Jianfeng ;
> > Wang, Xiao W
> > Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware
> > vhost backend
> >
> > On 10/04/2018 06:57, Tiwei Bie wrote:
> > >> So you just move the abstraction layer from qemu to kernel, and yo
; open.org; linux-ker...@vger.kernel.org; k...@vger.kernel.org;
> virtualizat...@lists.linux-foundation.org; net...@vger.kernel.org; Daly, Dan
> ; Liang, Cunming ; Wang,
> Zhihong ; Tan, Jianfeng ;
> Wang, Xiao W
> Subject: Re: [virtio-dev] Re: [RFC] vhost: introduce mdev based hardware
&
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 impleme
