From: Karolina Stolarek <karolina.stolarek@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/2] Support custom contexts in exec_blit()
Date: Wed, 30 Nov 2022 08:07:58 +0100 [thread overview]
Message-ID: <cover.1669791691.git.karolina.stolarek@intel.com> (raw)
The series changes how exec_blit() sets blitter engine id in
execbuf used by igt_blitter_src_copy() and
igt_blitter_fast_copy__raw(). Currently, the function assumes
a legacy engine identifier, which won't work for contexts that
have non-standard engine layout.
With this patch series, it will be possible to find a copy
engine based on intel_ctx_cfg_t passed in by the blitter
copy functions. To make it possible, find_engine() had to be
slightly modified. Here, instead of using intel_bb (which
limits the function usage to this structure only), we use
context config extracted from intel_bb, making find_engine()
more flexible.
Karolina Stolarek (2):
lib/intel_batchbuffer: Make find_engine() more flexible
lib/intel_batchbuffer: Use correct engine id in exec_blit()
lib/igt_fb.c | 4 +--
lib/intel_batchbuffer.c | 60 ++++++++++++++++++++++++-----------------
lib/intel_batchbuffer.h | 2 ++
tests/kms_prime.c | 6 +++--
tests/prime_vgem.c | 14 +++++-----
5 files changed, 50 insertions(+), 36 deletions(-)
--
2.25.1
next reply other threads:[~2022-11-30 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 7:07 Karolina Stolarek [this message]
2022-11-30 7:07 ` [igt-dev] [PATCH i-g-t 1/2] lib/intel_batchbuffer: Make find_engine() more flexible Karolina Stolarek
2022-12-01 7:18 ` Zbigniew Kempczyński
2022-12-01 7:38 ` Karolina Stolarek
2022-11-30 7:08 ` [igt-dev] [PATCH i-g-t 2/2] lib/intel_batchbuffer: Use correct engine id in exec_blit() Karolina Stolarek
2022-12-01 7:33 ` Zbigniew Kempczyński
2022-12-01 7:53 ` Karolina Stolarek
2022-11-30 10:13 ` [igt-dev] ✓ Fi.CI.BAT: success for Support custom contexts " Patchwork
2022-11-30 20:43 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-12-01 8:00 ` Karolina Stolarek
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=cover.1669791691.git.karolina.stolarek@intel.com \
--to=karolina.stolarek@intel.com \
--cc=igt-dev@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