[PATCH] drm/i915/gvt: Add mdev device attribute group
Tian, Kevin
kevin.tian at intel.com
Wed Mar 15 04:29:31 UTC 2017
> From: Zhenyu Wang [mailto:zhenyuw at linux.intel.com]
> Sent: Wednesday, March 15, 2017 12:06 PM
>
> On 2017.03.15 03:42:36 +0000, Tian, Kevin wrote:
> > > From: Du, Changbin
> > > Sent: Wednesday, March 15, 2017 11:15 AM
> > >
> > > On Wed, Mar 15, 2017 at 10:59:11AM +0800, Zhenyu Wang wrote:
> > > > On 2017.03.13 06:46:12 +0000, Tian, Kevin wrote:
> > > > >
> > > > > Better finding another example? :-)
> > > > >
> > > >
> > > > Another one can think of now is to show shadow context id for each
> > > > vGPU by mdev attributes, which could be used by gpu perf tool for
> > > > per-context profiling. There should be another way to link between
> > > > VM and mdev UUID, then we could identify VM instance.
> > > >
> > > hmm, I think this is useful if we want to profile GPU activity for a
> > > particular VM when the perf tool suport such feature. :)
> > >
> >
> > Are above nodes in the same level as other common mdev attributes?
> > If yes, might be cleaner to create one parent node (e.g. 'intel') to
> > host all those vendor specific attributes?
> >
>
> As in my initial patch it named parent node as "vgpu" which will appear as
> directory under each mdev device, so any further attributes will be under
> that. And I asked for comment if better to name as like "intel_vgpu", etc.?
>
yes, looks intel_vgpu is better in this context.
More information about the intel-gvt-dev
mailing list