From: "Winiarski, Michal" <michal.winiarski@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915: Avoid writing relocs with addresses in non-canonical form
Date: Fri, 4 Dec 2015 17:41:11 +0000 [thread overview]
Message-ID: <1449250871.3048.9.camel@intel.com> (raw)
In-Reply-To: <20151204161854.GG10243@phenom.ffwll.local>
On Fri, 2015-12-04 at 17:18 +0100, Daniel Vetter wrote:
> On Fri, Dec 04, 2015 at 04:20:43PM +0100, Michał Winiarski wrote:
> > According to bspec, some parts of HW expect the addresses to be in
> > a canonical form, where bits [63:48] == [47]. Let's convert
> > addresses to
> > canonical form prior to relocating and return converted offsets to
> > userspace.
> >
> > v2: Whitespace fixup, gen8_canonical_addr description (Chris,
> > Ville)
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Michel Thierry <michel.thierry@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
>
> Can we igt this? Maybe with softpin or whatever ... For cpu address
> space
> negative addresses are for the kernel, but I think on the gpu we can
> do
> them.
Yup - would definitely be useful, I can add something to one of the
existing reloc tests, but without softpin it's tricky to cover this in
a reliable way (not to mention corner cases).
-Michał
> -Daniel
>
> > ---
> > drivers/gpu/drm/i915/i915_gem_execbuffer.c | 8 +++++---
> > drivers/gpu/drm/i915/i915_gem_gtt.h | 12 ++++++++++++
> > 2 files changed, 17 insertions(+), 3 deletions(-)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-04 17:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 11:33 [PATCH] drm/i915: Avoid writing relocs with addresses in non-canonical form Michał Winiarski
2015-12-04 11:56 ` Ville Syrjälä
2015-12-04 12:05 ` Chris Wilson
2015-12-04 15:20 ` [PATCH v2] " Michał Winiarski
2015-12-04 15:39 ` Chris Wilson
2015-12-04 16:18 ` Daniel Vetter
2015-12-04 17:41 ` Winiarski, Michal [this message]
2015-12-07 8:31 ` Daniel Vetter
2015-12-10 12:50 ` Chris Wilson
2015-12-11 14:13 ` [PATCH v3] " Michał Winiarski
2015-12-11 14:43 ` Michel Thierry
2015-12-18 16:31 ` Chris Wilson
2015-12-18 20:01 ` [PATCH v4] " Michał Winiarski
2015-12-18 20:26 ` Chris Wilson
2015-12-22 11:00 ` [PATCH v5] " Michał Winiarski
2015-12-22 11:41 ` Winiarski, Michal
2015-12-22 12:37 ` [PATCH v6] " Michał Winiarski
2015-12-22 15:00 ` Chris Wilson
2015-12-29 15:49 ` [PATCH v7] " Michał Winiarski
2015-12-29 16:25 ` Chris Wilson
2015-12-29 17:14 ` [PATCH v8] " Michał Winiarski
2015-12-29 17:24 ` [PATCH v9] " Michał Winiarski
2015-12-29 17:28 ` Chris Wilson
2016-01-05 10:01 ` Daniel Vetter
2015-12-29 17:25 ` [PATCH v8] " Chris Wilson
2015-12-19 8:20 ` ✗ warning: Fi.CI.BAT Patchwork
2015-12-22 11:13 ` Patchwork
2015-12-22 14:49 ` Patchwork
2015-12-29 16:20 ` ✗ failure: Fi.CI.BAT Patchwork
2015-12-29 17:49 ` ✗ warning: Fi.CI.BAT 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=1449250871.3048.9.camel@intel.com \
--to=michal.winiarski@intel.com \
--cc=daniel@ffwll.ch \
--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;
as well as URLs for NNTP newsgroup(s).