On 18/05/2017 10:46, Chris Wilson wrote:
The first goal is to be able to measure GPU (and invidual ring) busyness
without having to poll registers from userspace. (Which not only incurs
holding the forcewake lock indefinitely, perturbing the system, but also
runs the risk of hanging the machine.
On 5/19/2017 1:01 AM, Chris Wilson wrote:
On Thu, May 18, 2017 at 04:48:47PM -0700, Dmitry Rogozhkin wrote:
On 5/18/2017 2:46 AM, Chris Wilson wrote:
The first goal is to be able to measure GPU (and invidual ring) busyness
without having to poll registers from userspace. (Which not only incu
On Thu, May 18, 2017 at 04:48:47PM -0700, Dmitry Rogozhkin wrote:
>
>
> On 5/18/2017 2:46 AM, Chris Wilson wrote:
> >The first goal is to be able to measure GPU (and invidual ring) busyness
> >without having to poll registers from userspace. (Which not only incurs
> >holding the forcewake lock in
On 5/18/2017 2:46 AM, Chris Wilson wrote:
The first goal is to be able to measure GPU (and invidual ring) busyness
without having to poll registers from userspace. (Which not only incurs
holding the forcewake lock indefinitely, perturbing the system, but also
runs the risk of hanging the machin
The first goal is to be able to measure GPU (and invidual ring) busyness
without having to poll registers from userspace. (Which not only incurs
holding the forcewake lock indefinitely, perturbing the system, but also
runs the risk of hanging the machine.) As an alternative we can use the
perf even
