From: ranjeet1.kumar@intel.com
To: igt-dev@lists.freedesktop.org, ranjeet1.kumar@intel.com
Subject: [igt-dev] [PATCH] [PATCH i-g-t] i915/gem_pipe_control_store_loop: added description for test case
Date: Wed, 1 Jul 2020 04:53:37 +0530 [thread overview]
Message-ID: <20200630232337.20135-1-ranjeet1.kumar@intel.com> (raw)
From: Ranjeet kumar <ranjeet1.kumar@intel.com>
Added test description for subtest.
Cc: Melkaveri, Arjun <Arjun.Melkaveri@intel.com>
Signed-off-by: Ranjeet kumar <ranjeet1.kumar@intel.com>
---
tests/i915/gem_pipe_control_store_loop.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/i915/gem_pipe_control_store_loop.c b/tests/i915/gem_pipe_control_store_loop.c
index e44e9fb53..a9ff66895 100644
--- a/tests/i915/gem_pipe_control_store_loop.c
+++ b/tests/i915/gem_pipe_control_store_loop.c
@@ -181,9 +181,12 @@ igt_main
igt_assert(batch);
}
+ igt_describe("Creates new buffer each time, emit commands and send it to ring"
+ " for execution.")
igt_subtest("fresh-buffer")
store_pipe_control_loop(false, 2);
+ igt_describe("Emit commands in reused buffer and send it to ring for execution.")
igt_subtest("reused-buffer")
store_pipe_control_loop(true, 2);
--
2.26.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-06-30 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 23:23 ranjeet1.kumar [this message]
2020-07-06 8:18 ` [igt-dev] ✗ Fi.CI.BUILD: failure for i915/gem_pipe_control_store_loop: added description for test case Patchwork
2020-07-06 8:53 ` [igt-dev] [PATCH] [PATCH i-g-t] " Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2020-07-09 1:23 [igt-dev] [PATCH] [PATCH i-g-t]i915/gem_pipe_control_store_loop: " ranjeet1.kumar
2020-07-16 4:14 ranjeet1.kumar
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=20200630232337.20135-1-ranjeet1.kumar@intel.com \
--to=ranjeet1.kumar@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