public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
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: [Intel-gfx] [igt-dev] [PATCH i-g-t 03/24] i915/gem_exec_schedule: Measure semaphore power consumption
Date: Tue, 26 Mar 2019 08:46:34 +0000	[thread overview]
Message-ID: <239d5792-a14e-37c0-25f0-05a7e3603e4c@linux.intel.com> (raw)
In-Reply-To: <20190322092155.1656-3-chris@chris-wilson.co.uk>


On 22/03/2019 09:21, Chris Wilson wrote:
> How much energy does spinning on a semaphore consume relative to plain
> old spinning?
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>   tests/i915/gem_exec_schedule.c | 72 +++++++++++++++++++++++++++++++++-
>   1 file changed, 71 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/i915/gem_exec_schedule.c b/tests/i915/gem_exec_schedule.c
> index a9383000a..4f0577b4e 100644
> --- a/tests/i915/gem_exec_schedule.c
> +++ b/tests/i915/gem_exec_schedule.c
> @@ -29,9 +29,10 @@
>   #include <signal.h>
>   
>   #include "igt.h"
> -#include "igt_vgem.h"
> +#include "igt_gpu_power.h"
>   #include "igt_rand.h"
>   #include "igt_sysfs.h"
> +#include "igt_vgem.h"
>   #include "i915/gem_ring.h"
>   
>   #define LO 0
> @@ -1202,6 +1203,65 @@ static void test_pi_ringfull(int fd, unsigned int engine)
>   	munmap(result, 4096);
>   }
>   
> +static void measure_semaphore_power(int i915)
> +{
> +	struct gpu_power power;
> +	unsigned int engine, signaler;
> +
> +	igt_require(gpu_power_open(&power) == 0);
> +
> +	for_each_physical_engine(i915, signaler) {
> +		struct gpu_power_sample s_spin[2];
> +		struct gpu_power_sample s_sema[2];
> +		double baseline, total;
> +		int64_t jiffie = 1;
> +		igt_spin_t *spin;
> +
> +		spin = __igt_spin_batch_new(i915,
> +					    .engine = signaler,
> +					    .flags = IGT_SPIN_POLL_RUN);

		if (!spin)
			continue;

To skip over !can_store_dword, since you are using the low level 
constructor which doesn't check.

> +		gem_wait(i915, spin->handle, &jiffie); /* waitboost */

Waitboost why? Will it be deterministic either way?

> +		igt_assert(spin->running);
> +		igt_spin_busywait_until_running(spin);
> +
> +		gpu_power_read(&power, &s_spin[0]);
> +		usleep(100*1000);
> +		gpu_power_read(&power, &s_spin[1]);
> +
> +		/* Add a waiter to each engine */
> +		for_each_physical_engine(i915, engine) {
> +			igt_spin_t *sema;
> +
> +			if (engine == signaler)
> +				continue;
> +
> +			sema = __igt_spin_batch_new(i915,
> +						    .engine = engine,
> +						    .dependency = spin->handle);
> +
> +			igt_spin_batch_free(i915, sema);
> +		}
> +		usleep(10); /* just give the tasklets a chance to run */
> +
> +		gpu_power_read(&power, &s_sema[0]);
> +		usleep(100*1000);
> +		gpu_power_read(&power, &s_sema[1]);
> +
> +		igt_spin_batch_free(i915, spin);
> +
> +		baseline = gpu_power_W(&power, &s_spin[0], &s_spin[1]);
> +		total = gpu_power_W(&power, &s_sema[0], &s_sema[1]);
> +
> +		igt_info("%s: %.1fmW + %.1fmW (total %1.fmW)\n",
> +			 e__->name,
> +			 1e3 * baseline,
> +			 1e3 * (total - baseline),
> +			 1e3 * total);
> +	}
> +
> +	gpu_power_close(&power);
> +}
> +
>   igt_main
>   {
>   	const struct intel_execution_engine *e;
> @@ -1362,6 +1422,16 @@ igt_main
>   		}
>   	}
>   
> +	igt_subtest_group {
> +		igt_fixture {
> +			igt_require(gem_scheduler_enabled(fd));
> +			igt_require(gem_scheduler_has_semaphores(fd));
> +		}
> +
> +		igt_subtest("semaphore-power")
> +			measure_semaphore_power(fd);
> +	}
> +
>   	igt_fixture {
>   		igt_stop_hang_detector();
>   		close(fd);
> 

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

  reply	other threads:[~2019-03-26  8:46 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  9:21 [igt-dev] [PATCH i-g-t 01/24] i915/gem_exec_latency: Measure the latency of context switching Chris Wilson
2019-03-22  9:21 ` [Intel-gfx] [PATCH i-g-t 02/24] lib: Add GPU power measurement Chris Wilson
2019-03-26  8:36   ` [igt-dev] " Tvrtko Ursulin
2019-03-26  8:49     ` Chris Wilson
2019-03-26  9:18   ` [igt-dev] [PATCH i-g-t v2] " Chris Wilson
2019-03-26  9:52     ` Tvrtko Ursulin
2019-03-26 10:06       ` Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 03/24] i915/gem_exec_schedule: Measure semaphore power consumption Chris Wilson
2019-03-26  8:46   ` Tvrtko Ursulin [this message]
2019-03-26  9:23     ` Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 04/24] i915/gem_exec_whisper: Measure total power consumed Chris Wilson
2019-03-26  8:47   ` Tvrtko Ursulin
2019-03-22  9:21 ` [Intel-gfx] [PATCH i-g-t 05/24] i915/gem_exec_schedule: Verify that using HW semaphores doesn't block Chris Wilson
2019-03-26  9:19   ` [igt-dev] " Tvrtko Ursulin
2019-03-26 10:03     ` [Intel-gfx] " Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 06/24] i915/gem_exec_nop: poll-sequential requires ordering between rings Chris Wilson
2019-03-26  9:38   ` Tvrtko Ursulin
2019-03-22  9:21 ` [Intel-gfx] [PATCH i-g-t 07/24] i915/gem_sync: Make switch-default asymmetric Chris Wilson
2019-03-26  9:57   ` [Intel-gfx] [igt-dev] " Tvrtko Ursulin
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 08/24] i915/gem_ctx_param: Remove kneecapping Chris Wilson
2019-03-26  9:58   ` Tvrtko Ursulin
2019-03-22  9:21 ` [Intel-gfx] [PATCH i-g-t 09/24] i915/gem_exec_big: Add a single shot test Chris Wilson
2019-03-26 10:06   ` [igt-dev] " Tvrtko Ursulin
2019-03-26 10:21     ` Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 10/24] kms_fence_pin_leak: Ask for the GPU before use Chris Wilson
2019-03-26 10:10   ` Tvrtko Ursulin
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 11/24] drm-uapi: Import i915_drm.h upto 53073249452d Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 12/24] lib/i915: Improve gem_context error messages Chris Wilson
2019-03-26 10:14   ` Tvrtko Ursulin
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 13/24] i915/gem_ctx_param: Test set/get (copy) VM Chris Wilson
2019-03-26 10:22   ` Tvrtko Ursulin
2019-03-26 10:33     ` Tvrtko Ursulin
2019-03-26 10:51       ` Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 14/24] i915/gem_ctx_create: Basic checks for constructor properties Chris Wilson
2019-03-26 10:46   ` Tvrtko Ursulin
2019-03-26 11:06     ` [Intel-gfx] " Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 15/24] i915: Add gem_vm_create Chris Wilson
2019-03-26 11:21   ` Tvrtko Ursulin
2019-03-26 11:37     ` Chris Wilson
2019-03-26 11:48       ` Tvrtko Ursulin
2019-03-26 14:11         ` Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 16/24] drm-uapi: Import i915_drm.h upto 364df3d04d51 Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 17/24] i915: Add gem_ctx_clone Chris Wilson
2019-03-26 15:44   ` Tvrtko Ursulin
2019-03-26 15:49     ` Chris Wilson
2019-03-26 15:54     ` Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 18/24] i915: Exercise creating context with shared GTT Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 19/24] i915/gem_ctx_switch: Exercise queues Chris Wilson
2019-03-22  9:21 ` [Intel-gfx] [PATCH i-g-t 20/24] i915/gem_exec_whisper: Fork all-engine tests one-per-engine Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 21/24] i915/gem_exec_whisper: debugfs/next_seqno is defunct Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 22/24] i915: Add gem_ctx_engines Chris Wilson
2019-03-22 16:40   ` Andi Shyti
2019-03-22 16:48     ` Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 23/24] i915: Add gem_exec_balancer Chris Wilson
2019-03-22  9:21 ` [igt-dev] [PATCH i-g-t 24/24] i915/gem_exec_balancer: Exercise bonded pairs Chris Wilson
2019-03-22 10:22 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,01/24] i915/gem_exec_latency: Measure the latency of context switching Patchwork
2019-03-23  6:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-03-26 11:00 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,01/24] i915/gem_exec_latency: Measure the latency of context switching (rev2) 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=239d5792-a14e-37c0-25f0-05a7e3603e4c@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