From: Michel Thierry <michel.thierry@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH v2] drm/i915: limit PPGTT size to 2GB in 32-bit platforms
Date: Fri, 29 May 2015 09:58:33 +0100 [thread overview]
Message-ID: <55682A39.4070501@intel.com> (raw)
In-Reply-To: <20150528211450.GJ19710@nuc-i3427.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 2030 bytes --]
On 5/28/2015 10:14 PM, Chris Wilson wrote:
> On Thu, May 28, 2015 at 06:09:34PM +0100, Michel Thierry wrote:
>> And prevent overflow warning during compilation. We already set this limit
>> for the GGTT.
>>
>> This is a temporary patch until a full replacement of size_t variables
>> (inadequate in 32-bit kernel) is in place.
>>
>> Regression from:
>> commit a4e0bedca678c81eea4cd79a4bd502335639f73a
>> Author: Michel Thierry <michel.thierry@intel.com>
>> Date: Wed Apr 8 12:13:35 2015 +0100
>>
>> drm/i915: Use complete address space in true PPGTT
>>
>> v2: Prettify code and explain why this is needed. (Chris)
>>
>> Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_gem_gtt.c | 11 ++++++++++-
>> 1 file changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
>> index 17b7df0..0653c28 100644
>> --- a/drivers/gpu/drm/i915/i915_gem_gtt.c
>> +++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
>> @@ -951,7 +951,16 @@ static int gen8_ppgtt_init(struct i915_hw_ppgtt *ppgtt)
>> gen8_initialize_pd(&ppgtt->base, ppgtt->scratch_pd);
>>
>> ppgtt->base.start = 0;
>> - ppgtt->base.total = 1ULL << 32;
>> +#ifdef CONFIG_X86_32
>> + /* While we have a proliferation of size_t variables
>> + * we cannot represent the full ppgtt size on 32bit,
>> + * so limit it to the same size as the GGTT (currently
>> + * 2GiB).
>> + */
>> + ppgtt->base.total = to_i915(ppgtt->base.dev)->gtt.base.total;
>> +#else
>> + ppgtt->base.total = 1ULL << 32;
>> +#endif
> You missed the point of having it always compiled. Part of that is that
> the compiler warning here is important.
> -Chris
I was under the impression that Daniel wanted to get rid of the warning
too, that's why I didn't use IS_ENABLED().
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5510 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
next prev parent reply other threads:[~2015-05-29 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 15:24 [PATCH] drm/i915: limit PPGTT size to 2GB in 32-bit platforms Michel Thierry
2015-05-28 15:39 ` Chris Wilson
2015-05-28 15:59 ` Michel Thierry
2015-05-28 17:09 ` [PATCH v2] " Michel Thierry
2015-05-28 17:47 ` Damien Lespiau
2015-05-28 21:14 ` Chris Wilson
2015-05-29 8:58 ` Michel Thierry [this message]
2015-05-29 12:41 ` Chris Wilson
2015-05-29 13:15 ` [PATCH v3] " Michel Thierry
2015-05-29 17:08 ` 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=55682A39.4070501@intel.com \
--to=michel.thierry@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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.