public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Ben Widawsky <benjamin.widawsky@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] BDW swizzling
Date: Thu, 10 Apr 2014 18:51:50 +0100	[thread overview]
Message-ID: <20140410175150.GI12932@strange.amr.corp.intel.com> (raw)
In-Reply-To: <20140410173246.GA7294@intel.com>

On Thu, Apr 10, 2014 at 10:32:46AM -0700, Ben Widawsky wrote:
> On Thu, Apr 10, 2014 at 05:24:07PM +0100, Damien Lespiau wrote:
> > While cruising through the specs, I noticed a note about swizzling changes on
> > BDW. My understanding is that we don't need to either initialize swizzling on
> > the GPU side nor swizzle the address ourselves on the CPU side.
> > 
> > That could be totally wrong though, and I unfortunately don't have a machine to
> > test this theory on.
> 
> I fought with this too. My resolution was we can either set all the
> swizzling bits, or set none. There is no motivation to do either, and
> the spec simply is telling us what they do for windows. That was well
> over a year ago, so it all can be different now.

My (limited) understanding is telling me that if we don't return
I915_BIT_6_SWIZZLE_NONE, user space is going to swizzle the address and
the controller is going to swizzle it again, even from the CPU, so we
end up at the wrong place.

> I honestly don't care what we do though, so long as the patches get
> tested both in simulation and silicon, and there is no measurable perf
> drop. I suppose my mild preference is to, "don't touch it if it ain't
> broke."
> 
> Sorry, but at the moment, I don't have time to test this for you. Maybe
> someone else can, or remind me in a couple of weeks.

Do you know if you have a configuration where we try to swizzle? If yes
and tests/gem_tiled_pread is passing that would give us a nice bit of
information. (which of course can be tried by the next person with time
to do so).

-- 
Damien

  reply	other threads:[~2014-04-10 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 16:24 [PATCH] BDW swizzling Damien Lespiau
2014-04-10 16:24 ` [PATCH] drm/i915/bdw: BDW swizzling in done by the memory controller Damien Lespiau
2014-04-11  9:09   ` Daniel Vetter
2014-04-11  9:17     ` Chris Wilson
2014-04-11 11:10     ` Damien Lespiau
2014-04-11 11:34       ` Daniel Vetter
2014-04-10 17:32 ` [PATCH] BDW swizzling Ben Widawsky
2014-04-10 17:51   ` Damien Lespiau [this message]
2014-04-10 22:50     ` Ben Widawsky
2014-04-11  5:58       ` Chris Wilson
2014-04-11  6:39       ` Ben Widawsky

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=20140410175150.GI12932@strange.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=benjamin.widawsky@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