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: [PATCH i-g-t 1/3] benchmarks/gem_syslatency: Pass a write hazard around
Date: Tue, 22 May 2018 12:37:35 +0100 [thread overview]
Message-ID: <6c8fb540-1cdc-52c8-1065-c81c97016f61@linux.intel.com> (raw)
In-Reply-To: <20180522110044.26439-1-chris@chris-wilson.co.uk>
On 22/05/2018 12:00, Chris Wilson wrote:
> Extend the i915 load to (optionally) pass a write hazard between
> engines, causing us to wait on the interrupt between engines. Thus
> adding MI_USER_INTERRUPT irq handling to our list of sins.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> benchmarks/gem_syslatency.c | 28 ++++++++++++++++++----------
> 1 file changed, 18 insertions(+), 10 deletions(-)
>
> diff --git a/benchmarks/gem_syslatency.c b/benchmarks/gem_syslatency.c
> index de59eaf82..9160e2199 100644
> --- a/benchmarks/gem_syslatency.c
> +++ b/benchmarks/gem_syslatency.c
> @@ -53,6 +53,7 @@ struct gem_busyspin {
> pthread_t thread;
> unsigned long count;
> bool leak;
> + bool interrupts;
> };
>
> struct sys_wait {
> @@ -94,7 +95,7 @@ static void *gem_busyspin(void *arg)
> const uint32_t bbe = MI_BATCH_BUFFER_END;
> struct gem_busyspin *bs = arg;
> struct drm_i915_gem_execbuffer2 execbuf;
> - struct drm_i915_gem_exec_object2 obj;
> + struct drm_i915_gem_exec_object2 obj[2];
> const unsigned sz = bs->leak ? 16 << 20 : 4 << 10;
> unsigned engines[16];
> unsigned nengine;
> @@ -107,13 +108,15 @@ static void *gem_busyspin(void *arg)
> for_each_engine(fd, engine)
> if (!ignore_engine(fd, engine)) engines[nengine++] = engine;
>
> - memset(&obj, 0, sizeof(obj));
> - obj.handle = gem_create(fd, sz);
> - gem_write(fd, obj.handle, 0, &bbe, sizeof(bbe));
> + memset(obj, 0, sizeof(obj));
> + obj[0].handle = gem_create(fd, 4096);
> + obj[0].flags = EXEC_OBJECT_WRITE;
> + obj[1].handle = gem_create(fd, sz);
> + gem_write(fd, obj[1].handle, 0, &bbe, sizeof(bbe));
>
> memset(&execbuf, 0, sizeof(execbuf));
> - execbuf.buffers_ptr = (uintptr_t)&obj;
> - execbuf.buffer_count = 1;
> + execbuf.buffers_ptr = (uintptr_t)(obj + !bs->interrupts);
> + execbuf.buffer_count = 1 + !!bs->interrupts;
Above two lines are to hacky. :/ Suggest a more pedestrian approach with
a ternary or something.
> execbuf.flags |= LOCAL_I915_EXEC_HANDLE_LUT;
> execbuf.flags |= LOCAL_I915_EXEC_NO_RELOC;
> if (__gem_execbuf(fd, &execbuf)) {
> @@ -129,9 +132,9 @@ static void *gem_busyspin(void *arg)
> }
> bs->count += nengine;
> if (bs->leak) {
> - gem_madvise(fd, obj.handle, I915_MADV_DONTNEED);
> - obj.handle = gem_create(fd, sz);
> - gem_write(fd, obj.handle, 0, &bbe, sizeof(bbe));
> + gem_madvise(fd, obj[1].handle, I915_MADV_DONTNEED);
> + obj[1].handle = gem_create(fd, sz);
> + gem_write(fd, obj[1].handle, 0, &bbe, sizeof(bbe));
> }
> }
>
> @@ -305,13 +308,17 @@ int main(int argc, char **argv)
> int field = -1;
> int enable_gem_sysbusy = 1;
> bool leak = false;
> + bool interrupts = false;
> int n, c;
>
> - while ((c = getopt(argc, argv, "t:f:bmn")) != -1) {
> + while ((c = getopt(argc, argv, "t:f:bmni")) != -1) {
> switch (c) {
> case 'n': /* dry run, measure baseline system latency */
> enable_gem_sysbusy = 0;
> break;
> + case 'i': /* interrupts ahoy! */
> + interrupts = true;
> + break;
> case 't':
> /* How long to run the benchmark for (seconds) */
> time = atoi(optarg);
> @@ -346,6 +353,7 @@ int main(int argc, char **argv)
> for (n = 0; n < ncpus; n++) {
> bind_cpu(&attr, n);
> busy[n].leak = leak;
> + busy[n].interrupts = interrupts;
> pthread_create(&busy[n].thread, &attr,
> gem_busyspin, &busy[n]);
> }
>
With the hackery eliminated:
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-05-22 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 11:00 [PATCH i-g-t 1/3] benchmarks/gem_syslatency: Pass a write hazard around Chris Wilson
2018-05-22 11:00 ` [PATCH i-g-t 2/3] benchmarks/gem_syslatency: Allow limiting to just 1 CPU hog Chris Wilson
2018-05-22 11:38 ` Tvrtko Ursulin
2018-05-22 11:00 ` [PATCH i-g-t 3/3] benchmarks/gem_syslatency: Specify batch duration Chris Wilson
2018-05-22 11:49 ` Tvrtko Ursulin
2018-05-22 11:24 ` [PATCH i-g-t 1/3] benchmarks/gem_syslatency: Pass a write hazard around Mika Kuoppala
2018-05-22 11:28 ` Chris Wilson
2018-05-22 11:37 ` Tvrtko Ursulin [this message]
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=6c8fb540-1cdc-52c8-1065-c81c97016f61@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 \
/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