From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+
Date: Tue, 14 Jul 2020 22:50:21 +0300 [thread overview]
Message-ID: <20200714195021.GP6112@intel.com> (raw)
In-Reply-To: <159475398330.3188.2132224433232566770@build.alporthouse.com>
On Tue, Jul 14, 2020 at 08:13:03PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2020-07-14 19:51:28)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Since g4x the CFB base only takes a 28bit offset into stolen.
> > Not sure if the CFB is allowed to start below that limit but
> > then extend beyond it. Let's assume not and just restrict the
> > allocation to the first 256MiB (in the unlikely case
> > we have more stolen than that).
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_fbc.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> > index 85723fba6002..448e966bad11 100644
> > --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> > @@ -424,6 +424,14 @@ static void intel_fbc_deactivate(struct drm_i915_private *dev_priv,
> > fbc->no_fbc_reason = reason;
> > }
> >
> > +static u64 intel_fbc_cfb_base_max(struct drm_i915_private *i915)
> > +{
> > + if (INTEL_GEN(i915) >= 5 || IS_G4X(i915))
> > + return BIT(28);
> > + else
> > + return BIT(32);
>
> BIT_ULL(32)
Argh. I should stop being lazy and always test build 32bit
locally. Also, 'long' really is the most annoying type ever.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-07-14 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 18:51 [Intel-gfx] [PATCH] drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+ Ville Syrjala
2020-07-14 19:13 ` Chris Wilson
2020-07-14 19:50 ` Ville Syrjälä [this message]
2020-07-14 19:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-07-14 19:56 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-07-14 20:19 ` [Intel-gfx] [PATCH v2] " Ville Syrjala
2020-07-14 20:32 ` Chris Wilson
2020-07-15 14:22 ` Ville Syrjälä
2020-07-15 15:17 ` Chris Wilson
2020-07-14 21:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+ (rev2) Patchwork
2020-07-14 21:37 ` [Intel-gfx] [PATCH] drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+ kernel test robot
2020-07-14 21:37 ` kernel test robot
2020-07-15 1:41 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/fbc: Limit cfb to the first 256MiB of stolen on g4x+ (rev2) Patchwork
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=20200714195021.GP6112@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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.