From: Chris Wilson <chris@chris-wilson.co.uk>
To: Simon Farnsworth <simon.farnsworth@onelan.com>,
intel-gfx@lists.freedesktop.org
Cc: t.artem@mailcity.com
Subject: Re: [PATCH] drm/agp/i915: trim stolen space to 32M
Date: Thu, 08 Jul 2010 17:42:19 +0100 [thread overview]
Message-ID: <89k77n$oab77c@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <201007081737.10942.simon.farnsworth@onelan.com>
On Thu, 8 Jul 2010 17:37:10 +0100, Simon Farnsworth <simon.farnsworth@onelan.com> wrote:
> On Thursday 8 July 2010, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > Some BIOSes will claim a large chunk of stolen space. Unless we
> > reclaim it, our aperture for remapping buffer objects will be
> > constrained. So clamp the stolen space to 32M and ignore the rest.
> >
> > Fixes https://bugzilla.kernel.org/show_bug.cgi?id=15469 among others.
> >
> > Adding the ignored stolen memory back into the general pool using the
> > memory hotplug code is left as an exercise for the reader.
> >
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
>
> FWIW, given how simple the code actually is:
> Reviewed-by: Simon Farnsworth <simon.farnsworth@onelan.com>
Heh, you were meant to say:
"What? Export a magic parameter from intel-gtt.c to indicate how much
space to remove from the aperture guestimate, but not replace the *broken*
code in i915_dma.c with an interface from intel-gtt.c to query and control
the populated GTT more precisely?"
;-)
-ickle
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-07-08 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 16:22 [PATCH] drm/agp/i915: trim stolen space to 32M Jesse Barnes
2010-07-08 16:37 ` Simon Farnsworth
2010-07-08 16:42 ` Chris Wilson [this message]
2010-07-08 16:52 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2010-07-07 21:40 Jesse Barnes
2010-07-08 9:58 ` Simon Farnsworth
2010-07-08 16:01 ` Jesse Barnes
2010-07-08 16:15 ` Jesse Barnes
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='89k77n$oab77c@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=simon.farnsworth@onelan.com \
--cc=t.artem@mailcity.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.