On Mon, 23 Sep 2019 at 14:06, Daniel Vetter wrote:
>
> On Sat, Sep 21, 2019 at 10:33 AM Heinrich Fink
> wrote:
> >
> > On Tue, 3 Sep 2019 at 11:53, Daniel Vetter wrote:
> > >
> > > On Tue, Sep 03, 2019 at 11:19:19AM +0200, Heinrich Fink wrote:
> > &
On Tue, 3 Sep 2019 at 11:53, Daniel Vetter wrote:
>
> On Tue, Sep 03, 2019 at 11:19:19AM +0200, Heinrich Fink wrote:
> > On Tue, 3 Sep 2019 at 09:46, Daniel Vetter wrote:
> > >
> > > On Mon, Sep 02, 2019 at 04:24:12PM +0200, Heinrich Fink wrote:
> > > >
On Tue, 3 Sep 2019 at 09:46, Daniel Vetter wrote:
>
> On Mon, Sep 02, 2019 at 04:24:12PM +0200, Heinrich Fink wrote:
> > Store the timestamp of the current vblank in the new field 'time' of the
> > vblank trace event. If the timestamp is calculated by a driver that
Thanks for the review, Daniel. I noticed that my last name was missing
in the initial revision (my git config was messed up). I am sending v2
of this patch to fix this, including your r/b tag.
Cheers, Heinrich
___
Intel-gfx mailing list
Intel-gfx@lists
-by: Daniel Vetter
Signed-off-by: Heinrich Fink
---
drivers/gpu/drm/drm_trace.h | 14 ++
drivers/gpu/drm/drm_vblank.c | 3 ++-
2 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/drm_trace.h b/drivers/gpu/drm/drm_trace.h
index 471eb927474b..11c6dd577e8
the format
> list appropriately.
>
> Cc: sta...@vger.kernel.org
> Cc: Maarten Lankhorst
> Cc: Matt Roper
> Cc: Heinrich Fink
> Reported-by: Heinrich Fink
> Fixes: b20815255693 ("drm/i915: Add plane alpha blending support, v2.")
> Signed-off-by: Ville Syrj
On Tue, 2017-11-14 at 12:23 +, Chris Wilson wrote:
> What is a PM-triggered change of gpu freq? Do you mean when the hw
> itself throttles depending on thermal load.
yes, that's what I meant. Apologies for not being clear about this.
> Then no. Best you can do is
> use the i915 pmu interface
Hi,
is there a simple way for user space to trace PM-triggered changes of
GPU frequency on GEN9/Skylake?
i915:intel_gpu_freq_change seems to only report SW-triggered frequency
change requests. The best option I currently see is to poll
gt_act_freq_mhz, but I was hoping for a more elegant solutio
