From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>,
stable@vger.kernel.org,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH] [v3] drm/i915/bdw: Only use 2g GGTT for 32b platforms
Date: Mon, 19 May 2014 08:13:30 -0700 [thread overview]
Message-ID: <20140519081330.27d79cd5@jbarnes-desktop> (raw)
In-Reply-To: <87oaz22khl.fsf@intel.com>
On Tue, 13 May 2014 10:41:58 +0300
Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Thu, 08 May 2014, Ben Widawsky <benjamin.widawsky@intel.com> wrote:
> > Daniel requested in the bug that I use a 3GB fallback size. Since this
> > is not in the spec as a valid size, I decided against it. We could
> > potentially add a patch to bump it to 3GB on top of this one.
> >
> > This probably should be CC: stable - but I'll let the powers that be
> > decide that one.
> >
> > Regression from a revert of the revert:
> > commit 7907f45bf9f67a1c5e5d4ae05bab428d7c2f43b2
> > Author: Ben Widawsky <benjamin.widawsky@intel.com>
> > Date: Wed Feb 19 22:05:46 2014 -0800
> >
> > Revert "drm/i915/bdw: Limit GTT to 2GB"
> >
> > v2: Change ifdef to 32b, instead of ifndef
> > update comment
> >
> > v3. Update comment to not wrap (Daniel).
> > Update commit message
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=76619
> > Cc: stable@vger.kernel.org
> > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > ---
> > drivers/gpu/drm/i915/i915_gem_gtt.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
> > index 4d87bf2..8d6d531 100644
> > --- a/drivers/gpu/drm/i915/i915_gem_gtt.c
> > +++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
> > @@ -2640,6 +2640,13 @@ static inline unsigned int gen8_get_total_gtt_size(u16 bdw_gmch_ctl)
> > bdw_gmch_ctl &= BDW_GMCH_GGMS_MASK;
> > if (bdw_gmch_ctl)
> > bdw_gmch_ctl = 1 << bdw_gmch_ctl;
> > +
> > +#ifdef CONFIG_32BIT
>
> There's no such config for x86.
>
> There's CONFIG_X86_32 though. Which I think matches the original
> approach of #ifndef CONFIG_64BIT in the referenced bug. However, "with
> this patch only, the system still hung while booting." [1].
>
> I want a new patch with Tested-by on it.
>
>
> BR,
> Jani.
>
>
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=76619#c16
Ben, will you re-post this or can you find someone else who can?
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-05-19 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 4:58 [PATCH] drm/i915/bdw: Only use 2g GGTT for 32b platforms Ben Widawsky
2014-05-07 7:42 ` Daniel Vetter
2014-05-08 1:21 ` Ben Widawsky
2014-05-08 6:25 ` Jani Nikula
2014-05-12 16:42 ` Daniel Vetter
2014-05-08 2:17 ` [PATCH] [v3] " Ben Widawsky
2014-05-13 7:41 ` [Intel-gfx] " Jani Nikula
2014-05-19 15:13 ` Jesse Barnes [this message]
2014-05-19 22:46 ` [PATCH] " Rodrigo Vivi
2014-05-20 7:15 ` Chris Wilson
2014-05-20 7:55 ` 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=20140519081330.27d79cd5@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=stable@vger.kernel.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