From: Andi Shyti <andi@etezian.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/3] drm/i915/gt: Trace RPS events
Date: Fri, 24 Apr 2020 16:03:26 +0300 [thread overview]
Message-ID: <20200424130326.GF460760@jack.zhora.eu> (raw)
In-Reply-To: <20200422001703.1697-2-chris@chris-wilson.co.uk>
Hi Chris,
On Wed, Apr 22, 2020 at 01:17:02AM +0100, Chris Wilson wrote:
> Add tracek to the RPS events (interrupts, worker, enabling, threshold
> selection, frequency setting), so that if we have to debug reticent HW
> we have some traces to start from.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-24 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 0:17 [Intel-gfx] [PATCH 1/3] drm/i915/gt: Prefer soft-rc6 over RPS DOWN_TIMEOUT Chris Wilson
2020-04-22 0:17 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Trace RPS events Chris Wilson
2020-04-24 13:03 ` Andi Shyti [this message]
2020-04-22 0:17 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: Use the RPM config register to determine clk frequencies Chris Wilson
2020-04-22 0:49 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/gt: Prefer soft-rc6 over RPS DOWN_TIMEOUT Patchwork
2020-04-22 1:14 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-04-22 17:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/gt: Prefer soft-rc6 over RPS DOWN_TIMEOUT (rev2) Patchwork
2020-04-22 18:17 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-04-24 12:50 ` [Intel-gfx] [PATCH 1/3] drm/i915/gt: Prefer soft-rc6 over RPS DOWN_TIMEOUT Andi Shyti
2020-04-24 13:37 ` Chris Wilson
2020-04-24 14:30 ` Andi Shyti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200424130326.GF460760@jack.zhora.eu \
--to=andi@etezian.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox