From: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 0/1] Drop relocations for new gens
Date: Wed, 17 Mar 2021 12:17:43 +0100 [thread overview]
Message-ID: <20210317111744.97872-1-zbigniew.kempczynski@intel.com> (raw)
Patch likely is temporary - until Jason will figure out where
to put his code and avoid unnecessary walk over the objects array.
I need this to find out what tests will fail when we disallow
passing relocations data in execbuf.
Current patch
https://patchwork.freedesktop.org/patch/424069/?series=87980&rev=2
still allows passing relocation data. So we got no -EINVAL
for new hardware what is not we want.
When pread/pwrite drop + allocator series will be merge we want
to rerun of that series and see what's failing on CI.
v2: fixing incidentally left tested comparison (< 9) instead
proper one on newer gens (< 12)
Cc: Jason Ekstrand <jason@jlekstrand.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Zbigniew Kempczyński (1):
drm/i915/gem: Drop relocation support on all new hardware
.../gpu/drm/i915/gem/i915_gem_execbuffer.c | 22 +++++++++++++++++++
1 file changed, 22 insertions(+)
--
2.26.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-03-17 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 11:17 Zbigniew Kempczyński [this message]
2021-03-17 11:17 ` [Intel-gfx] [PATCH v2 1/1] drm/i915/gem: Drop relocation support on all new hardware Zbigniew Kempczyński
2021-03-17 12:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Drop relocations for new gens (rev2) Patchwork
2021-03-17 12:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-17 14:09 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-03-17 16:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-17 17:47 ` Patchwork
2021-03-17 19:57 ` [Intel-gfx] ✓ 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=20210317111744.97872-1-zbigniew.kempczynski@intel.com \
--to=zbigniew.kempczynski@intel.com \
--cc=intel-gfx@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