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: [PATCH v3 7/8] drm/i915: Bump gen4+ fb stride limit to 256KiB
Date: Fri, 28 Sep 2018 22:19:26 +0300 [thread overview]
Message-ID: <20180928191926.GE9144@intel.com> (raw)
In-Reply-To: <153790642172.21139.11842161193789382805@skylake-alporthouse-com>
On Tue, Sep 25, 2018 at 09:13:41PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2018-09-25 20:37:13)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > With gtt remapping plugged in we can simply raise the stride
> > limit on gen4+. Let's just arbitraily pick 256 KiB as the limit.
> >
> > No remapping CCS because the virtual address of each page actually
> > matters due to the new hash mode
> > (WaCompressedResourceDisplayNewHashMode:skl,kbl etc.), and no remapping
> > on gen2/3 due to lack of fence on the remapped vma.
> >
> > v2: Rebase due to is_ccs_modifier()
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index eca873653fea..d533a6086169 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -2522,6 +2522,19 @@ static
> > u32 intel_fb_max_stride(struct drm_i915_private *dev_priv,
> > u32 pixel_format, u64 modifier)
> > {
> > + /*
> > + * Arbitrary limit for gen4+. We can deal with any page
> > + * aligned stride via GTT remapping. Gen2/3 need a fence
> > + * for tiled scanout which the remapped vma won't have,
> > + * so we don't allow remapping on those platforms.
> > + *
> > + * Also the new hash mode we use for CCS isn't compatible
> > + * with remapping as the virtual address of the pages
> > + * affects the compressed data.
> > + */
> > + if (INTEL_GEN(dev_priv) >= 4 && !is_ccs_modifier(modifier))
> > + return 256*1024;
>
> Worth using SZ_256K ?
That question prompted me to try a mass conversion. Managed to trick
cocci to do it more or less. Unfortunately it was a bit too greedy
and converted non-pot sizes as well. Not sure how much the SZ_ things
are worth due to that reason.
I couldn't get cocci to do what I wanted with ## so had to resort
to python. I get the impression that ## only works with identifiers.
Here's what I ended with in case anyone wants to evaluate for
themselves:
@find_m@
constant old_m =~ "^[0-9]*$";
@@
old_m * 1024 * 1024
@script:python rename_m@
input << find_m.old_m;
new_m;
@@
def do_rename_m(name):
return "SZ_" + name + "M"
coccinelle.new_m = cocci.make_ident(do_rename_m(input))
print coccinelle.new_m
@@
constant find_m.old_m;
identifier rename_m.new_m;
@@
- old_m * 1024 * 1024
+ new_m
@find_k@
constant old_k =~ "^[0-9]*$";
@@
old_k * 1024
@@
@@
- 1024 * 1024
+ SZ_1M
@script:python rename_k@
input << find_k.old_k;
new_k;
@@
def do_rename_k(name):
return "SZ_" + name + "K"
coccinelle.new_k = cocci.make_ident(do_rename_k(input))
print coccinelle.new_k
@@
constant find_k.old_k;
identifier rename_k.new_k;
@@
- old_k * 1024
+ new_k
--
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:[~2018-09-28 19:19 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 19:37 [PATCH v3 0/8] drm/i915: GTT remapping for display Ville Syrjala
2018-09-25 19:37 ` [PATCH v3 1/8] drm/i915: Make sure fb gtt offsets stay within 32bits Ville Syrjala
2018-09-25 20:29 ` Chris Wilson
2018-09-26 9:27 ` Ville Syrjälä
2018-09-26 20:09 ` Chris Wilson
2018-09-27 12:24 ` Ville Syrjälä
2018-10-23 16:02 ` [PATCH v4 " Ville Syrjala
2018-10-23 18:49 ` Chris Wilson
2018-10-23 19:16 ` Ville Syrjälä
2018-09-25 19:37 ` [PATCH v3 2/8] drm/i915: Decouple SKL stride units from intel_fb_stride_alignment() Ville Syrjala
2018-10-23 18:50 ` Chris Wilson
2018-09-25 19:37 ` [PATCH v3 3/8] drm/i915: Add a new "remapped" gtt_view Ville Syrjala
2018-09-26 7:50 ` Tvrtko Ursulin
2018-10-01 15:03 ` Ville Syrjälä
2018-10-01 15:12 ` Chris Wilson
2018-10-01 15:27 ` Ville Syrjälä
2018-10-01 15:37 ` Chris Wilson
2018-10-01 15:48 ` Tvrtko Ursulin
2018-10-05 18:42 ` Ville Syrjälä
2018-10-09 8:24 ` Tvrtko Ursulin
2018-10-09 8:41 ` Chris Wilson
2018-10-09 11:54 ` Ville Syrjälä
2018-10-10 7:04 ` Tvrtko Ursulin
2018-10-01 15:38 ` Tvrtko Ursulin
2018-10-01 15:35 ` Tvrtko Ursulin
2018-10-23 16:02 ` [PATCH v4 " Ville Syrjala
2018-10-23 18:56 ` Chris Wilson
2018-10-23 19:10 ` Ville Syrjälä
2018-10-26 9:19 ` Tvrtko Ursulin
2018-10-26 12:43 ` Ville Syrjälä
2018-10-26 12:48 ` Tvrtko Ursulin
2018-09-25 19:37 ` [PATCH v3 4/8] drm/i915/selftests: Add mock selftest for remapped vmas Ville Syrjala
2018-09-25 20:22 ` Chris Wilson
2018-09-26 9:28 ` Ville Syrjälä
2018-10-23 16:03 ` [PATCH v4 " Ville Syrjala
2018-10-23 19:02 ` Chris Wilson
2018-10-23 19:14 ` Ville Syrjälä
2018-09-25 19:37 ` [PATCH v3 5/8] drm/i915/selftests: Add live vma selftest Ville Syrjala
2018-09-25 20:19 ` Chris Wilson
2018-09-25 20:40 ` Chris Wilson
2018-09-26 9:33 ` Ville Syrjälä
2018-10-23 16:03 ` [PATCH v4 " Ville Syrjala
2018-10-23 19:05 ` Chris Wilson
2018-09-25 19:37 ` [PATCH v3 6/8] drm/i915: Overcome display engine stride limits via GTT remapping Ville Syrjala
2018-10-23 19:16 ` Chris Wilson
2018-10-25 13:45 ` Ville Syrjälä
2018-09-25 19:37 ` [PATCH v3 7/8] drm/i915: Bump gen4+ fb stride limit to 256KiB Ville Syrjala
2018-09-25 20:13 ` Chris Wilson
2018-09-28 19:19 ` Ville Syrjälä [this message]
2018-09-25 19:37 ` [PATCH v3 8/8] drm/i915: Bump gen7+ fb size limits to 16kx16k Ville Syrjala
2018-09-25 19:59 ` Chris Wilson
2018-09-26 9:25 ` Ville Syrjälä
2018-09-25 20:05 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: GTT remapping for display Patchwork
2018-09-25 20:08 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-09-25 20:30 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-25 21:21 ` ✓ Fi.CI.IGT: " Patchwork
2018-10-23 16:21 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: GTT remapping for display (rev5) Patchwork
2018-10-23 16:24 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-10-23 16:43 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-23 18:13 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-09 9:45 ` [PATCH v3 0/8] drm/i915: GTT remapping for display Timo Aaltonen
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=20180928191926.GE9144@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).