From: Mika Kuoppala <mika.kuoppala@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] [Intel-gfx] [PATCH i-g-t] i915/gem_ctx_create: Fix 'files'
Date: Tue, 03 Mar 2020 16:39:28 +0200 [thread overview]
Message-ID: <87lfoh5wpr.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200303143137.1615349-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> The test is supposed to create a context for each execution, so do so.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> tests/i915/gem_ctx_create.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/tests/i915/gem_ctx_create.c b/tests/i915/gem_ctx_create.c
> index 2c44a3e3e..d9192fbab 100644
> --- a/tests/i915/gem_ctx_create.c
> +++ b/tests/i915/gem_ctx_create.c
> @@ -178,7 +178,7 @@ static void active(int fd, const struct intel_execution_engine2 *e,
>
> execbuf.flags = ppgtt_engines[child];
>
> - while (!*(volatile unsigned *)shared) {
> + while (!READ_ONCE(*shared)) {
Pleasing.
> obj.handle = gem_create(fd, 4096 << 10);
> gem_write(fd, obj.handle, 0, &bbe, sizeof(bbe));
>
> @@ -209,17 +209,19 @@ static void active(int fd, const struct intel_execution_engine2 *e,
>
> clock_gettime(CLOCK_MONOTONIC, &start);
> do {
> - do {
> - execbuf.rsvd1 = ctx;
> - for (unsigned n = 0; n < nengine; n++) {
> - execbuf.flags = engines[n];
> - gem_execbuf(fd, &execbuf);
> - }
> - gem_context_destroy(fd, execbuf.rsvd1);
> - } while (++count & 1023);
> + execbuf.rsvd1 = gem_context_clone_with_engines(fd, ctx);
> + for (unsigned n = 0; n < nengine; n++) {
> + execbuf.flags = engines[n];
> + gem_execbuf(fd, &execbuf);
> + }
> + gem_context_destroy(fd, execbuf.rsvd1);
> + count++;
> +
> clock_gettime(CLOCK_MONOTONIC, &end);
> } while (elapsed(&start, &end) < timeout);
>
> + gem_context_destroy(fd, ctx);
Tidy.
Well as the test name is terse as 'active' I can't argue that it should or
should not create a context.
But tossing the same ctx for each execbuf looks fruitless enough.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> +
> gem_sync(fd, obj.handle);
> clock_gettime(CLOCK_MONOTONIC, &end);
> igt_info("[%d] Context creation + execution: %.3f us\n",
> --
> 2.25.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
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: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t] i915/gem_ctx_create: Fix 'files'
Date: Tue, 03 Mar 2020 16:39:28 +0200 [thread overview]
Message-ID: <87lfoh5wpr.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20200303143137.1615349-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> The test is supposed to create a context for each execution, so do so.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> tests/i915/gem_ctx_create.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/tests/i915/gem_ctx_create.c b/tests/i915/gem_ctx_create.c
> index 2c44a3e3e..d9192fbab 100644
> --- a/tests/i915/gem_ctx_create.c
> +++ b/tests/i915/gem_ctx_create.c
> @@ -178,7 +178,7 @@ static void active(int fd, const struct intel_execution_engine2 *e,
>
> execbuf.flags = ppgtt_engines[child];
>
> - while (!*(volatile unsigned *)shared) {
> + while (!READ_ONCE(*shared)) {
Pleasing.
> obj.handle = gem_create(fd, 4096 << 10);
> gem_write(fd, obj.handle, 0, &bbe, sizeof(bbe));
>
> @@ -209,17 +209,19 @@ static void active(int fd, const struct intel_execution_engine2 *e,
>
> clock_gettime(CLOCK_MONOTONIC, &start);
> do {
> - do {
> - execbuf.rsvd1 = ctx;
> - for (unsigned n = 0; n < nengine; n++) {
> - execbuf.flags = engines[n];
> - gem_execbuf(fd, &execbuf);
> - }
> - gem_context_destroy(fd, execbuf.rsvd1);
> - } while (++count & 1023);
> + execbuf.rsvd1 = gem_context_clone_with_engines(fd, ctx);
> + for (unsigned n = 0; n < nengine; n++) {
> + execbuf.flags = engines[n];
> + gem_execbuf(fd, &execbuf);
> + }
> + gem_context_destroy(fd, execbuf.rsvd1);
> + count++;
> +
> clock_gettime(CLOCK_MONOTONIC, &end);
> } while (elapsed(&start, &end) < timeout);
>
> + gem_context_destroy(fd, ctx);
Tidy.
Well as the test name is terse as 'active' I can't argue that it should or
should not create a context.
But tossing the same ctx for each execbuf looks fruitless enough.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> +
> gem_sync(fd, obj.handle);
> clock_gettime(CLOCK_MONOTONIC, &end);
> igt_info("[%d] Context creation + execution: %.3f us\n",
> --
> 2.25.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-03 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 14:31 [igt-dev] [PATCH i-g-t] i915/gem_ctx_create: Fix 'files' Chris Wilson
2020-03-03 14:31 ` [Intel-gfx] " Chris Wilson
2020-03-03 14:39 ` Mika Kuoppala [this message]
2020-03-03 14:39 ` Mika Kuoppala
2020-03-03 15:45 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-03-04 4:22 ` [igt-dev] ✓ Fi.CI.IGT: " 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=87lfoh5wpr.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--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.