[PATCH] drm/i915/gvt: Add mdev device attribute group

[Zhenyu Wang]

On 2017.03.13 06:46:12 +0000, Tian, Kevin wrote:
> > >
> > > what about printing vGPU id when the vGPU instance is created?
> > >
> > 
> > I think an interface to read that is more clean than parsing log.
> > And as this will create attrs group for each mdev, there will be
> > more attrs to add in future for vgpu state or even control, etc.
> > 
> 
> It depends on how you want to use that vGPU id. If the only purpose
> is to use it when reading driver message, I don't think it a big burden
> for user to further understand one more message before reading following.
>

The base issue is that we need an interface to tell relationship for
mdev vs vgpu instance, which is represented by uuid vs vgpu id.

> On the other hand, if the vGPU id is required as an input parameter to
> other interfaces, then it's necessary. But in this manner I suppose the
> UUID already serves the purpose.
>

yeah, don't think vgpu id should be used for anything as user input.

> Better finding another example? :-)

well, currently this is to resolve a user complains that for driver message
output we can't tell which mdev that is for.

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/intel-gvt-dev/attachments/20170313/30a805c4/attachment-0001.sig>