From: Dale B Stimson <dale.b.stimson@intel.com>
To: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v2 5/5] i915/gem_ctx_isolation.c - If initialization fails, exit
Date: Wed, 12 Feb 2020 17:28:40 -0800 [thread overview]
Message-ID: <20200213012840.31472-6-dale.b.stimson@intel.com> (raw)
In-Reply-To: <20200213012840.31472-1-dale.b.stimson@intel.com>
At the start of igt_main, failure of the initial tests for successful
initialization transfer control to the end of an igt_fixture block.
From there, execution of the main per-engine loop is attempted.
Instead, the test should be caused to exit.
If initialization fails, exit.
Signed-off-by: Dale B Stimson <dale.b.stimson@intel.com>
---
tests/i915/gem_ctx_isolation.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/tests/i915/gem_ctx_isolation.c b/tests/i915/gem_ctx_isolation.c
index 07ffbb84a..b11158dab 100644
--- a/tests/i915/gem_ctx_isolation.c
+++ b/tests/i915/gem_ctx_isolation.c
@@ -898,10 +898,13 @@ igt_main
int fd = -1;
struct eng_mmio_base_table_s *mbp = NULL;
uint32_t mmio_base = 0;
+ /* igt_fixture block is skipped if --list-subtests, so start with true. */
+ bool init_successful = true;
igt_fixture {
int gen;
+ init_successful = false;
fd = drm_open_driver(DRIVER_INTEL);
igt_require_gem(fd);
igt_require(gem_has_contexts(fd));
@@ -916,8 +919,20 @@ igt_main
igt_skip_on(gen > LAST_KNOWN_GEN);
mbp = gem_engine_mmio_base_info_get(fd);
+ init_successful = true;
}
+ if (!init_successful) {
+ igt_exit_early();
+ }
+
+ /**
+ * With --list-subtests the above igt_fixture block is skipped and so
+ * the device is not open. Because fd < 0, __for_each_physical_engine
+ * falls back to a static engine list, which will affect the output
+ * of --list-subtests.
+ */
+
/* __for_each_physical_engine switches context to all engines. */
__for_each_physical_engine(fd, e) {
igt_subtest_group {
--
2.25.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-13 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 1:28 [igt-dev] [PATCH i-g-t v2 0/5] mmio_base via debugfs infrastructure + gem_ctx_isolation Dale B Stimson
2020-02-13 1:28 ` [igt-dev] [PATCH i-g-t v2 1/5] i915/gem_mmio_base.c - get mmio_base from debugfs (if possible) Dale B Stimson
2020-02-13 1:28 ` [igt-dev] [PATCH i-g-t v2 2/5] i915/gem_ctx_isolation: Check engine relative registers Dale B Stimson
2020-02-13 1:28 ` [igt-dev] [PATCH i-g-t v2 3/5] i915/gem_ctx_isolation: Check engine relative registers - Part 2 Dale B Stimson
2020-02-13 1:28 ` [Intel-gfx] [PATCH i-g-t v2 4/5] lib/igt_core.c - Introduce igt_exit_early() Dale B Stimson
2020-02-13 1:28 ` Dale B Stimson [this message]
2020-02-13 8:29 ` [igt-dev] [PATCH i-g-t v2 5/5] i915/gem_ctx_isolation.c - If initialization fails, exit Petri Latvala
2020-02-13 19:29 ` Dale B Stimson
2020-02-14 11:12 ` Petri Latvala
2020-02-13 2:12 ` [igt-dev] ✓ Fi.CI.BAT: success for mmio_base via debugfs infrastructure + gem_ctx_isolation Patchwork
2020-02-16 5:26 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20200213012840.31472-6-dale.b.stimson@intel.com \
--to=dale.b.stimson@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@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