All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/i915: Replace 4096 with PAGE_SIZE or I915_GTT_PAGE_SIZE
Date: Tue, 10 Jan 2017 18:17:42 +0200	[thread overview]
Message-ID: <1484065062.3237.33.camel@linux.intel.com> (raw)
In-Reply-To: <20170110144734.26052-1-chris@chris-wilson.co.uk>

On ti, 2017-01-10 at 14:47 +0000, Chris Wilson wrote:
> Start converting over from the byte count to its semantic macro, either
> we want to allocate the size of a physical page in main memory or we
> want the size of a virtual page in the GTT. 4096 could mean either, but
> PAGE_SIZE and I915_GTT_PAGE_SIZE are explicit and should help improve
> code comprehension and future changes. In the future, we may want to use
> variable GTT page sizes and so have the challenge of knowing which
> hardcoded values were used to represent a physical page vs the virtual
> page.
> 
> v2: Look for a few more 4096s to convert, discover IS_ALIGNED().
> v3: 4096ul paranoia, make fence alignment a distinct value of 4096, keep
> bdw stolen w/a as 4096 until we know better.
> v4: Add asserts that i915_vma_insert() start/end are aligned to GTT page
> sizes.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

<SNIP>

> +++ b/drivers/gpu/drm/i915/i915_gem_fence_reg.h
> @@ -47,5 +47,7 @@ struct drm_i915_fence_reg {
> >  	bool dirty;
>  };
>  
> +#define I965_FENCE_PAGE 4096UL

I'm pretty sure I'd look for this from the very top of the file before
structs. Any specific reason not there?

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-01-10 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 12:15 [PATCH] drm/i915: Replace 4096 with PAGE_SIZE or I915_GTT_PAGE_SIZE Chris Wilson
2017-01-10 13:55 ` Joonas Lahtinen
2017-01-10 14:02   ` Chris Wilson
2017-01-10 14:16   ` Chris Wilson
2017-01-10 14:25   ` Chris Wilson
2017-01-10 14:47 ` [PATCH v4] " Chris Wilson
2017-01-10 16:17   ` Joonas Lahtinen [this message]
2017-01-10 17:02     ` Chris Wilson
2017-01-10 20:57     ` Chris Wilson
2017-01-10 18:23 ` ✗ Fi.CI.BAT: warning for drm/i915: Replace 4096 with PAGE_SIZE or I915_GTT_PAGE_SIZE (rev3) Patchwork

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=1484065062.3237.33.camel@linux.intel.com \
    --to=joonas.lahtinen@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 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.