From: Matthew Brost <matthew.brost@intel.com>
To: Mastan Katragadda <mastanx.katragadda@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] tests/i915/exec_balancer: Added Skip Guc Submission
Date: Thu, 9 Dec 2021 19:20:23 -0800 [thread overview]
Message-ID: <20211210032023.GA22348@jons-linux-dev-box> (raw)
In-Reply-To: <20211209082053.1412439-1-mastanx.katragadda@intel.com>
On Thu, Dec 09, 2021 at 01:50:53PM +0530, Mastan Katragadda wrote:
> This test makes assumptions about the backend scheduling algorithm that
> a real world UMD would never assume. This test is not testing a UMD-KMD
> contract, rather a specific backend.It is an invalid test case thus we
> are skipping.
>
> Changes Since v1:
> -Updated commit message
>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Mastan Katragadda <mastanx.katragadda@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> tests/i915/gem_exec_balancer.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/i915/gem_exec_balancer.c b/tests/i915/gem_exec_balancer.c
> index cc07a5a9..d58734ab 100644
> --- a/tests/i915/gem_exec_balancer.c
> +++ b/tests/i915/gem_exec_balancer.c
> @@ -3320,6 +3320,7 @@ igt_main
>
> igt_subtest_group {
> igt_fixture {
> + igt_require(!gem_using_guc_submission(i915));
> intel_allocator_multiprocess_start();
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-12-10 3:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 8:20 [igt-dev] [i-g-t] tests/i915/exec_balancer: Added Skip Guc Submission Mastan Katragadda
2021-12-09 22:24 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/exec_balancer: Added Skip Guc Submission (rev3) Patchwork
2021-12-10 3:20 ` Matthew Brost [this message]
2021-12-10 8:26 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-12-10 10:02 ` [igt-dev] [i-g-t] tests/i915/exec_balancer: Added Skip Guc Submission Tvrtko Ursulin
2021-12-22 9:30 ` Tvrtko Ursulin
2021-12-22 21:02 ` John Harrison
2021-12-23 11:08 ` Tvrtko Ursulin
2021-12-23 11:16 ` Surendrakumar Upadhyay, TejaskumarX
-- strict thread matches above, loose matches on Subject: below --
2021-11-26 1:57 Mastan Katragadda
2021-11-29 10:30 ` Tvrtko Ursulin
2021-11-29 10:58 ` Katragadda, MastanX
2021-11-29 11:15 ` Tvrtko Ursulin
2021-11-30 16:48 ` Matthew Brost
2021-12-01 9:46 ` Tvrtko Ursulin
2021-12-01 11:36 ` Radoslaw Szwichtenberg
2021-12-01 11:46 ` Daniel Vetter
2021-12-01 12:14 ` Tvrtko Ursulin
2021-12-01 23:57 ` Matthew Brost
2021-12-01 23:42 ` Matthew Brost
2021-12-02 9:19 ` Petri Latvala
2021-12-02 9:20 ` Tvrtko Ursulin
2021-12-03 19:36 ` Matthew Brost
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=20211210032023.GA22348@jons-linux-dev-box \
--to=matthew.brost@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mastanx.katragadda@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 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.