From: Stuart Summers <stuart.summers@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Add MOCS state dump to debugfs
Date: Wed, 07 Aug 2019 14:48:55 -0700 [thread overview]
Message-ID: <1565214535.30036.1.camel@intel.com> (raw)
In-Reply-To: <156521337006.17543.2674431519733362990@skylake-alporthouse-com>
On Wed, 2019-08-07 at 22:29 +0100, Chris Wilson wrote:
> Quoting Stuart Summers (2019-08-07 21:55:55)
> > User applications might need to verify hardware configuration
> > of the MOCS entries. To facilitate this debug, add a new debugfs
> > entry to allow a dump of the MOCS state to verify expected values
> > are set by i915.
>
> User applications + debugfs? It's not an avenue for ABI.
>
> If you really want to provide the settings back to userspace, look at
> something like an i915_query or sysfs.
>
> Or if you just mean igt, then add a Testcase:
>
> If you just need to validate that we are setting and restoring them,
> selftests.
>
> If you need them for debugging errors, add them to the error state.
This was probably poorly worded, you're right. I'll update the commit
message to be more specific.
I do want this for debugging, but not sure error state is the right
place. This is for debugging performance issues, so no specific
failures. If you feel sysfs or i915_query are more correct here, I can
look at adding this there instead. Is there a reason we don't want this
in debugfs specifically?
Thanks,
Stuart
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-07 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 20:55 [PATCH 1/2] drm/i915: Add MOCS state dump to debugfs Stuart Summers
2019-08-07 20:55 ` [PATCH 2/2] drm/i915: Return true by default in mocs settings Stuart Summers
2019-08-08 14:46 ` Kumar Valsan, Prathap
2019-08-07 21:26 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Add MOCS state dump to debugfs Patchwork
2019-08-07 21:29 ` [PATCH 1/2] " Chris Wilson
2019-08-07 21:48 ` Stuart Summers [this message]
2019-08-07 22:01 ` Chris Wilson
2019-08-07 23:00 ` Stuart Summers
2019-08-07 23:12 ` Chris Wilson
2019-08-08 0:09 ` Stuart Summers
2019-08-07 21:54 ` Kumar Valsan, Prathap
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=1565214535.30036.1.camel@intel.com \
--to=stuart.summers@intel.com \
--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 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.