From: priyanka.dandamudi@intel.com
To: kamil.konieczny@linux.intel.com, igt-dev@lists.freedesktop.org,
arjun.melkaveri@intel.com, priyanka.dandamudi@intel.com
Subject: [igt-dev] [PATCH i-g-t 1/2] i915/gem_madvise: added description for test case
Date: Mon, 25 Apr 2022 15:01:35 +0530 [thread overview]
Message-ID: <20220425093136.507342-2-priyanka.dandamudi@intel.com> (raw)
In-Reply-To: <20220425093136.507342-1-priyanka.dandamudi@intel.com>
From: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
Added test description for subtest.
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: ranjeet kumar <ranjeet1.kumar@intel.com>
Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
Acked-by: Katarzyna Dec <katarzyna.dec@intel.com>
---
tests/i915/gem_madvise.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tests/i915/gem_madvise.c b/tests/i915/gem_madvise.c
index d88747a9..2502d84c 100644
--- a/tests/i915/gem_madvise.c
+++ b/tests/i915/gem_madvise.c
@@ -190,15 +190,23 @@ dontneed_before_exec(void)
igt_main
{
+ igt_describe("Check signal for Segmentation Fault and bus error before"
+ " obtaining a purgeable object and calling for sighandler.");
igt_subtest("dontneed-before-mmap")
dontneed_before_mmap();
+ igt_describe("Check signal for Segmentation Fault and bus error after"
+ " obtaining a purgeable object and calling for sighandler.");
igt_subtest("dontneed-after-mmap")
dontneed_after_mmap();
+ igt_describe("Check if PWRITE reports EFAULT when trying to use purged bo"
+ " for write operation.");
igt_subtest("dontneed-before-pwrite")
dontneed_before_pwrite();
+ igt_describe("Check if EXECBUFFER2 reports EFAULT when trying to submit"
+ " purged bo for GPU.");
igt_subtest("dontneed-before-exec")
dontneed_before_exec();
}
--
2.25.1
next prev parent reply other threads:[~2022-04-25 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 9:31 [igt-dev] [PATCH i-g-t 0/2] HAX add description to gem_madvise priyanka.dandamudi
2022-04-25 9:31 ` priyanka.dandamudi [this message]
2022-04-26 23:28 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_madvise: added description for test case Kamil Konieczny
2022-04-25 9:31 ` [igt-dev] [PATCH i-g-t 2/2] HAX: don't do full run priyanka.dandamudi
2022-04-25 10:48 ` [igt-dev] ✗ Fi.CI.BAT: failure for HAX add description to gem_madvise Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-04-29 6:20 [igt-dev] [PATCH i-g-t 0/2] " priyanka.dandamudi
2022-04-29 6:20 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_madvise: added description for test case priyanka.dandamudi
2022-04-29 7:27 ` Kamil Konieczny
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=20220425093136.507342-2-priyanka.dandamudi@intel.com \
--to=priyanka.dandamudi@intel.com \
--cc=arjun.melkaveri@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.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