From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib/igt_fb: Don't use blitter for large buffers
Date: Wed, 3 Apr 2019 18:24:40 +0300 [thread overview]
Message-ID: <20190403152440.GY3888@intel.com> (raw)
In-Reply-To: <05991cf0bab4f5aab44944bbc5cdd4ec01ea20af.camel@intel.com>
On Tue, Apr 02, 2019 at 03:41:43PM -0700, Dhinakaran Pandiyan wrote:
> On Thu, 2019-03-28 at 18:25 +0000, Chris Wilson wrote:
> > Quoting Ville Syrjala (2019-03-28 17:54:49)
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > The blitter stride is limited to <32k. Fall back to gtt mmap or
> > > rendercopy if we're about to exceed that.
> > >
> > > Not quite sure why we're not just using gtt mmap for Y tiling
> > > always. But let's keep it like that for now.
> > >
> > > v2: Use rendercopy as the fallback for Yf
> > >
> > > Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > ---
> > > lib/igt_fb.c | 25 ++++++++++++++++++-------
> > > 1 file changed, 18 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/lib/igt_fb.c b/lib/igt_fb.c
> > > index fcd7c4c5d187..8b6adf55a338 100644
> > > --- a/lib/igt_fb.c
> > > +++ b/lib/igt_fb.c
> > > @@ -1502,6 +1502,20 @@ struct fb_blit_upload {
> > > struct intel_batchbuffer *batch;
> > > };
> > >
> > > +static bool use_rendercopy(const struct igt_fb *fb)
> > > +{
> > > + return is_ccs_modifier(fb->modifier) ||
> > > + (fb->modifier == I915_FORMAT_MOD_Yf_TILED &&
> > > + fb->strides[0] >= 32768);
> >
> > And probably wise to assert <= 256k.
> Is that a hardware limitation for the render engine?
I think the limits are:
gen2/3: 8k
gen4+: 128k
gen7+: 256k
I guess a 256k check here would make sense since we're only
interested in ccs and yf, and those are gen9+ only. Or maybe
I should just toss some asserts into the rendercopy functions
themselves.
>
> >
> > > +
> > > +static bool use_blitter(const struct igt_fb *fb)
> > > +{
> > > + return (fb->modifier == I915_FORMAT_MOD_Y_TILED ||
> > > + fb->modifier == I915_FORMAT_MOD_Yf_TILED) &&
> > > + fb->strides[0] < 32768;
> >
> > 32k dwords is the limit for tiled blits (on gen4+). I presume strides[]
> > is in bytes.
>
> I see conflicting limits in bspec for this, the Data Size Limitations page says
> "up to 32,768 bytes per scan line" whereas the docs for XY_SRC_COPY_BLT claims
> 32k dwords.
I always found the docs confusing when it comes to the blitter
stride. But the code we have works with the /4 for tiled so it
must be right :) I'll respin with this.
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-03 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 17:54 [igt-dev] [PATCH i-g-t 1/2] lib/igt_fb: Don't use blitter for large buffers Ville Syrjala
2019-03-28 17:54 ` [igt-dev] [PATCH i-g-t 2/2] lib/igt_fb: Don't leak the bufmgr and batch for converted surfaces Ville Syrjala
2019-04-02 23:01 ` Dhinakaran Pandiyan
2019-03-28 18:17 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] lib/igt_fb: Don't use blitter for large buffers Patchwork
2019-03-28 18:25 ` [igt-dev] [PATCH i-g-t 1/2] " Chris Wilson
2019-04-02 22:41 ` Dhinakaran Pandiyan
2019-04-03 15:24 ` Ville Syrjälä [this message]
2019-03-29 4:20 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2] " Patchwork
2019-04-08 17:13 ` [igt-dev] [PATCH i-g-t v3 1/2] " Ville Syrjala
2019-04-08 17:19 ` Chris Wilson
2019-04-08 17:20 ` Chris Wilson
2019-04-09 12:25 ` Ville Syrjälä
2019-04-09 19:49 ` Chris Wilson
2019-04-09 20:12 ` Ville Syrjälä
2019-04-08 18:02 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v3,1/2] lib/igt_fb: Don't use blitter for large buffers (rev2) Patchwork
2019-04-08 21:09 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190403152440.GY3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=igt-dev@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.