From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 2/2] tests/intel/xe_configfs: Check ctx_restore_post_bb
Date: Fri, 19 Sep 2025 17:29:07 -0400 [thread overview]
Message-ID: <aM3LI87WWOA-BCZY@intel.com> (raw)
In-Reply-To: <20250918-configfs-ctx-restore-v2-2-5df035e27e42@intel.com>
On Thu, Sep 18, 2025 at 09:50:21PM -0700, Lucas De Marchi wrote:
> Add sanity checks for some bb written to ctx_restore_post_bb and
> ctx_restore_mid_bb. For invalid values, it validates the xe configfs
> implementation correctly rejects them. For valid values, it checks the
> values are written correctly and that later when we driver binds that
> the HW register contains the expected value.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> tests/intel/xe_configfs.c | 177 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 177 insertions(+)
>
> diff --git a/tests/intel/xe_configfs.c b/tests/intel/xe_configfs.c
> index 794c76132..7a7a7edf4 100644
> --- a/tests/intel/xe_configfs.c
> +++ b/tests/intel/xe_configfs.c
> @@ -26,6 +26,31 @@
> static char bus_addr[NAME_MAX];
> static struct pci_device *pci_dev;
>
> +static bool check_registers(const uint32_t reg[], const uint32_t val[],
> + size_t max)
> +{
> + struct intel_mmio_data mmio_data = { };
> + bool ret = false;
> +
> + intel_register_access_init(&mmio_data, pci_dev, 0);
> +
> + for (int i = 0; i < max && reg[i]; i++) {
> + uint32_t v = intel_register_read(&mmio_data, reg[i]);
> +
easier than I had imagined...
Thanks
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> + if (v != val[i]) {
> + igt_debug("Expecting [%x]=%x but found %x\n",
> + reg[i], val[i], v);
> + goto out;
> + }
> + }
> +
> + ret = true;
> +
> +out:
> + intel_register_access_fini(&mmio_data);
> + return ret;
> +}
> +
> static void restore(int sig)
> {
> int configfs_fd;
> @@ -124,6 +149,142 @@ static void test_engines_allowed(int configfs_device_fd)
> }
> }
>
> +/**
> + * SUBTEST: ctx-restore-post-bb-invalid
> + * Description: Validate ctx_restore_post_bb attribute for invalid values
> + *
> + * SUBTEST: ctx-restore-mid-bb-invalid
> + * Description: Validate ctx_restore_mid_bb attribute for invalid values
> + */
> +static void test_ctx_restore_invalid(int configfs_device_fd, const char *type)
> +{
> + static const struct value {
> + const char *test;
> + const char *in;
> + } values[] = {
> + { .test = "invalid-engine",
> + .in = "foobar cmd 11000001 4F100 DEADBEEF",
> + },
> + { .test = "invalid-type",
> + .in = "rcs 11000001 4F100 DEADBEEF",
> + },
> + { .test = "invalid-number",
> + .in = "rcs cmd 1100000g 4F100 DEADBEEF",
> + },
> + { .test = "invalid-number",
> + .in = "rcs cmd 1100000g 4F100 DEADBEEF",
> + },
> + { .test = "invalid-reg-addr-only",
> + .in = "rcs reg 4F100",
> + },
> + };
> + char buf[4096] = { };
> + char file[64] = { };
> +
> + snprintf(file, sizeof(file), "ctx_restore_%s_bb", type);
> + igt_sysfs_set(configfs_device_fd, "ctx_restore_post_bb", "");
> +
> + /*
> + * These only test if command parsing is correct,
> + * so just make sure there's no device bound
> + */
> + igt_kmod_unbind("xe", bus_addr);
> +
> + for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
> + const struct value *v = &values[i];
> +
> + igt_info("Test %s\n", v->test);
> + igt_debug("bb '%s'\n", v->in);
> + igt_assert(!igt_sysfs_set(configfs_device_fd, file, v->in));
> + igt_assert(igt_sysfs_read(configfs_device_fd, file, buf,
> + sizeof(buf) - 1));
> + if (strcmp(buf, "")) {
> + igt_debug("Expecting empty bb, but found '%s'\n", buf);
> + igt_fail(IGT_EXIT_FAILURE);
> + }
> + }
> +}
> +
> +/**
> + * SUBTEST: ctx-restore-post-bb
> + * Description: Validate ctx_restore_post_bb attribute
> + *
> + * SUBTEST: ctx-restore-mid-bb
> + * Description: Validate ctx_restore_mid_bb attribute
> + */
> +static void test_ctx_restore(int configfs_device_fd, const char *type)
> +{
> + static const struct value {
> + const char *test;
> + const char *in;
> + const char *out;
> + uint32_t reg[4];
> + uint32_t reg_val[4];
> + } values[] = {
> + /*
> + * values for the registers just keep incrementing on different
> + * tests to avoid having tests passing just because the
> + * previous execution set a specific value in the HW
> + */
> + { .test = "cmd-single",
> + .in = "rcs cmd 11000001 4F100 DEA0BEE0",
> + .out = "rcs: 11000001 0004f100 dea0bee0\n",
> + .reg = { 0x4f100 },
> + .reg_val = { 0xdea0bee0 },
> + },
> + { .test = "cmd-single-multi-values",
> + .in = "rcs cmd 11000003 4F100 DEA1BEE1 4F104 DEA2BEE2",
> + .out = "rcs: 11000003 0004f100 dea1bee1 0004f104 dea2bee2\n",
> + .reg = { 0x4f100, 0x4f104 },
> + .reg_val = { 0xdea1bee1, 0xdea2bee2 },
> + },
> + { .test = "cmd-multi",
> + .in = "rcs cmd 11000001 4F100 DEA3BEE3\n"
> + "rcs cmd 11000001 4F104 DEA4BEE4",
> + .out = "rcs: 11000001 0004f100 dea3bee3 11000001 0004f104 dea4bee4\n",
> + .reg = { 0x4f100, 0x4f104 },
> + .reg_val = { 0xdea3bee3, 0xdea4bee4 },
> + },
> + { .test = "reg-single",
> + .in = "rcs reg 4F100 DEA5BEE5",
> + .out = "rcs: 11000001 0004f100 dea5bee5\n",
> + .reg = { 0x4f100 },
> + .reg_val = { 0xdea5bee5 },
> + },
> + { .test = "reg-multi",
> + .in = "rcs reg 4F100 DEA6BEE6\n"
> + "rcs reg 4F104 DEA7BEE7",
> + .out = "rcs: 11000001 0004f100 dea6bee6 11000001 0004f104 dea7bee7\n",
> + .reg = { 0x4f100, 0x4f104 },
> + .reg_val = { 0xdea6bee6, 0xdea7bee7 },
> + },
> + };
> + char buf[4096] = { };
> + char file[64] = { };
> +
> + snprintf(file, sizeof(file), "ctx_restore_%s_bb", type);
> +
> + for (size_t i = 0; i < ARRAY_SIZE(values); i++) {
> + const struct value *v = &values[i];
> +
> + igt_kmod_unbind("xe", bus_addr);
> +
> + igt_info("Test %s\n", v->test);
> + igt_debug("bb '%s'\n", v->in);
> + igt_assert(igt_sysfs_set(configfs_device_fd, file, v->in));
> +
> + igt_assert(igt_sysfs_read(configfs_device_fd, file, buf,
> + sizeof(buf) - 1));
> + if (strcmp(v->out, buf)) {
> + igt_debug("Expecting '%s' but found '%s'\n", v->out, buf);
> + igt_fail(IGT_EXIT_FAILURE);
> + }
> +
> + igt_kmod_bind("xe", bus_addr);
> + igt_assert(check_registers(v->reg, v->reg_val, sizeof(v->reg)));
> + }
> +}
> +
> static void set_bus_addr(int fd)
> {
> pci_dev = igt_device_get_pci_device(fd);
> @@ -176,6 +337,22 @@ igt_main
> igt_subtest("engines-allowed")
> test_engines_allowed(configfs_device_fd);
>
> + igt_describe("Validate ctx_restore_post_bb with invalid options");
> + igt_subtest("ctx-restore-post-bb-invalid")
> + test_ctx_restore_invalid(configfs_device_fd, "post");
> +
> + igt_describe("Validate ctx_restore_post_bb");
> + igt_subtest("ctx-restore-post-bb")
> + test_ctx_restore(configfs_device_fd, "post");
> +
> + igt_describe("Validate ctx_restore_mid_bb with invalid options");
> + igt_subtest("ctx-restore-mid-bb-invalid")
> + test_ctx_restore_invalid(configfs_device_fd, "mid");
> +
> + igt_describe("Validate ctx_restore_mid_bb");
> + igt_subtest("ctx-restore-mid-bb")
> + test_ctx_restore(configfs_device_fd, "mid");
> +
> igt_fixture {
> close(configfs_device_fd);
> close(configfs_fd);
>
> --
> 2.50.1
>
next prev parent reply other threads:[~2025-09-19 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 4:50 [PATCH i-g-t v2 0/2] tests/intel/xe_configfs: Test ctx_restore_* Lucas De Marchi
2025-09-19 4:50 ` [PATCH i-g-t v2 1/2] tests/intel/xe_configfs: Save pci_device Lucas De Marchi
2025-09-22 13:39 ` Rodrigo Vivi
2025-09-19 4:50 ` [PATCH i-g-t v2 2/2] tests/intel/xe_configfs: Check ctx_restore_post_bb Lucas De Marchi
2025-09-19 21:29 ` Rodrigo Vivi [this message]
2025-09-24 11:03 ` Kamil Konieczny
2025-09-24 13:03 ` Lucas De Marchi
2025-09-19 6:00 ` ✓ Xe.CI.BAT: success for tests/intel/xe_configfs: Test ctx_restore_* Patchwork
2025-09-19 6:25 ` ✓ i915.CI.BAT: " Patchwork
2025-09-19 15:54 ` ✓ Xe.CI.Full: " Patchwork
2025-09-20 1:57 ` ✗ i915.CI.Full: 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=aM3LI87WWOA-BCZY@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@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