On Wed, Jul 15, 2015 at 11:31:32AM +0100, Chris Wilson wrote:
> On Wed, Jul 15, 2015 at 10:54:28AM +0100, Chris Wilson wrote:
> > On Wed, Jul 15, 2015 at 02:16:56PM +0530, sourab.gu...@intel.com wrote:
> > > From: Sourab Gupta
> > >
> > > Currently the context ids are specific to a drm file insta
On Wed, Jul 15, 2015 at 10:54:28AM +0100, Chris Wilson wrote:
> On Wed, Jul 15, 2015 at 02:16:56PM +0530, sourab.gu...@intel.com wrote:
> > From: Sourab Gupta
> >
> > Currently the context ids are specific to a drm file instance, as opposed
> > to being globally unique. There are some usecases, w
On Wed, Jul 15, 2015 at 02:16:56PM +0530, sourab.gu...@intel.com wrote:
> From: Sourab Gupta
>
> Currently the context ids are specific to a drm file instance, as opposed
> to being globally unique. There are some usecases, which may require
> globally unique context ids. For e.g. a system level
From: Sourab Gupta
Currently the context ids are specific to a drm file instance, as opposed
to being globally unique. There are some usecases, which may require
globally unique context ids. For e.g. a system level GPU profiler tool may
lean upon the context ids to associate the performance snaps
From: Sourab Gupta
Currently the context ids are specific to a drm file instance, as opposed to
being globally unique. There are some usecases, which may require globally
unique context ids. For e.g. a system level GPU profiler tool may lean upon
the context ids to associate the performance snaps
