public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Make contexts non-snooped on non-LLC platforms
Date: Tue, 1 Apr 2014 13:11:02 +0300	[thread overview]
Message-ID: <20140401101102.GA21652@intel.com> (raw)
In-Reply-To: <20140331153937.GA7314@nuc-i3427.alporthouse.com>

On Mon, Mar 31, 2014 at 04:39:37PM +0100, Chris Wilson wrote:
> On Mon, Mar 31, 2014 at 06:09:49PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > We don't do CPU access to GPU contexts so making the GPU access snoop
> > the CPU caches seems silly, and potentially expensive.
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Maybe define a macro to be HAS_L3_CACHE?

What should I do with such a macro?

> 
> The root cause is that our singular enum is not flexible enough to
> account for all platform variations.
> 
> Otherwise, lgtm.
> -Chris
> 
> -- 
> Chris Wilson, Intel Open Source Technology Centre

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-04-01 10:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 15:09 [PATCH] drm/i915: Make contexts non-snooped on non-LLC platforms ville.syrjala
2014-03-31 15:39 ` Chris Wilson
2014-04-01 10:11   ` Ville Syrjälä [this message]
2014-04-01 10:19     ` Chris Wilson
2014-04-01 10:37       ` Ville Syrjälä
2014-04-04 13:36 ` [PATCH v2] " ville.syrjala
2014-04-04 13:41   ` Chris Wilson
2014-04-04 16:00     ` 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=20140401101102.GA21652@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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