From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/perf: add tests for triggered OA reports
Date: Tue, 31 Mar 2020 17:30:41 +0300 [thread overview]
Message-ID: <d2ea62a5-554a-6f12-968f-61da7246d83b@intel.com> (raw)
In-Reply-To: <158566466722.5852.13316064706500516988@build.alporthouse.com>
On 31/03/2020 17:24, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2020-03-31 12:47:46)
>> By whitelisting a couple of registers we can allow an application
> By whitelisting, through the i915_perf interface, a couple of...
>
> I was looking for how you found a way to set RING_NONPRIV. :)
Yeah, I'll give a try at whitelisting when OA is enabled.
I have another patch where I whitelist 3 ranges of OA perf counter
registers (total 72dwords) on Gen12.
>
>> batch to trigger OA reports in the OA buffer by switching back & forth
>> an inverter on the condition logic.
> Test looks reasonable, but the specific mechanics of OA I can't comment
Yeah, I could enhance by adding stalls and verify the deltas, but I've
checked in Mesa already and came up with piglit tests :
https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/248
-Lionel
> on.
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-03-31 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 11:47 [igt-dev] [PATCH i-g-t] tests/perf: add tests for triggered OA reports Lionel Landwerlin
2020-03-31 13:06 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-03-31 14:24 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2020-03-31 14:30 ` Lionel Landwerlin [this message]
2020-04-02 8:37 ` Lionel Landwerlin
2020-04-01 9:39 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=d2ea62a5-554a-6f12-968f-61da7246d83b@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@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