All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Thomas Daniel <thomas.daniel@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Shift driver's HWSP usage out of reserved range
Date: Thu, 19 Feb 2015 14:58:48 +0000	[thread overview]
Message-ID: <54E5FA28.8020407@intel.com> (raw)
In-Reply-To: <1424260101-18122-1-git-send-email-thomas.daniel@intel.com>

On 18/02/15 11:48, Thomas Daniel wrote:
> As of Gen6, the general purpose area of the hardware status page has shrunk and
> now begins at dword 0x30.  i915 driver uses dword 0x20 to store the seqno which
> is now reserved.  So shift our HWSP dwords up into the general purpose range
> before this bites us.
> 
> Signed-off-by: Thomas Daniel <thomas.daniel@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_ringbuffer.h |    7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.h b/drivers/gpu/drm/i915/intel_ringbuffer.h
> index b6c484f..39183fc 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.h
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.h
> @@ -373,11 +373,12 @@ intel_write_status_page(struct intel_engine_cs *ring,
>   * 0x06: ring 2 head pointer (915-class)
>   * 0x10-0x1b: Context status DWords (GM45)
>   * 0x1f: Last written status offset. (GM45)
> + * 0x20-0x2f: Reserved (Gen6+)
>   *
> - * The area from dword 0x20 to 0x3ff is available for driver usage.
> + * The area from dword 0x30 to 0x3ff is available for driver usage.
>   */
> -#define I915_GEM_HWS_INDEX		0x20
> -#define I915_GEM_HWS_SCRATCH_INDEX	0x30
> +#define I915_GEM_HWS_INDEX		0x30
> +#define I915_GEM_HWS_SCRATCH_INDEX	0x40
>  #define I915_GEM_HWS_SCRATCH_ADDR (I915_GEM_HWS_SCRATCH_INDEX << MI_STORE_DWORD_INDEX_SHIFT)
>  
>  void intel_unpin_ringbuffer_obj(struct intel_ringbuffer *ringbuf);

Well, nothing much can go wnorg here!

Reviewed-by: Dave Gordon <david.s.gordon@intel.com>

But just FYI, these will all get changed again when we add support for
preemption (: because then we'll need more than one place to store
'sequence numbers' :)

.Dave.

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

  parent reply	other threads:[~2015-02-19 14:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 11:48 [PATCH] drm/i915: Shift driver's HWSP usage out of reserved range Thomas Daniel
2015-02-18 14:22 ` shuang.he
2015-02-19 14:58 ` Dave Gordon [this message]
2015-02-23 23:27   ` Daniel Vetter
2015-02-24 10:20     ` Daniel, Thomas
2015-02-24 10:51       ` 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=54E5FA28.8020407@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thomas.daniel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.