[libvirt] [PATCH v2 1/1] Add attribute single_usage_restriction for mdev type-id

read N then user space application can proceed with multiple mdev devices. This is optional and readonly attribute. Signed-off-by: Kirti Wankhede Reviewed-by: Neo Jia --- Documentation/ABI/testing/sysfs-bus-vfio-mdev | 16 1 file changed, 16 insertions(+) diff --git

Re: [libvirt] [RFC PATCH v1 1/1] Add attribute multiple_mdev_support for mdev type-id

On 9/27/2018 9:29 PM, Alex Williamson wrote: > On Thu, 27 Sep 2018 06:48:27 + > "Tian, Kevin" wrote: > >>> From: Kirti Wankhede >>> Sent: Thursday, September 27, 2018 2:22 PM >>> >>> Generally a single instance of mdev device, a

[libvirt] [RFC PATCH v1 1/1] Add attribute multiple_mdev_support for mdev type-id

-by: Neo Jia Signed-off-by: Kirti Wankhede --- Documentation/ABI/testing/sysfs-bus-vfio-mdev | 13 + 1 file changed, 13 insertions(+) diff --git a/Documentation/ABI/testing/sysfs-bus-vfio-mdev b/Documentation/ABI/testing/sysfs-bus-vfio-mdev index 452dbe39270e..69e1291479ce 100644

Re: [libvirt] Matching the type of mediated devices in the migration

On 8/3/2018 11:26 PM, Alex Williamson wrote: > On Fri, 3 Aug 2018 12:07:58 + > "Wang, Zhi A" wrote: > >> Hi: >> >> Thanks for unfolding your idea. The picture is clearer to me now. I didn't >> realize that you also want to support cross hardware migration. Well, I >> thought for a

Re: [libvirt] [RFC PATCH 0/2] Add new mdev type for aggregated resources

On 6/22/2018 1:12 PM, Zhenyu Wang wrote: > On 2018.06.21 09:00:28 -0600, Alex Williamson wrote: >> On Thu, 21 Jun 2018 19:57:38 +0530 >> Kirti Wankhede wrote: >> >>> On 6/20/2018 1:10 PM, Zhenyu Wang wrote: >>>> Current mdev device create inter

Re: [libvirt] [RFC PATCH 0/2] Add new mdev type for aggregated resources

On 6/20/2018 1:10 PM, Zhenyu Wang wrote: > Current mdev device create interface depends on fixed mdev type, which get > uuid > from user to create instance of mdev device. If user wants to use customized > number of resource for mdev device, then only can create new mdev type for > that >

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 4/26/2018 1:22 AM, Dr. David Alan Gilbert wrote: > * Alex Williamson (alex.william...@redhat.com) wrote: >> On Wed, 25 Apr 2018 21:00:39 +0530 >> Kirti Wankhede <kwankh...@nvidia.com> wrote: >> >>> On 4/25/2018 4:29 AM, Alex Williamson wrote: >>>&g

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 4/25/2018 4:29 AM, Alex Williamson wrote: > On Wed, 25 Apr 2018 01:20:08 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> On 4/24/2018 3:10 AM, Alex Williamson wrote: >>> On Wed, 18 Apr 2018 12:31:53 -0600 >>> Alex Williamson <alex.willia

Re: [libvirt] [PATCH 0/3] sample: vfio mdev display devices.

On 4/24/2018 3:10 AM, Alex Williamson wrote: > On Wed, 18 Apr 2018 12:31:53 -0600 > Alex Williamson wrote: > >> On Mon, 9 Apr 2018 12:35:10 +0200 >> Gerd Hoffmann wrote: >> >>> This little series adds three drivers, for demo-ing and testing vfio

Re: [libvirt] [RFC]Add new mdev interface for QoS

On 8/7/2017 1:11 PM, Gao, Ping A wrote: > > On 2017/8/4 5:11, Alex Williamson wrote: >> On Thu, 3 Aug 2017 20:26:14 +0800 >> "Gao, Ping A" <ping.a@intel.com> wrote: >> >>> On 2017/8/3 0:58, Alex Williamson wrote: >>>>

