From: Daniel Vetter <daniel@ffwll.ch>
To: "Barbalho, Rafael" <rafael.barbalho@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
"Widawsky, Benjamin" <benjamin.widawsky@intel.com>
Subject: Re: [PATCH] drm/i915: Support 64b execbuf
Date: Mon, 5 May 2014 16:02:30 +0200 [thread overview]
Message-ID: <20140505140230.GK20800@phenom.ffwll.local> (raw)
In-Reply-To: <4B498744C37F034EA16F6FBC6AB9FAD2014D10D9@IRSMSX103.ger.corp.intel.com>
On Thu, May 01, 2014 at 10:18:52AM +0000, Barbalho, Rafael wrote:
> > -----Original Message-----
> > From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
> > Of Chris Wilson
> > Sent: Thursday, May 01, 2014 9:13 AM
> > To: Widawsky, Benjamin
> > Cc: Intel GFX
> > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Support 64b execbuf
> >
> > On Mon, Apr 28, 2014 at 07:29:25PM -0700, Ben Widawsky wrote:
> > > Previously, our code only had a 32b offset value for where the
> > > batchbuffer starts. With full PPGTT, and 64b canonical GPU address
> > > space, that is an insufficient value. The code to expand is pretty
> > > straight forward, and only one platform needs to do anything with the
> > > extra bits.
> > >
> > > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> -Chris
> Reviewed-by: Rafael Barbalho <rafael.barbalho@intel.com>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-05-05 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 0:18 [PATCH] drm/i915: Support 64b relocations Ben Widawsky
2014-04-29 1:11 ` [PATCH] drm/i915: Expand error state's address width to 64b Ben Widawsky
2014-04-29 1:43 ` [PATCH] [v2] " Ben Widawsky
2014-04-29 1:45 ` [PATCH] intel_error_decode: use 64b gtt_offset Ben Widawsky
2014-04-29 8:52 ` Daniel Vetter
2014-04-29 9:01 ` Daniel Vetter
2014-04-29 10:48 ` Chris Wilson
2014-04-29 11:05 ` Daniel Vetter
2014-04-30 0:54 ` Ben Widawsky
2014-05-01 8:06 ` [PATCH] [v2] drm/i915: Expand error state's address width to 64b Chris Wilson
2014-04-29 2:21 ` [PATCH] [v3] " Ben Widawsky
2014-04-29 2:29 ` [PATCH] drm/i915: Support 64b execbuf Ben Widawsky
2014-05-01 8:12 ` Chris Wilson
2014-05-01 10:18 ` Barbalho, Rafael
2014-05-05 14:02 ` Daniel Vetter [this message]
2014-05-01 8:04 ` [PATCH] drm/i915: Support 64b relocations Chris Wilson
2014-05-05 14:06 ` Daniel Vetter
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=20140505140230.GK20800@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rafael.barbalho@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