From: Anshuman Gupta <anshuman.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: badal.nilawar@intel.com, rodrigo.vivi@intel.com
Subject: [igt-dev] [PATCH i-g-t v2 0/2] Add vram_d3cold_threshold test
Date: Fri, 11 Aug 2023 16:40:24 +0530 [thread overview]
Message-ID: <20230811111026.1327273-1-anshuman.gupta@intel.com> (raw)
v2 has major changes in "test/xe_pm: Add vram_d3cold_threshold subtest"
Tests was expecting card to enter to d3cold after freeing up the Xe Bo.
But it wasn't entering because gem_close() doesn't wake device from d3hot.
Therefore test requires to use forcewake debugfs handle to wake device from d3hot and
let XeKMD to compute d3cold.allow based upon used vram and
vram_d3cold_threshold.
Due to above major change in test, i removed the existing RB.
Anshuamn Gupta (1):
lib/igt_pm: Remove pci_system_{init, cleanup}
Anshuman Gupta (1):
test/xe_pm: Add vram_d3cold_threshold subtest
lib/igt_pm.c | 5 --
tests/xe/xe_pm.c | 128 +++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 128 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2023-08-11 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 11:10 Anshuman Gupta [this message]
2023-08-11 11:10 ` [igt-dev] [PATCH i-g-t v2 1/2] lib/igt_pm: Remove pci_system_{init, cleanup} Anshuman Gupta
2023-08-11 11:10 ` [igt-dev] [PATCH i-g-t v2 2/2] test/xe_pm: Add vram_d3cold_threshold subtest Anshuman Gupta
2023-08-11 21:09 ` Rodrigo Vivi
2023-08-14 3:51 ` Gupta, Anshuman
2023-08-14 6:21 ` Anshuman Gupta
2023-08-11 11:20 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add vram_d3cold_threshold test (rev3) Patchwork
2023-08-11 11:47 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-11 11:56 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-12 15:04 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20230811111026.1327273-1-anshuman.gupta@intel.com \
--to=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=rodrigo.vivi@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