From: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: [igt-dev] [PATCH i-g-t 0/6] Make gpgpu fill tests libdrm independent
Date: Tue, 12 May 2020 10:23:56 +0200 [thread overview]
Message-ID: <20200512082402.26792-1-zbigniew.kempczynski@intel.com> (raw)
This series is likely begin of the journey to make all gpgpu code
(and then media and render copy) libdrm free.
I've introduced intel_bb which is very simplified version of libdrm
powered intel_batchbuffer. Currently it supports simple relocation
but it is enough to cover all gpgpu fill needs. Other (fenced)
relocation will be added when I will have to face with such pipelines /
batchbuffers.
I think there're two possibilities - iterate until functions with
suffix "_v2" will be ready to be replaced older libdrm versions or when
patch will be mature enough to merge and add other gens one by one
with final replacement of "_v2" to "" on the end. I'm looking forward
review comments and suggestions.
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Zbigniew Kempczyński (6):
lib/intel_bufops: Add bufops reference and relaxate stride requirement
lib/intel_batchbuffer: Introduce intel_bb
lib/intel_batchbuffer: Introduce temporary igt_fillfunc_v2_t
lib/gpu_cmds: Add gpgpu pipeline functions based on intel_bb
lib/gpgpu_fill: libdrm-free gpgpu pipeline creation for gen7
tests/gem_gpgpu_fill: Add gen7 version without libdrm dependency
lib/gpgpu_fill.c | 48 +++++
lib/gpgpu_fill.h | 8 +
lib/gpu_cmds.c | 340 ++++++++++++++++++++++++++++++++++++
lib/gpu_cmds.h | 33 ++++
lib/intel_batchbuffer.c | 221 +++++++++++++++++++++++
lib/intel_batchbuffer.h | 86 +++++++++
lib/intel_bufops.c | 20 ++-
lib/intel_bufops.h | 3 +
tests/i915/gem_gpgpu_fill.c | 125 ++++++++++---
9 files changed, 856 insertions(+), 28 deletions(-)
--
2.26.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-05-12 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 8:23 Zbigniew Kempczyński [this message]
2020-05-12 8:23 ` [igt-dev] [PATCH i-g-t 1/6] lib/intel_bufops: Add bufops reference and relaxate stride requirement Zbigniew Kempczyński
2020-05-12 9:29 ` Chris Wilson
2020-05-12 8:23 ` [igt-dev] [PATCH i-g-t 2/6] lib/intel_batchbuffer: Introduce intel_bb Zbigniew Kempczyński
2020-05-12 9:39 ` Chris Wilson
2020-05-12 8:23 ` [igt-dev] [PATCH i-g-t 3/6] lib/intel_batchbuffer: Introduce temporary igt_fillfunc_v2_t Zbigniew Kempczyński
2020-05-12 8:24 ` [igt-dev] [PATCH i-g-t 4/6] lib/gpu_cmds: Add gpgpu pipeline functions based on intel_bb Zbigniew Kempczyński
2020-05-12 8:24 ` [igt-dev] [PATCH i-g-t 5/6] lib/gpgpu_fill: libdrm-free gpgpu pipeline creation for gen7 Zbigniew Kempczyński
2020-05-12 8:24 ` [igt-dev] [PATCH i-g-t 6/6] tests/gem_gpgpu_fill: Add gen7 version without libdrm dependency Zbigniew Kempczyński
2020-05-12 8:59 ` [igt-dev] ✓ Fi.CI.BAT: success for Make gpgpu fill tests libdrm independent Patchwork
2020-05-12 10:43 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20200512082402.26792-1-zbigniew.kempczynski@intel.com \
--to=zbigniew.kempczynski@intel.com \
--cc=chris@chris-wilson.co.uk \
--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