public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix context size calculation on SNB/IVB/VLV
Date: Thu, 22 Aug 2013 21:52:53 +0300	[thread overview]
Message-ID: <20130822185253.GF29682@intel.com> (raw)
In-Reply-To: <20130822183054.GB7181@bwidawsk.net>

On Thu, Aug 22, 2013 at 11:30:55AM -0700, Ben Widawsky wrote:
> On Thu, Aug 22, 2013 at 07:23:13PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > All the different context sizes reported in the CXT_SIZE register
> > aren't meant to be simply added together.
> > 
> > While BSpec is somewhat unclear on the topic of the actual context
> > size, empirical tests have now revealed the truth. So let's add a
> > big fat comment to remind people how it all works.
> 
> By the way. I've done some digging. I believe (75% certain) pre-HSW,
> every context save writes the entire data. So if you wanted to set some
> pattern and see what HW actually overwrites, it should be doable. HSW+
> though we can't do that.

Ah right, so you were thinking of initializing the context w/ some
poison, and then see how much is left after the HW has saved. That I
didnb't actually do. Should be reasonable trivial though, so I guess
I'll try it. The same method could also be used to identify whether
HSW skips parts or rearranges the context dynamically.

-- 
Ville Syrjälä
Intel OTC

  parent reply	other threads:[~2013-08-22 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 16:23 [PATCH] drm/i915: Fix context size calculation on SNB/IVB/VLV ville.syrjala
2013-08-22 18:30 ` Ben Widawsky
2013-08-22 18:45   ` Ville Syrjälä
2013-08-22 18:52   ` Ville Syrjälä [this message]
2013-08-22 18:58     ` Ben Widawsky
2013-08-23  9:54   ` Ville Syrjälä
2013-08-22 19:05 ` Ben Widawsky
2013-08-22 20:16   ` 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=20130822185253.GF29682@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=ben@bwidawsk.net \
    --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