From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <benjamin.widawsky@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH 4/4] drm/i915: Reserve space for FBC (fbcon)
Date: Thu, 19 Jun 2014 20:28:11 +0100 [thread overview]
Message-ID: <20140619192811.GD8476@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1403204773-7112-4-git-send-email-benjamin.widawsky@intel.com>
On Thu, Jun 19, 2014 at 12:06:13PM -0700, Ben Widawsky wrote:
> This is one part in a few fixes needed to make FBC work with limited
> stolen memory and large resolution displays. It is not the full
> solution, but one (easy) step.
>
> The patch is straight-forward, it attempts to check there will be room
> for FBC before trying to "reclaim"
But it special cases one particular allocation. Why don't you just
reserve stolen upfront for FBC? Compute the maximum buffer size the
hardware could support and try to claim it during stolen init.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-06-19 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 19:06 [PATCH 1/4] drm/i915: Move compressed_fb to static allocation Ben Widawsky
2014-06-19 19:06 ` [PATCH 2/4] drm/i915: Extract CFB threshold calculation Ben Widawsky
2014-07-01 0:16 ` Rodrigo Vivi
2014-06-19 19:06 ` [PATCH 3/4] drm/i915: Try harder to get FBC Ben Widawsky
2014-06-20 15:56 ` Runyan, Arthur J
2014-06-20 16:55 ` Ben Widawsky
2014-06-30 17:41 ` [PATCH] " Rodrigo Vivi
2014-07-01 16:09 ` Rodrigo Vivi
2014-07-03 11:52 ` Jani Nikula
2014-06-19 19:06 ` [PATCH 4/4] drm/i915: Reserve space for FBC (fbcon) Ben Widawsky
2014-06-19 19:28 ` Chris Wilson [this message]
2014-06-19 19:41 ` Ben Widawsky
2014-07-01 3:34 ` Ben Widawsky
2014-07-01 0:15 ` [PATCH 1/4] drm/i915: Move compressed_fb to static allocation Rodrigo Vivi
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=20140619192811.GD8476@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--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.