From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] i915/gem_exec_create: Added test description for test case.
Date: Wed, 25 May 2022 17:23:08 +0200 [thread overview]
Message-ID: <Yo5J3LeT7aQBrgeV@kamilkon-desk1> (raw)
In-Reply-To: <20220523121916.25932-2-sai.gowtham.ch@intel.com>
Hi Sai,
On 2022-05-23 at 17:49:15 +0530, sai.gowtham.ch@intel.com wrote:
> From: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
>
> Added test description for all the subtests that are available.
>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Signed-off-by: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
> ---
> tests/i915/gem_exec_create.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/tests/i915/gem_exec_create.c b/tests/i915/gem_exec_create.c
> index 78d5ffb3..fd09ef02 100644
> --- a/tests/i915/gem_exec_create.c
> +++ b/tests/i915/gem_exec_create.c
> @@ -47,6 +47,10 @@
> #include "i915_drm.h"
> #include "i915/intel_memory_region.h"
>
> +IGT_TEST_DESCRIPTION("\n This test overloads the driver with transient active "
------------------------ ^ ^
Remove these white chars from beginning.
> + "objects and checks if we don't kill the system under the "
> + "mempressure. Some of the symptoms this test look for include "
---------------- ^
s/mempressure/memory pressure/
> + "mysterious hangs.");
> #define ENGINE_FLAGS (I915_EXEC_RING_MASK | I915_EXEC_BSD_MASK)
>
> static double elapsed(const struct timespec *start, const struct timespec *end)
> @@ -166,6 +170,7 @@ igt_main
> I915_DEVICE_MEMORY);
> }
>
> + igt_describe("Checks if we kill the systems by overloading it with active objects");
s/systems/system/
Please add use of only legacy engines here.
> igt_subtest_with_dynamic("legacy")
> for_each_combination(regions, 1, set) {
> char *sub_name = memregion_dynamic_subtest_name(regions);
> @@ -177,6 +182,7 @@ igt_main
> free(sub_name);
> }
>
> + igt_describe("Quick sanitycheck of the above test setup iterating over engines");
Please do not make remarks about "above test", order can change
later, so
s/sanitycheck/sanity check/
s/of the above test setup//
s/over/over all/
> igt_subtest_with_dynamic("basic")
> for_each_combination(regions, 1, set) {
> char *sub_name = memregion_dynamic_subtest_name(regions);
> @@ -188,6 +194,7 @@ igt_main
> free(sub_name);
> }
>
> + igt_describe("This test does a concurrent execution");
Please find better description here.
> igt_subtest_with_dynamic("forked")
> for_each_combination(regions, 1, set) {
> char *sub_name = memregion_dynamic_subtest_name(regions);
> @@ -199,6 +206,9 @@ igt_main
> free(sub_name);
> }
>
> +
> + igt_describe("This test does a forced reclaim, behaving like a bad application"
> + " leaking its bo cache");
> igt_subtest_with_dynamic("madvise")
> for_each_combination(regions, 1, set) {
> char *sub_name = memregion_dynamic_subtest_name(regions);
> --
> 2.35.1
>
BR,
Kamil
next prev parent reply other threads:[~2022-05-25 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 12:19 [igt-dev] [PATCH i-g-t 0/2] HAX add description to gem_exec_create sai.gowtham.ch
2022-05-23 12:19 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_exec_create: Added test description for test case sai.gowtham.ch
2022-05-25 15:23 ` Kamil Konieczny [this message]
2022-05-23 12:19 ` [igt-dev] [PATCH i-g-t 2/2] HAX: don't do full run sai.gowtham.ch
2022-05-23 15:47 ` [igt-dev] ✗ GitLab.Pipeline: warning for HAX add description to gem_exec_create Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-06-26 18:42 [igt-dev] [PATCH i-g-t 0/2] " sai.gowtham.ch
2022-06-26 18:42 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_exec_create: Added test description for test case sai.gowtham.ch
2022-06-27 14:13 ` Kamil Konieczny
2022-06-28 4:43 [igt-dev] [PATCH i-g-t 0/2] HAX add description to gem_exec_create sai.gowtham.ch
2022-06-28 4:43 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_exec_create: Added test description for test case sai.gowtham.ch
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=Yo5J3LeT7aQBrgeV@kamilkon-desk1 \
--to=kamil.konieczny@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=sai.gowtham.ch@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