Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "kamil.konieczny@linux.intel.com" <kamil.konieczny@linux.intel.com>
Subject: Re: [PATCH v9] tests/intel/xe_exec_capture: Add xe_exec_capture test
Date: Thu, 12 Dec 2024 21:41:50 +0000	[thread overview]
Message-ID: <af3aef60ce3eb6963120ed1a45865a98cd8fcf70.camel@intel.com> (raw)
In-Reply-To: <20241206225911.465603-1-zhanjun.dong@intel.com>

On Fri, 2024-12-06 at 14:59 -0800, Dong, Zhanjun wrote:
> Submit cmds to the GPU that result in a GuC engine reset and check that
> devcoredump register dump is generated, by the GuC, and includes the
> full register range.
> 
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> ---
> 
alan:snip

> +igt_main
> +{
> +       int xe;
> +
> +       igt_fixture
> +               xe = drm_open_driver(DRIVER_XE);
> +
> +       igt_subtest("reset") {
> +               int gpu_count = drm_prepare_filtered_multigpu(DRIVER_XE);
> +
> +               igt_require(xe > 0);
> +               if (gpu_count >= 2) {
alan: Zhanjun, i got some offline feedback from Kamil that we should break
up separate subtests for single gpu vs multi-gpu scenarios. That said,
he was okay with doing single GPU first and doing multi-gpu later as an
addition patch if we really need to get this test integrated sooner.
Let's follow up on what works for you (i believe breaking up
subtests for single-default-gpu vs multi-gpu is actually more straight
forward).
> +                       igt_info("Running test on multiple GPU\n");
> +
> +                       igt_multi_fork(child, gpu_count) {
> +                               int gpu_fd;
> +
> +                               gpu_fd = drm_open_filtered_card(child);
> +                               igt_assert_f(gpu_fd > 0, "cannot open gpu-%d, errno=%d\n", child,
> +                                            errno);
> +                               igt_assert(is_xe_device(gpu_fd));
> +
> +                               test_card(gpu_fd);
> +                               drm_close_driver(gpu_fd);
> +                       }
> +                       igt_waitchildren();
> +               } else {
> +                       igt_info("Running test on single GPU\n");
> +                       test_card(xe);
> +               }
> +       }

alan:snip

      parent reply	other threads:[~2024-12-12 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 22:59 [PATCH v9] tests/intel/xe_exec_capture: Add xe_exec_capture test Zhanjun Dong
2024-12-06 23:38 ` ✓ Xe.CI.BAT: success for tests/intel/xe_exec_capture: Add xe_exec_capture test (rev8) Patchwork
2024-12-06 23:52 ` ✓ i915.CI.BAT: " Patchwork
2024-12-07  1:11 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-07  4:42 ` ✗ Xe.CI.Full: " Patchwork
2024-12-11 22:08 ` [PATCH v9] tests/intel/xe_exec_capture: Add xe_exec_capture test Teres Alexis, Alan Previn
2024-12-12 19:54   ` Teres Alexis, Alan Previn
2025-01-07 15:41     ` Dong, Zhanjun
2024-12-12 21:41 ` Teres Alexis, Alan Previn [this message]

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=af3aef60ce3eb6963120ed1a45865a98cd8fcf70.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=zhanjun.dong@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