From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org, Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_workarounds: Adapt to change in file format for per-engine wa
Date: Thu, 4 Jul 2019 10:51:44 +0100 [thread overview]
Message-ID: <a85e32da-d4df-6291-e875-59051db06b1d@linux.intel.com> (raw)
In-Reply-To: <20190703165956.16232-1-chris@chris-wilson.co.uk>
On 03/07/2019 17:59, Chris Wilson wrote:
> To reduce the assumptions of RCS0 in the kernel, we want to make the
> debugfs engine agnostic and so we need to adapt the igt parser for
> flexibility.
>
> If we could just adequately simulate S3/S4 in the kernel we could forgo
> this test entirely...
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> tests/i915/gem_workarounds.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/gem_workarounds.c b/tests/i915/gem_workarounds.c
> index 403863c0b..81c356f06 100644
> --- a/tests/i915/gem_workarounds.c
> +++ b/tests/i915/gem_workarounds.c
> @@ -249,6 +249,7 @@ igt_main
> igt_fixture {
> FILE *file;
> char *line = NULL;
> + char *str;
> size_t line_size;
> int i, fd;
>
> @@ -261,9 +262,13 @@ igt_main
>
> fd = igt_debugfs_open(device, "i915_wa_registers", O_RDONLY);
> file = fdopen(fd, "r");
> - igt_assert(getline(&line, &line_size, file) > 0);
> + igt_require(getline(&line, &line_size, file) > 0);
> igt_debug("i915_wa_registers: %s", line);
> - sscanf(line, "Workarounds applied: %d", &num_wa_regs);
> +
> + /* We assume that the first batch is for rcs */
I think you mean "first line".
> + str = strstr(line, "Workarounds applied:");
> + igt_assert(str);
> + sscanf(str, "Workarounds applied: %d", &num_wa_regs);
> igt_require(num_wa_regs > 0);
I have a suspicion all the above section could be simplified using
fscanf and just checking return value and errno but that would be asking
for too much work for what this is.
>
> wa_regs = malloc(num_wa_regs * sizeof(*wa_regs));
> @@ -271,6 +276,9 @@ igt_main
>
> i = 0;
> while (getline(&line, &line_size, file) > 0) {
> + if (strstr(line, "Workarounds applied:"))
> + break;
> +
> igt_debug("%s", line);
> if (sscanf(line, "0x%X: 0x%08X, mask: 0x%08X",
> &wa_regs[i].addr,
>
I just had a thought that since we are fiddling with this we should add
engine names into strings. And/or class:instance pairs.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_workarounds: Adapt to change in file format for per-engine wa
Date: Thu, 4 Jul 2019 10:51:44 +0100 [thread overview]
Message-ID: <a85e32da-d4df-6291-e875-59051db06b1d@linux.intel.com> (raw)
In-Reply-To: <20190703165956.16232-1-chris@chris-wilson.co.uk>
On 03/07/2019 17:59, Chris Wilson wrote:
> To reduce the assumptions of RCS0 in the kernel, we want to make the
> debugfs engine agnostic and so we need to adapt the igt parser for
> flexibility.
>
> If we could just adequately simulate S3/S4 in the kernel we could forgo
> this test entirely...
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> tests/i915/gem_workarounds.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/gem_workarounds.c b/tests/i915/gem_workarounds.c
> index 403863c0b..81c356f06 100644
> --- a/tests/i915/gem_workarounds.c
> +++ b/tests/i915/gem_workarounds.c
> @@ -249,6 +249,7 @@ igt_main
> igt_fixture {
> FILE *file;
> char *line = NULL;
> + char *str;
> size_t line_size;
> int i, fd;
>
> @@ -261,9 +262,13 @@ igt_main
>
> fd = igt_debugfs_open(device, "i915_wa_registers", O_RDONLY);
> file = fdopen(fd, "r");
> - igt_assert(getline(&line, &line_size, file) > 0);
> + igt_require(getline(&line, &line_size, file) > 0);
> igt_debug("i915_wa_registers: %s", line);
> - sscanf(line, "Workarounds applied: %d", &num_wa_regs);
> +
> + /* We assume that the first batch is for rcs */
I think you mean "first line".
> + str = strstr(line, "Workarounds applied:");
> + igt_assert(str);
> + sscanf(str, "Workarounds applied: %d", &num_wa_regs);
> igt_require(num_wa_regs > 0);
I have a suspicion all the above section could be simplified using
fscanf and just checking return value and errno but that would be asking
for too much work for what this is.
>
> wa_regs = malloc(num_wa_regs * sizeof(*wa_regs));
> @@ -271,6 +276,9 @@ igt_main
>
> i = 0;
> while (getline(&line, &line_size, file) > 0) {
> + if (strstr(line, "Workarounds applied:"))
> + break;
> +
> igt_debug("%s", line);
> if (sscanf(line, "0x%X: 0x%08X, mask: 0x%08X",
> &wa_regs[i].addr,
>
I just had a thought that since we are fiddling with this we should add
engine names into strings. And/or class:instance pairs.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-04 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 16:59 [igt-dev] [PATCH i-g-t] i915/gem_workarounds: Adapt to change in file format for per-engine wa Chris Wilson
2019-07-03 16:59 ` Chris Wilson
2019-07-03 18:15 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-07-04 9:51 ` Tvrtko Ursulin [this message]
2019-07-04 9:51 ` [igt-dev] [PATCH i-g-t] " Tvrtko Ursulin
2019-07-04 9:58 ` Chris Wilson
2019-07-04 9:58 ` Chris Wilson
2019-07-04 10:05 ` Tvrtko Ursulin
2019-07-04 10:05 ` Tvrtko Ursulin
2019-07-04 20:05 ` [igt-dev] ✗ Fi.CI.IGT: failure 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=a85e32da-d4df-6291-e875-59051db06b1d@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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.