Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

[Tian, Kevin]

> From: Neo Jia [mailto:address@hidden
> Sent: Wednesday, February 17, 2016 6:34 PM
> 
> >
> > Qemu is not a kernel component. And UUID is OPTIONAL for Qemu.
> >
> > KVM is the kernel component. It doesn't use UUID at all. the relation 
> > between
> > UUID and VM is fully maintained in user space.
> 
> Hold on ... we are talking about the vgpu.ko not KVM right?

You said UUID is a general way to represent an object. VM is an object.
There is UUID associated with a VM. But UUID is not recorded in the
kernel KVM. It's a good reference to our design on vgpu object. If
one thing can be done in user space, then better not involve kernel side.

> > >
> > > This is why I think we should use this UUID as a generic management 
> > > interface,
> > > and we shouldn't have anything optional.
> > >
> >
> > I don't buy-in this argument. I always think kernel design should provide
> > enough flexibility, instead of assuming user space behavior.
> >
> 
> I think you are using the wrong terms here. Flexibility doesn't apply here. 
> What
> we are trying to achieve here is to have a generic interface for upper layer
> software to manage vgpu device.

Even Qemu doesn't make UUID as mandatory. It's just an optional parameter.
I'm not sure why you insist UUID mandatory for vGPU here.

> 
> > Let me also add some Citrix friends. See how they feel about the necessity 
> > of
> > having UUID in vgpu name.
> 
> Sorry?

Paul/Malcolm are experts in Citrix XenServer. So I think they may give some
suggestions from their angle. :-)

Thanks
Kevin