[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEauFbww3X2WZuOvMbnhOD2ONBjqR-JS2BrxWPO=HqzXVcKakw@mail.gmail.com>
Date: Mon, 23 Mar 2020 14:33:11 -0700
From: Yonghyun Hwang <yonghyun@...gle.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Kirti Wankhede <kwankhede@...dia.com>,
Alex Williamson <alex.williamson@...hat.com>,
Cornelia Huck <cohuck@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Havard Skinnemoen <hskinnemoen@...gle.com>,
Moritz Fischer <mdf@...nel.org>
Subject: Re: [PATCH] vfio-mdev: support mediated device creation in kernel
On Mon, Mar 23, 2020 at 4:14 AM Christoph Hellwig <hch@...radead.org> wrote:
>
> On Fri, Mar 20, 2020 at 10:59:10AM -0700, Yonghyun Hwang wrote:
> > To enable a mediated device, a device driver registers its device to VFIO
> > MDev framework. Once the mediated device gets enabled, UUID gets fed onto
> > the sysfs attribute, "create", to create the mediated device. This
> > additional step happens after boot-up gets complete. If the driver knows
> > how many mediated devices need to be created during probing time, the
> > additional step becomes cumbersome. This commit implements a new function
> > to allow the driver to create a mediated device in kernel.
>
> Please send this along with your proposed user so that we can understand
> the use. Without that new exports have no chance of going in anyway.
My driver is still under development. Do you recommend me to implement
an example code for the new exports and re-submit the commit?
Thank you,
Yonghyun
Powered by blists - more mailing lists