From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Hellstrom Thomas <thomas.hellstrom@intel.com>
Subject: [Intel-gfx] [PATCH v4 0/4] lrc selftest fixes
Date: Mon, 2 May 2022 16:39:59 +0530 [thread overview]
Message-ID: <20220502111003.32397-1-ramalingam.c@intel.com> (raw)
Few bug fixes for lrc selftest.
v4:
Gen8 don't have per engine recording of BB_OFFSET [Chris]
Chris Wilson (4):
drm/i915/gt: Explicitly clear BB_OFFSET for new contexts
drm/i915/selftests: Check for incomplete LRI from the context image
drm/i915/selftest: Always cancel semaphore on error
drm/i915/selftest: Clear the output buffers before GPU writes
drivers/gpu/drm/i915/gt/intel_engine_regs.h | 1 +
drivers/gpu/drm/i915/gt/intel_lrc.c | 20 ++++
drivers/gpu/drm/i915/gt/selftest_lrc.c | 115 ++++++++++++++++----
3 files changed, 116 insertions(+), 20 deletions(-)
--
2.20.1
next reply other threads:[~2022-05-02 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 11:09 Ramalingam C [this message]
2022-05-02 11:10 ` [Intel-gfx] [PATCH v4 1/4] drm/i915/gt: Explicitly clear BB_OFFSET for new contexts Ramalingam C
2022-05-02 12:41 ` Ramalingam C
2022-05-02 11:10 ` [Intel-gfx] [PATCH v4 2/4] drm/i915/selftests: Check for incomplete LRI from the context image Ramalingam C
2022-05-02 11:10 ` [Intel-gfx] [PATCH v4 3/4] drm/i915/selftest: Always cancel semaphore on error Ramalingam C
2022-05-02 11:10 ` [Intel-gfx] [PATCH v4 4/4] drm/i915/selftest: Clear the output buffers before GPU writes Ramalingam C
2022-05-02 11:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for lrc selftest fixes (rev6) Patchwork
2022-05-02 12:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-02 15:12 ` [Intel-gfx] ✗ 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=20220502111003.32397-1-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.hellstrom@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