All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/selftests: Measure CS_TIMESTAMP
Date: Mon, 18 May 2020 10:18:49 +0100	[thread overview]
Message-ID: <158979352965.17769.6762149584043163933@build.alporthouse.com> (raw)
In-Reply-To: <20200516133102.32167-1-chris@chris-wilson.co.uk>

Quoting Chris Wilson (2020-05-16 14:31:02)
> Count the number of CS_TIMESTAMP ticks and check that it matches our
> expectations.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>

ilk:
<6> [197.410742] rcs0: TIMESTAMP 0 cycles [0ns] in 1001322ns [12517 cycles], using CS clock frequency of 12500KHz

elk:
<6> [203.278858] rcs0: TIMESTAMP 562036736 cycles [33722163018ns] in 1001366ns [16690 cycles], using CS clock frequency of 16666KHz

Those two do look gibberish.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-05-18  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 13:24 [Intel-gfx] [PATCH] drm/i915/selftests: Measure CS_TIMESTAMP Chris Wilson
2020-05-16 13:31 ` Chris Wilson
2020-05-18  9:18   ` Chris Wilson [this message]
2020-05-19 10:42   ` Ville Syrjälä
2020-05-19 10:46     ` Chris Wilson
2020-05-19 11:47       ` Ville Syrjälä
2020-05-18  8:16 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Measure CS_TIMESTAMP (rev2) Patchwork
2020-05-18  8:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-05-19 12:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Measure CS_TIMESTAMP (rev3) Patchwork
2020-05-19 12:59 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork

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=158979352965.17769.6762149584043163933@build.alporthouse.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.