Re: [libvirt] [RFC]Add new mdev interface for QoS

On 8/2/2017 6:29 PM, Gao, Ping A wrote: > > On 2017/8/2 18:19, Kirti Wankhede wrote: >> >> On 8/2/2017 3:56 AM, Alex Williamson wrote: >>> On Tue, 1 Aug 2017 13:54:27 +0800 >>> "Gao, Ping A" <ping.a@intel.com> wrote: >>> >&

Re: [libvirt] [RFC]Add new mdev interface for QoS

On 8/2/2017 3:56 AM, Alex Williamson wrote: > On Tue, 1 Aug 2017 13:54:27 +0800 > "Gao, Ping A" wrote: > >> On 2017/7/28 0:00, Gao, Ping A wrote: >>> On 2017/7/27 0:43, Alex Williamson wrote: [cc +libvir-list] On Wed, 26 Jul 2017 21:16:59 +0800 "Gao,

Re: [libvirt] [RFC PATCH v2 REBASE 17/18] docs: Document the new hostdev and address type 'mdev'

On 2/20/2017 7:58 PM, Erik Skultety wrote: > Signed-off-by: Erik Skultety > --- > docs/formatdomain.html.in | 48 > +++ > 1 file changed, 44 insertions(+), 4 deletions(-) > > diff --git a/docs/formatdomain.html.in

Re: [libvirt] [Qemu-devel] [RFC v2] libvirt vGPU QEMU integration

can have 'class' as optional attribute. So Intel don't have to >> provide 'class' attribute and they don't have to specify mandatory >> attributes of that class. We would provide 'class' attribute and provide >> mandatory attributes. > Thanks, Kirti On 10/3/2016 1:50 PM, Kirt

Re: [libvirt] [Qemu-devel] [RFC v2] libvirt vGPU QEMU integration

On 9/30/2016 10:49 AM, Kirti Wankhede wrote: > ... >>>>>> Hi Daniel, >>>>>> >>>>>> Here you are proposing to add a class named "gpu", which will make all >>>>>> those gpu >>>>>> rela

Re: [libvirt] [Qemu-devel] [RFC v2] libvirt vGPU QEMU integration

a...@redhat.com] >>>> Sent: Thursday, September 29, 2016 4:06 PM >>>> >>>> On Wed, Sep 28, 2016 at 12:48:33PM -0700, Neo Jia wrote: >>>>> On Tue, Sep 20, 2016 at 10:47:53AM +0100, Daniel P. Berrange wrote: >>>>>> On Tue, Sep 20, 2

Re: [libvirt] [RFC v2] libvirt vGPU QEMU integration

7. Hot-plug It is same syntax to create a virtual device for hot-plug. >>> >>> How do groups work with hotplug? Can a device be creating into an >>> existing, running group? Can a device be removed from an existing, >>> running group?

Re: [libvirt] [Qemu-devel] summary of current vfio mdev upstreaming status

On 9/29/2016 3:16 PM, Xiao Guangrong wrote: > > > On 09/29/2016 05:36 PM, Neo Jia wrote: >> On Thu, Sep 29, 2016 at 05:05:47PM +0800, Xiao Guangrong wrote: >>> >>> >>> On 09/29/2016 04:55 PM, Jike Song wrote: Hi all, In order to have a clear understanding about the VFIO mdev

Re: [libvirt] summary of current vfio mdev upstreaming status

On 9/29/2016 2:47 PM, Neo Jia wrote: > On Thu, Sep 29, 2016 at 04:55:39PM +0800, Jike Song wrote: >> Hi all, >> >> In order to have a clear understanding about the VFIO mdev upstreaming >> status, I'd like to summarize it. Please share your opinions on this, >> and correct my misunderstandings.

[libvirt] [PATCH 1/1] Add simple sample driver for mediated device framework

Sample driver creates mdev device that simulates serial port over PCI card. Signed-off-by: Kirti Wankhede <kwankh...@nvidia.com> Signed-off-by: Neo Jia <c...@nvidia.com> Change-Id: I857f8f12f8b275f2498dfe8c628a5cdc7193b1b2 --- Documentation/mdev/Makefile

