Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Grzegorzek, Dominik" <dominik.grzegorzek@intel.com>
To: "Patelczyk, Maciej" <maciej.patelczyk@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tests/xe_eudebug_online: breakpoint-many-sessions-* add delay before resume
Date: Fri, 24 Jan 2025 10:47:36 +0000	[thread overview]
Message-ID: <00452bc5736cf2ba6b367003b28c8b84340eaf55.camel@intel.com> (raw)
In-Reply-To: <20250124104107.3626601-1-maciej.patelczyk@intel.com>

On Fri, 2025-01-24 at 11:41 +0100, Maciej Patelczyk wrote:
> For single tile workloads under debug are executed sequentially.
> The test quickly resumes workload that hit the breakpoint without any
> delay. That is then catched by the expectation that there shall be a
> break between workloads.
> 
> Add sleep before resuming workload so that there is a forced gap
> between workloads. If they were properly executed sequentially
> then the diff between workloads shall be longer than sleep.
> 
> Additionally fix the 'ms' to 'us' typo report in case of assert.
> 
> Signed-off-by: Maciej Patelczyk <maciej.patelczyk@intel.com>
> ---
>  tests/intel/xe_eudebug_online.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/intel/xe_eudebug_online.c b/tests/intel/xe_eudebug_online.c
> index f532387af..d58f7d65f 100644
> --- a/tests/intel/xe_eudebug_online.c
> +++ b/tests/intel/xe_eudebug_online.c
> @@ -2305,6 +2305,7 @@ static void test_many_sessions_on_tiles(int fd, bool multi_tile)
>  				attempt_mask |= BIT(i);
>  				should_break = 1;
>  
> +				usleep(WORKLOAD_DELAY_US);
Oh wow. Nice catch! Pretty sure we had that delay before. 
It had to be dropped acidentally down the road, without this below check was pointless.

Reviewed-by: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
>  				eus = (struct drm_xe_eudebug_event_eu_attention *)data[i]->exception_event;
>  				eu_ctl_resume(s[i]->debugger->master_fd, s[i]->debugger->fd,
>  					      eus->client_handle, eus->exec_queue_handle,
> @@ -2328,11 +2329,11 @@ static void test_many_sessions_on_tiles(int fd, bool multi_tile)
>  
>  		if (multi_tile)
>  			igt_assert_f(diff < WORKLOAD_DELAY_US,
> -				     "Expected to execute workloads concurrently. Actual delay: %lu ms\n",
> +				     "Expected to execute workloads concurrently. Actual delay: %lu us\n",
>  				     diff);
>  		else
>  			igt_assert_f(diff >= WORKLOAD_DELAY_US,
> -				     "Expected a serialization of workloads. Actual delay: %lu ms\n",
> +				     "Expected a serialization of workloads. Actual delay: %lu us\n",
>  				     diff);
>  	}
>  


  reply	other threads:[~2025-01-24 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 10:41 [PATCH i-g-t] tests/xe_eudebug_online: breakpoint-many-sessions-* add delay before resume Maciej Patelczyk
2025-01-24 10:47 ` Grzegorzek, Dominik [this message]
2025-01-24 18:03 ` ✗ Fi.CI.BUILD: failure for " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-01-27 12:10 [PATCH i-g-t] " Maciej Patelczyk

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=00452bc5736cf2ba6b367003b28c8b84340eaf55.camel@intel.com \
    --to=dominik.grzegorzek@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maciej.patelczyk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox