public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: michel.thierry@intel.com
Cc: intel-gfx@lists.freedesktop.org,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: drm/i915/gen8: page directories rework allocation
Date: Thu, 30 Apr 2015 13:27:54 +0100	[thread overview]
Message-ID: <55421FCA.1090100@intel.com> (raw)
In-Reply-To: <20150430104745.GA25329@mwanda>

On 30/04/15 11:47, Dan Carpenter wrote:
> Hi Michel,
> 
> The patch 69876bed7e00: "drm/i915/gen8: page directories rework
> allocation" from Apr 8, 2015, has the following issue:
> 
> 	drivers/gpu/drm/i915/i915_gem_gtt.c:760
> 	warn: too many zeroes
> 
> drivers/gpu/drm/i915/i915_gem_gtt.c
>    746  static int gen8_ppgtt_alloc_page_directories(struct i915_hw_ppgtt *ppgtt,
>    747                                       struct i915_page_directory_pointer *pdp,
>    748                                       uint64_t start,
>    749                                       uint64_t length,
>    750                                       unsigned long *new_pds)
>    751  {
>    752          struct drm_device *dev = ppgtt->base.dev;
>    753          struct i915_page_directory *pd;
>    754          uint64_t temp;
>    755          uint32_t pdpe;
>    756  
>    757          WARN_ON(!bitmap_empty(new_pds, GEN8_LEGACY_PDPES));
>    758  
>    759          /* FIXME: PPGTT container_of won't work for 64b */
>    760          WARN_ON((start + length) > 0x800000000ULL);
>                                                      ^
> This last zero was not intended.

Wouldn't (1ULL << 31) be clearer?

And shouldn't it be >= not > ?

Or perhaps,
	/* FIXME: upper bound must not overflow 31 bits */
	WARN_ON((start + length) & (~0ULL << 31));

Pick whichever you think is most comprehensible and least typo-prone!

.Dave.

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

  reply	other threads:[~2015-04-30 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 10:47 drm/i915/gen8: page directories rework allocation Dan Carpenter
2015-04-30 12:27 ` Dave Gordon [this message]
2015-04-30 13:59 ` [PATCH] drm/i915: Fix 32b overflow check in gen8_ppgtt_alloc_page_directories Michel Thierry
2015-04-30 14:22   ` Ville Syrjälä
2015-04-30 14:33     ` Michel Thierry
2015-04-30 14:53       ` Dave Gordon
2015-04-30 14:56         ` Michel Thierry
2015-04-30 14:58         ` Ville Syrjälä
2015-05-02  0:38   ` shuang.he
2015-05-04 12:57   ` David Weinehall
2015-04-30 15:06 ` [PATCH v2] " Michel Thierry
2015-05-02  4:26   ` shuang.he
2015-05-06 10:14   ` 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=55421FCA.1090100@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=dan.carpenter@oracle.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michel.thierry@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox