From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: priyanka.dandamudi@intel.com
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] tests/i915/i915_hangman: Explicitly test per engine reset vs full GPU reset
Date: Tue, 30 Nov 2021 15:27:14 -0800 [thread overview]
Message-ID: <878rx5z0kt.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20211128070823.1396652-3-priyanka.dandamudi@intel.com>
On Sat, 27 Nov 2021 23:08:23 -0800, <priyanka.dandamudi@intel.com> wrote:
>
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Although the hangman test was ensuring that *some* reset functionality
> was enabled, it did not differentiate what kind. So add in the
> infrastructure required to choose between per engine reset or full GPU
> reset and update the test to use it. Hangman will now check that it
> can capture error logs when both forms of reset occur. It will also
> ensure that the 'does per engine reset work' tests will only run if
> per engine reset is avaiable.
This is insufficient description for what is included here. This patch
should be split into multiple patches and resubmitted.
next prev parent reply other threads:[~2021-11-30 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 7:08 [igt-dev] [PATCH i-g-t 0/2] Helper function and engine reset test priyanka.dandamudi
2021-11-28 7:08 ` [igt-dev] [PATCH i-g-t 1/2] lib: Refactor common store code into helper function priyanka.dandamudi
2021-11-30 23:18 ` Dixit, Ashutosh
2021-11-28 7:08 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/i915_hangman: Explicitly test per engine reset vs full GPU reset priyanka.dandamudi
2021-11-30 23:27 ` Dixit, Ashutosh [this message]
2021-11-28 8:00 ` [igt-dev] ✓ Fi.CI.BAT: success for Helper function and engine reset test Patchwork
2021-11-28 9:09 ` [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=878rx5z0kt.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=priyanka.dandamudi@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