From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/selftests: Confirm CS_TIMESTAMP / CTX_TIMESTAMP share a clock
Date: Wed, 23 Dec 2020 15:01:11 +0000 [thread overview]
Message-ID: <160873567138.15843.13996944377330471366@build.alporthouse.com> (raw)
In-Reply-To: <87v9csy3jt.fsf@gaia.fi.intel.com>
Quoting Mika Kuoppala (2020-12-23 14:56:06)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
> > + d_ctx *= RUNTIME_INFO(engine->i915)->cs_timestamp_frequency_hz;
> > + if (IS_ICELAKE(engine->i915))
> > + d_ring *= 12500000; /* Fixed 80ns for icl ctx timestamp? */
>
> This is...weird. But I am not going to argue against hardware.
>
> Will be interesting to see if this can find something funny.
Well it already found the icl funny :(
I didn't appreciate the joke myself.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-12-23 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 12:23 [Intel-gfx] [PATCH 1/2] drm/i915/selftests: Confirm CS_TIMESTAMP / CTX_TIMESTAMP share a clock Chris Wilson
2020-12-23 12:23 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Consolidate the CS timestamp clocks Chris Wilson
2020-12-23 14:36 ` Mika Kuoppala
2020-12-23 14:56 ` [Intel-gfx] [PATCH 1/2] drm/i915/selftests: Confirm CS_TIMESTAMP / CTX_TIMESTAMP share a clock Mika Kuoppala
2020-12-23 15:01 ` Chris Wilson [this message]
2020-12-23 17:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] " Patchwork
2020-12-23 17:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-12-23 22:38 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=160873567138.15843.13996944377330471366@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
/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.