Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] gem_exec_balancer: move no-GuC requirement to test functions
Date: Thu, 1 Jun 2023 12:46:07 +0200	[thread overview]
Message-ID: <2d4293bf-58f4-c289-5f4f-357d3674c471@intel.com> (raw)
In-Reply-To: <20230601100250.747088-1-andrzej.hajda@intel.com>


On 6/1/2023 12:02 PM, Andrzej Hajda wrote:
> Requirements put into igt_subtest_group/igt_fixture are checked for
> all tests in the file. Even if they do not influence test execution
> they print misleading infos.
>
> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
>   tests/i915/gem_exec_balancer.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_exec_balancer.c b/tests/i915/gem_exec_balancer.c
> index 004ba9a14fe..9190fc2383f 100644
> --- a/tests/i915/gem_exec_balancer.c
> +++ b/tests/i915/gem_exec_balancer.c
> @@ -1525,6 +1525,7 @@ bonded_runner(int i915,
>   	 * submission across multiple engines.
>   	 */
>   	igt_require(gem_scheduler_has_preemption(i915));
> +	igt_require(!gem_using_guc_submission(i915));
>   
>   	cycles = mmap(0, 4096, PROT_WRITE, MAP_SHARED | MAP_ANON, -1, 0);
>   
> @@ -1996,6 +1997,7 @@ static void sliced(int i915)
>   
>   	igt_require(gem_scheduler_has_preemption(i915));
>   	igt_require(gem_scheduler_has_semaphores(i915));
> +	igt_require(!gem_using_guc_submission(i915));
>   
>   	for (int class = 0; class < 32; class++) {
>   		struct i915_engine_class_instance *ci;
> @@ -3605,7 +3607,6 @@ igt_main
>   
>   	igt_subtest_group {
>   		igt_fixture {
> -			igt_require(!gem_using_guc_submission(i915));
>   			intel_allocator_multiprocess_start();
>   		}
>   

  reply	other threads:[~2023-06-01 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 10:02 [igt-dev] [PATCH i-g-t] gem_exec_balancer: move no-GuC requirement to test functions Andrzej Hajda
2023-06-01 10:46 ` Nirmoy Das [this message]
2023-06-01 10:51 ` Kumar, Janga Rahul
2023-06-01 12:44 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-01 17:13 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-06-03  9:41 ` [igt-dev] ✓ Fi.CI.IGT: success 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=2d4293bf-58f4-c289-5f4f-357d3674c471@intel.com \
    --to=nirmoy.das@intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=igt-dev@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