On 22/02/18 09:17, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-02-21 01:12:46)
On 09/02/18 20:47, Chris Wilson wrote:
Quoting Daniele Ceraolo Spurio (2018-02-09 18:56:36)
On 09/02/18 02:22, Chris Wilson wrote:
Future gen reduce the number of bits we will have available to
differentiat
Quoting Lionel Landwerlin (2018-02-21 01:12:46)
> On 09/02/18 20:47, Chris Wilson wrote:
> > Quoting Daniele Ceraolo Spurio (2018-02-09 18:56:36)
> >>
> >> On 09/02/18 02:22, Chris Wilson wrote:
> >>> Future gen reduce the number of bits we will have available to
> >>> differentiate between context
On 09/02/18 20:47, Chris Wilson wrote:
Quoting Daniele Ceraolo Spurio (2018-02-09 18:56:36)
On 09/02/18 02:22, Chris Wilson wrote:
Future gen reduce the number of bits we will have available to
differentiate between contexts, so reduce the lifetime of the ID
assignment from that of the context
On 12/02/18 11:08, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-02-12 11:00:10)
On 12/02/18 10:41, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-02-12 10:37:52)
On 09/02/18 20:53, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-02-09 17:47:44)
Hey Chris,
From the i915/p
Quoting Lionel Landwerlin (2018-02-12 11:00:10)
> On 12/02/18 10:41, Chris Wilson wrote:
> > Quoting Lionel Landwerlin (2018-02-12 10:37:52)
> >> On 09/02/18 20:53, Chris Wilson wrote:
> >>> Quoting Lionel Landwerlin (2018-02-09 17:47:44)
> Hey Chris,
>
> From the i915/perf point
On 12/02/18 10:41, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-02-12 10:37:52)
On 09/02/18 20:53, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-02-09 17:47:44)
Hey Chris,
From the i915/perf point of view, I'm fine with this change.
The pinning of the hw_id when monitoring a s
Quoting Lionel Landwerlin (2018-02-12 10:37:52)
> On 09/02/18 20:53, Chris Wilson wrote:
> > Quoting Lionel Landwerlin (2018-02-09 17:47:44)
> >> Hey Chris,
> >>
> >> From the i915/perf point of view, I'm fine with this change.
> >> The pinning of the hw_id when monitoring a single context (with
On 09/02/18 20:53, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-02-09 17:47:44)
Hey Chris,
From the i915/perf point of view, I'm fine with this change.
The pinning of the hw_id when monitoring a single context (with OA)
doesn't break the existing userspace (I can only think of Mesa).
Quoting Lionel Landwerlin (2018-02-09 17:47:44)
> Hey Chris,
>
> From the i915/perf point of view, I'm fine with this change.
> The pinning of the hw_id when monitoring a single context (with OA)
> doesn't break the existing userspace (I can only think of Mesa).
>
> I'm also trying to build up
Quoting Daniele Ceraolo Spurio (2018-02-09 18:56:36)
>
>
> On 09/02/18 02:22, Chris Wilson wrote:
> > Future gen reduce the number of bits we will have available to
> > differentiate between contexts, so reduce the lifetime of the ID
> > assignment from that of the context to its current active c
On 09/02/18 02:22, Chris Wilson wrote:
Future gen reduce the number of bits we will have available to
differentiate between contexts, so reduce the lifetime of the ID
assignment from that of the context to its current active cycle (i.e.
only while it is pinned for use by the HW, will it have a
Hey Chris,
From the i915/perf point of view, I'm fine with this change.
The pinning of the hw_id when monitoring a single context (with OA)
doesn't break the existing userspace (I can only think of Mesa).
I'm also trying to build up a system wide monitoring feature in GPUTop
with a timeline d
Future gen reduce the number of bits we will have available to
differentiate between contexts, so reduce the lifetime of the ID
assignment from that of the context to its current active cycle (i.e.
only while it is pinned for use by the HW, will it have a constant ID).
This means that instead of a
13 matches
Mail list logo