[libvirt] [PATCH 0/1] Sample driver for mediated device framework

and how it is supposed to work. Kirti Wankhede (1): Add simple sample driver for mediated device framework Documentation/mdev/Makefile | 14 + Documentation/mdev/mtty.c | 1202 + Documentation/{ => mdev}/vfio-media

Re: [libvirt] [RFC v2] libvirt vGPU QEMU integration

On 9/23/2016 12:55 AM, Tian, Kevin wrote: >> From: Kirti Wankhede [mailto:kwankh...@nvidia.com] >> Sent: Wednesday, September 21, 2016 12:23 AM >>> >>>>> I have >>>>> a hard time believing that a given vendor can even allocate unique type >

Re: [libvirt] [RFC v2] libvirt vGPU QEMU integration

> My concern is that a type id seems arbitrary but we're specifying that > it be unique. We already have something unique, the name. So why try > to make the type id unique as well? A vendor can accidentally create > their vendor driver so that a given name means something

Re: [libvirt] [RFC v2] libvirt vGPU QEMU integration

On 9/20/2016 10:20 PM, Alex Williamson wrote: > On Tue, 20 Sep 2016 21:53:16 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> On 9/20/2016 8:13 PM, Alex Williamson wrote: >>> On Tue, 20 Sep 2016 19:51:58 +0530 >>> Kirti Wankhede <kwankh...@nvi

Re: [libvirt] [Qemu-devel] [RFC v2] libvirt vGPU QEMU integration

On 9/20/2016 10:06 PM, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 10:01:18PM +0530, Kirti Wankhede wrote: >> >> >> On 9/20/2016 8:44 PM, Daniel P. Berrange wrote: >>> On Tue, Sep 20, 2016 at 05:05:43PM +0200, Paolo Bonzini wrote: >>>> >>

Re: [libvirt] [Qemu-devel] [RFC v2] libvirt vGPU QEMU integration

On 9/20/2016 8:44 PM, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 05:05:43PM +0200, Paolo Bonzini wrote: >> >> >> On 20/09/2016 16:58, Daniel P. Berrange wrote: > As I've said in my earlier reply - libvirt will *NOT* support passing > arbitrary vendor specific parameters as a

Re: [libvirt] [RFC v2] libvirt vGPU QEMU integration

On 9/20/2016 8:13 PM, Alex Williamson wrote: > On Tue, 20 Sep 2016 19:51:58 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> On 9/20/2016 3:06 AM, Alex Williamson wrote: >>> On Tue, 20 Sep 2016 02:05:52 +0530 >>> Kirti Wankhede <kwankh...

Re: [libvirt] [RFC v2] libvirt vGPU QEMU integration

On 9/20/2016 3:55 AM, Alex Williamson wrote: > On Mon, 19 Sep 2016 23:50:56 +0200 > Paolo Bonzini <pbonz...@redhat.com> wrote: > >> On 19/09/2016 23:36, Alex Williamson wrote: >>> On Tue, 20 Sep 2016 02:05:52 +0530 >>> Kirti Wankhede <kwan

Re: [libvirt] [RFC v2] libvirt vGPU QEMU integration

On 9/20/2016 3:06 AM, Alex Williamson wrote: > On Tue, 20 Sep 2016 02:05:52 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> Hi libvirt experts, >> >> Thanks for valuable input on v1 version of RFC. >> >> Quick brief, VFIO based mediated dev

[libvirt] [RFC v2] libvirt vGPU QEMU integration

