[PATCH] drm/i915/gvt: Add mdev device attribute group
Zhenyu Wang
zhenyuw at linux.intel.com
Mon Mar 13 06:40:28 UTC 2017
On 2017.03.13 06:34:35 +0000, Tian, Kevin wrote:
> > From: Zhenyu Wang [mailto:zhenyuw at linux.intel.com]
> > Sent: Monday, March 13, 2017 2:30 PM
> >
> > On 2017.03.13 06:26:49 +0000, Tian, Kevin wrote:
> > > > From: Zhenyu Wang
> > > > Sent: Wednesday, March 08, 2017 4:42 PM
> > > >
> > > > On 2017.03.08 16:19:48 +0800, Zhenyu Wang wrote:
> > > > > This adds initial attribute group for mdev to hold vGPU related
> > > > > for each mdev device, currently just vGPU id is shown.
> > > > >
> > > > > Signed-off-by: Zhenyu Wang <zhenyuw at linux.intel.com>
> > > > > ---
> > > >
> > > > As this will try to create gvt specific attrs directory for each mdev,
> > > > named for "vgpu" now, if anyone prefers other name like "intel_vgpu"?
> > >
> > > vgpu is OK, but curious what's the point of reporting such internal ID?
> > >
> >
> > One reason is that for driver message which only contains vGPU id, we need
> > a way to link that for mdev device which is created by UUID, otherwise can't
> > tell which VM the driver message is for.
> >
>
> 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.
--
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/421806c3/attachment.sig>
More information about the intel-gvt-dev
mailing list