From: "Sharma, Nishit" <nishit.sharma@intel.com>
To: Varun Gupta <varun.gupta@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <arvind.yadav@intel.com>, <himal.prasad.ghimiray@intel.com>
Subject: Re: [PATCH i-g-t v2 1/4] tests/intel/xe_madvise: Generalize metadata and group purgeable subtests
Date: Mon, 11 May 2026 14:21:10 +0530 [thread overview]
Message-ID: <be508e0f-e324-4f38-b5ba-b05a3d3fdd8e@intel.com> (raw)
In-Reply-To: <20260511035310.32323-2-varun.gupta@intel.com>
On 5/11/2026 9:22 AM, Varun Gupta wrote:
> Generalize the test file description and functionality tags from
> purgeable-only to cover upcoming atomic madvise subtests.
>
> Wrap existing purgeable subtests in igt_subtest_group with a dedicated
> fixture so the purgeable capability check does not gate future
> non-purgeable subtests.
>
> Signed-off-by: Varun Gupta <varun.gupta@intel.com>
> ---
> tests/intel/xe_madvise.c | 94 +++++++++++++++++++++-------------------
> 1 file changed, 49 insertions(+), 45 deletions(-)
>
> diff --git a/tests/intel/xe_madvise.c b/tests/intel/xe_madvise.c
> index e9bf55ff5..e79cafbff 100644
> --- a/tests/intel/xe_madvise.c
> +++ b/tests/intel/xe_madvise.c
> @@ -4,11 +4,11 @@
> */
>
> /**
> - * TEST: Validate purgeable BO madvise functionality
> + * TEST: Validate madvise functionality
> * Category: Core
> * Mega feature: General Core features
> * Sub-category: Memory management tests
> - * Functionality: madvise, purgeable
> + * Functionality: madvise, purgeable, atomic
> */
>
> #include "igt.h"
> @@ -776,51 +776,55 @@ int igt_main()
> igt_fixture() {
> fd = drm_open_driver(DRIVER_XE);
> xe_device_get(fd);
> - igt_require_f(xe_has_purgeable_support(fd),
> - "Kernel does not support purgeable buffer objects\n");
> }
>
> - igt_subtest("dontneed-before-mmap")
> - xe_for_each_engine(fd, hwe) {
> - test_dontneed_before_mmap(fd);
> - break;
> - }
> -
> - igt_subtest("purged-mmap-blocked")
> - xe_for_each_engine(fd, hwe) {
> - test_purged_mmap_blocked(fd);
> - break;
> - }
> -
> - igt_subtest("dontneed-after-mmap")
> - xe_for_each_engine(fd, hwe) {
> - test_dontneed_after_mmap(fd);
> - break;
> - }
> -
> - igt_subtest("dontneed-before-exec")
> - xe_for_each_engine(fd, hwe) {
> - test_dontneed_before_exec(fd, hwe);
> - break;
> - }
> -
> - igt_subtest("dontneed-after-exec")
> - xe_for_each_engine(fd, hwe) {
> - test_dontneed_after_exec(fd, hwe);
> - break;
> - }
> -
> - igt_subtest("per-vma-tracking")
> - xe_for_each_engine(fd, hwe) {
> - test_per_vma_tracking(fd);
> - break;
> - }
> -
> - igt_subtest("per-vma-protection")
> - xe_for_each_engine(fd, hwe) {
> - test_per_vma_protection(fd, hwe);
> - break;
> - }
> + igt_subtest_group() {
> + igt_fixture()
> + igt_require_f(xe_has_purgeable_support(fd),
> + "Kernel does not support purgeable buffer objects\n");
> +
> + igt_subtest("dontneed-before-mmap")
> + xe_for_each_engine(fd, hwe) {
> + test_dontneed_before_mmap(fd);
> + break;
> + }
> +
> + igt_subtest("purged-mmap-blocked")
> + xe_for_each_engine(fd, hwe) {
> + test_purged_mmap_blocked(fd);
> + break;
> + }
> +
> + igt_subtest("dontneed-after-mmap")
> + xe_for_each_engine(fd, hwe) {
> + test_dontneed_after_mmap(fd);
> + break;
> + }
> +
> + igt_subtest("dontneed-before-exec")
> + xe_for_each_engine(fd, hwe) {
> + test_dontneed_before_exec(fd, hwe);
> + break;
> + }
> +
> + igt_subtest("dontneed-after-exec")
> + xe_for_each_engine(fd, hwe) {
> + test_dontneed_after_exec(fd, hwe);
> + break;
> + }
> +
> + igt_subtest("per-vma-tracking")
> + xe_for_each_engine(fd, hwe) {
> + test_per_vma_tracking(fd);
> + break;
> + }
> +
> + igt_subtest("per-vma-protection")
> + xe_for_each_engine(fd, hwe) {
> + test_per_vma_protection(fd, hwe);
> + break;
> + }
> + }
>
> igt_fixture() {
> xe_device_put(fd);
LGTM:
Reviewed-by: Nishit Sharma <nishit.sharma@intel.com>
next prev parent reply other threads:[~2026-05-11 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 3:52 [PATCH i-g-t v2 0/4] tests/intel/xe_madvise: Add atomic madvise subtests Varun Gupta
2026-05-11 3:52 ` [PATCH i-g-t v2 1/4] tests/intel/xe_madvise: Generalize metadata and group purgeable subtests Varun Gupta
2026-05-11 8:51 ` Sharma, Nishit [this message]
2026-05-11 3:52 ` [PATCH i-g-t v2 2/4] tests/intel/xe_madvise: Add atomic-device subtest Varun Gupta
2026-05-11 8:54 ` Sharma, Nishit
2026-05-11 3:52 ` [PATCH i-g-t v2 3/4] tests/intel/xe_madvise: Add atomic-global subtest Varun Gupta
2026-05-11 9:06 ` Sharma, Nishit
2026-05-11 3:52 ` [PATCH i-g-t v2 4/4] tests/intel/xe_madvise: Add atomic-cpu subtest Varun Gupta
2026-05-11 9:08 ` Sharma, Nishit
2026-05-11 22:18 ` ✗ Fi.CI.BUILD: failure for tests/intel/xe_madvise: Add atomic madvise subtests (rev2) 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=be508e0f-e324-4f38-b5ba-b05a3d3fdd8e@intel.com \
--to=nishit.sharma@intel.com \
--cc=arvind.yadav@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=varun.gupta@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