Hi libvirt experts, Thanks for valuable input on v1 version of RFC. Quick brief, VFIO based mediated device framework provides a way to virtualize their devices without SR-IOV, like NVIDIA vGPU, Intel KVMGT and IBM's channel IO. This framework reuses VFIO APIs for all the functionalities for

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/8/2016 3:43 AM, Alex Williamson wrote: > On Wed, 7 Sep 2016 23:36:28 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> On 9/7/2016 10:14 PM, Alex Williamson wrote: >>> On Wed, 7 Sep 2016 21:45:31 +0530 >>> Kirti Wankhede <kwankh...@nvidia.c

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/7/2016 10:14 PM, Alex Williamson wrote: > On Wed, 7 Sep 2016 21:45:31 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> On 9/7/2016 2:58 AM, Alex Williamson wrote: >>> On Wed, 7 Sep 2016 01:05:11 +0530 >>> Kirti Wankhede <kwankh...@nvidia

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/7/2016 2:58 AM, Alex Williamson wrote: > On Wed, 7 Sep 2016 01:05:11 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> On 9/6/2016 11:10 PM, Alex Williamson wrote: >>> On Sat, 3 Sep 2016 22:04:56 +0530 >>> Kirti Wankhede <kwankh...@nvidia.c

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/6/2016 11:10 PM, Alex Williamson wrote: > On Sat, 3 Sep 2016 22:04:56 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> On 9/3/2016 3:18 AM, Paolo Bonzini wrote: >>> >>> >>> On 02/09/2016 20:33, Kirti Wankhede wrote: >>>

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/3/2016 6:37 PM, Paolo Bonzini wrote: > > > On 03/09/2016 13:56, John Ferlan wrote: >> On 09/02/2016 05:48 PM, Paolo Bonzini wrote: >>> On 02/09/2016 20:33, Kirti Wankhede wrote: >>>> We could even do: >>>>>> >>>>>>

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/3/2016 5:27 AM, Laine Stump wrote: > On 09/02/2016 05:44 PM, Paolo Bonzini wrote: >> >> >> On 02/09/2016 22:19, John Ferlan wrote: >>> We don't have such a pool for GPU's (yet) - although I suppose they >>> could just become a class of storage pools. >>> >>> The issue being nodedev device

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/3/2016 3:18 AM, Paolo Bonzini wrote: > > > On 02/09/2016 20:33, Kirti Wankhede wrote: >> We could even do: >>>> >>>> echo $UUID1:$GROUPA > create >>>> >>>> where $GROUPA is the group ID of a previously created mdev de

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/3/2016 1:59 AM, John Ferlan wrote: > > > On 09/02/2016 02:33 PM, Kirti Wankhede wrote: >> >> On 9/2/2016 10:55 PM, Paolo Bonzini wrote: >>> >>> >>> On 02/09/2016 19:15, Kirti Wankhede wrote: >>>> On 9/2/201

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/2/2016 10:55 PM, Paolo Bonzini wrote: > > > On 02/09/2016 19:15, Kirti Wankhede wrote: >> On 9/2/2016 3:35 PM, Paolo Bonzini wrote: >>> >>> my-vgpu >>> pci__86_00_0 >>> >>> >>>

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/2/2016 3:35 PM, Paolo Bonzini wrote: > > > On 02/09/2016 07:21, Kirti Wankhede wrote: >> On 9/2/2016 10:18 AM, Michal Privoznik wrote: >>> Okay, maybe I'm misunderstanding something. I just thought that users >>> will consult libvirt's nodedev driver

Re: [libvirt] [PATCH v7 0/4] Add Mediated device support

On 9/2/2016 1:31 AM, Alex Williamson wrote: > On Thu, 1 Sep 2016 23:52:02 +0530 > Kirti Wankhede <kwankh...@nvidia.com> wrote: > >> Alex, >> Thanks for summarizing the discussion. >> >> On 8/31/2016 9:18 PM, Alex Williamson wrote: >>> On Wed,

Re: [libvirt] [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On 9/2/2016 10:18 AM, Michal Privoznik wrote: > On 01.09.2016 18:59, Alex Williamson wrote: >> On Thu, 1 Sep 2016 18:47:06 +0200 >> Michal Privoznik wrote: >> >>> On 31.08.2016 08:12, Tian, Kevin wrote: > From: Alex Williamson [mailto:alex.william...@redhat.com] >

Re: [libvirt] [PATCH v7 0/4] Add Mediated device support

Alex, Thanks for summarizing the discussion. On 8/31/2016 9:18 PM, Alex Williamson wrote: > On Wed, 31 Aug 2016 15:04:13 +0800 > Jike Song wrote: > >> On 08/31/2016 02:12 PM, Tian, Kevin wrote: From: Alex Williamson [mailto:alex.william...@redhat.com] Sent: