On 2019/11/6 上午2:28, Cornelia Huck wrote:
On Tue, 5 Nov 2019 10:44:18 -0700
Alex Williamson wrote:
On Tue, 5 Nov 2019 17:50:25 +0100
Cornelia Huck wrote:
On Tue, 5 Nov 2019 17:32:37 +0800
Jason Wang wrote:
Currently, except for the create and remove, the rest of
mdev_parent_ops is d
On Tue, 5 Nov 2019 10:44:18 -0700
Alex Williamson wrote:
> On Tue, 5 Nov 2019 17:50:25 +0100
> Cornelia Huck wrote:
>
> > On Tue, 5 Nov 2019 17:32:37 +0800
> > Jason Wang wrote:
> >
> > > Currently, except for the create and remove, the rest of
> > > mdev_parent_ops is designed for vfio-md
On Tue, 5 Nov 2019 17:50:25 +0100
Cornelia Huck wrote:
> On Tue, 5 Nov 2019 17:32:37 +0800
> Jason Wang wrote:
>
> > Currently, except for the create and remove, the rest of
> > mdev_parent_ops is designed for vfio-mdev driver only and may not help
> > for kernel mdev driver. With the help of
On Tue, 5 Nov 2019 17:32:37 +0800
Jason Wang wrote:
> Currently, except for the create and remove, the rest of
> mdev_parent_ops is designed for vfio-mdev driver only and may not help
> for kernel mdev driver. With the help of class id, this patch
> introduces device specific callbacks inside md
Currently, except for the create and remove, the rest of
mdev_parent_ops is designed for vfio-mdev driver only and may not help
for kernel mdev driver. With the help of class id, this patch
introduces device specific callbacks inside mdev_device
structure. This allows different set of callback to b
