Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: patches for occlusion query fix on sandybridge
Date: Wed, 15 Dec 2010 09:29:40 +0800	[thread overview]
Message-ID: <20101215012940.GE27927@zhen-devel.sh.intel.com> (raw)
In-Reply-To: <20101214181322.GB13645@viiv.ffwll.ch>


[-- Attachment #1.1: Type: text/plain, Size: 1749 bytes --]

On 2010.12.14 19:13:22 +0100, Daniel Vetter wrote:
> On Tue, Dec 14, 2010 at 12:55:59PM +0800, Zhenyu Wang wrote:
> > It appears Sandybridge PIPE_CONTROL write out buffer need
> > to be set as cached, currently LLC cached, in order to read
> > back correct counter. Otherwise I can always be possible to
> > get corrupted 64-bit PS_DEPTH_COUNT from PIPE_CONTROL write.
> > 
> > So below patches try to add new flag during bo create with
> > cacheable type, to be sure that GTT entry's cache bits would
> > be setup for that.
> > 
> > This fixes occlusion query piglit test and mesa demos on my
> > sandybridge. Note that below patches don't include necessary
> > component version check changes.
> 
> General comment on the introduction of a new flag for bo creation:
> 
> If I'm not mistaken, all the query objects are relocated as read_domain =
> I915_GEM_DOMAIN_INSTRUCTION, write_domain = I915_GEM_DOMAIN_INSTRUCTION,
> i.e. we already have an api for userspace to tell us that a PIPE_CONTROL
> command will write to this buffer. Why can't we use that one and remap
> the bo with the correct caching flags on execbuf time (on gen6)?

True, that's the other way I thought about.

> 
> I simply fear that introducing a hacky ad-hoc abi complicates matters when
> we introduce real llc/mlc caching for general stuff. Especially since
> there's seems to be an existing thing already available. I'm still
> fighting the fallout from the incoherent multiple rings introduction and I
> just don't want to repeat such a goof-up.
> 

yeah, it's quick hack. I would take the way to fix caching instead.

thanks.

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2010-12-15  1:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14  4:55 patches for occlusion query fix on sandybridge Zhenyu Wang
2010-12-14  4:56 ` [PATCH] drm/i915: Add cached bo create interface Zhenyu Wang
2010-12-14  4:56 ` [PATCH] intel: new interface for cached bo create Zhenyu Wang
2010-12-14  9:35   ` Chris Wilson
2010-12-14  4:56 ` [PATCH] i965: alloc cached bo for query object on Sandybridge Zhenyu Wang
2010-12-14 17:58 ` patches for occlusion query fix on sandybridge Eric Anholt
2010-12-14 20:59   ` david may
2010-12-14 21:47     ` Chris Wilson
2010-12-15  1:18       ` Zhenyu Wang
2010-12-14 18:13 ` Daniel Vetter
2010-12-15  1:29   ` Zhenyu Wang [this message]

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=20101215012940.GE27927@zhen-devel.sh.intel.com \
    --to=zhenyuw@linux.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