From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: "Juha-Pekka Heikkilä" <juhapekka.heikkila@gmail.com>,
"Clinton Taylor" <Clinton.A.Taylor@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 7/7] tests/kms_ccs: Larger fb to fully cover up the primary plane
Date: Tue, 26 Feb 2019 23:50:23 -0800 [thread overview]
Message-ID: <7b4023699fb3204387d2e1bad93f9f133db2baeb.camel@intel.com> (raw)
In-Reply-To: <cff3fbca-a92b-417f-e26f-27c97f844593@gmail.com>
On Sat, 2019-02-23 at 15:43 +0200, Juha-Pekka Heikkilä wrote:
>
> Clinton Taylor kirjoitti 22.2.2019 klo 18.18:
> >
> > On 2/22/19 6:19 AM, Juha-Pekka Heikkila wrote:
> > > I wouldn't go reverting this limitation. Idea of this test is to
> > > see
> > > if ccs work but not how big planes can be used with ccs. Matt's
> > > patch
> > > was to fix that two planes 1080p problem on APL but if you go see
> > > the
> > > machine https://intel-gfx-ci.01.org/hardware.html#fi-apl-guc
> > > you'll
> > > notice it support 4096x2160@60Hz at highest. After removing this
> > > limitation all you need to do to fail this test is to change the
> > > monitor.
> > >
> >
> > The test has been changed to the current active size of the pipe
> > and not
> > the maximum size supported by the hardware.
> >
>
> I didn't understand the reasoning. This test did fail on different
> machines because of plane sizes which required more bandwith than
> was
> available in budget.
There is just
one primary plane scanning out a fb sized to match connector's default
mode
an overlay scanning out a fb of size 256x256.
This to me is a reasonable configuration that should not exceeding any
hardware limits. The commit that changes the primary fb size does not
specifically call out which platforms the problem was on and what exact
hardware limit the test exceeds.
> Watermark calculation was adjusted but it doesn't
> change limitations on hardware.
Looking at the bug, it does seem like the real problem was the second
plane not meeting the minimum watermark limits due to a buggy watermark
algorithm. And that problem has been fixed. If you see the original
list of failures, it is across all platforms and the test fails only
when both primary and sprite plane are enabled.
>
> Is there benefit in reindroducing this point of failure?
There is not much point in testing an artificial configuration (2000 *
vdisplay) in order to make the test pass. We should know when a sane
configuration fails so that it can be debugged.
>
> /Juha-Pekka
>
> >
> >
> > > This igt test was originally limited due to this machine
> > > https://intel-gfx-ci.01.org/hardware.html#fi-kbl-soraka which is
> > > meant
> > > to be Chromebook with 2400x1600 size display. Quickly looking it
> > > seems
> > > Soraka has not been recently running so much CI runs though.
> > >
> > > /Juha-Pekka
> > >
> > > On 21.2.2019 16.41, Dhinakaran Pandiyan wrote:
> > > > This is a revert of commit 27fa97d16294 ("tests/kms_ccs: Avoid
> > > > using
> > > > plane
> > > > sizes which exceed hw capability"). The watermarks issue that
> > > > the patch
> > > > refers to has been fixed as per the bugzilla, so let's use an
> > > > fb that
> > > > covers the whole screen.
> > > >
> > > > Cc: Clinton Taylor <clinton.a.taylor@intel.com>
> > > > Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> > > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > References: https://bugs.freedesktop.org/show_bug.cgi?id=105458
> > > > Signed-off-by: Dhinakaran Pandiyan <
> > > > dhinakaran.pandiyan@intel.com>
> > > > ---
> > > > tests/kms_ccs.c | 16 +++-------------
> > > > 1 file changed, 3 insertions(+), 13 deletions(-)
> > > >
> > > > diff --git a/tests/kms_ccs.c b/tests/kms_ccs.c
> > > > index 8cbf100f..48f10af0 100644
> > > > --- a/tests/kms_ccs.c
> > > > +++ b/tests/kms_ccs.c
> > > > @@ -69,15 +69,6 @@ const struct {
> > > > {0.0, 1.0, 0.0}
> > > > };
> > > > -/*
> > > > - * Limit maximum used sprite plane width so this test will
> > > > not
> > > > mistakenly
> > > > - * fail on hardware limitations which are not interesting to
> > > > this test.
> > > > - * On this test too wide sprite plane may fail during creation
> > > > with
> > > > dmesg
> > > > - * comment saying:
> > > > - * "Requested display configuration exceeds system watermark
> > > > limitations"
> > > > - */
> > > > -#define MAX_SPRITE_PLANE_WIDTH 2000
> > > > -
> > > > struct local_drm_format_modifier {
> > > > /* Bitmask of formats in get_plane format list this
> > > > info
> > > > applies to. The
> > > > * offset allows a sliding window of which 64 formats
> > > > (bits).
> > > > @@ -313,13 +304,12 @@ static bool try_config(data_t *data,
> > > > enum
> > > > test_fb_flags fb_flags,
> > > > if (data->plane && fb_flags & FB_COMPRESSED) {
> > > > if (!plane_has_format_with_ccs(data, data->plane,
> > > > DRM_FORMAT_XRGB8888))
> > > > return false;
> > > > - generate_fb(data, &fb, min(MAX_SPRITE_PLANE_WIDTH,
> > > > drm_mode->hdisplay),
> > > > - drm_mode->vdisplay,
> > > > + generate_fb(data, &fb, drm_mode->hdisplay, drm_mode-
> > > > >vdisplay,
> > > > (fb_flags & ~FB_COMPRESSED) | FB_HAS_PLANE);
> > > > generate_fb(data, &fb_sprite, 256, 256, fb_flags);
> > > > } else {
> > > > - generate_fb(data, &fb, min(MAX_SPRITE_PLANE_WIDTH,
> > > > drm_mode->hdisplay),
> > > > - drm_mode->vdisplay, fb_flags);
> > > > + generate_fb(data, &fb, drm_mode->hdisplay, drm_mode-
> > > > >vdisplay,
> > > > + fb_flags);
> > > > }
> > > > if (data->flags & TEST_FAIL_ON_ADDFB2)
> > > >
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-27 7:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 14:41 [igt-dev] [PATCH i-g-t 0/7] Use rendercopy for generating CCS buffers Dhinakaran Pandiyan
2019-02-21 14:41 ` [igt-dev] [PATCH i-g-t 1/7] lib/rendercopy: Add support for Yf/Ys tiling to gen9 rendercopy Dhinakaran Pandiyan
2019-02-25 13:39 ` Katarzyna Dec
2019-02-26 21:00 ` Pandiyan, Dhinakaran
2019-02-27 12:56 ` Katarzyna Dec
2019-03-01 20:17 ` Dhinakaran Pandiyan
2019-02-21 14:41 ` [igt-dev] [PATCH i-g-t 2/7] tests/gem_render_copy: Test Yf tiling Dhinakaran Pandiyan
2019-02-25 13:49 ` Katarzyna Dec
2019-03-05 1:50 ` Dhinakaran Pandiyan
2019-02-21 14:41 ` [igt-dev] [PATCH i-g-t 3/7] lib/igt_fb: Use rendercopy for rendering into compressed buffers Dhinakaran Pandiyan
2019-02-21 18:04 ` [igt-dev] [PATCH i-g-t v2 3/8] " Dhinakaran Pandiyan
2019-02-21 14:41 ` [igt-dev] [PATCH i-g-t 4/7] lib/igt_fb: s/tiling/modifier/ where appropriate Dhinakaran Pandiyan
2019-02-21 18:05 ` [igt-dev] [PATCH i-g-t v2 4/8] " Dhinakaran Pandiyan
2019-02-21 14:41 ` [igt-dev] [PATCH i-g-t 5/7] lib/igt_fb: Function to create a bo for passed in igt_fb Dhinakaran Pandiyan
2019-02-22 16:20 ` Ville Syrjälä
2019-02-21 14:41 ` [igt-dev] [PATCH i-g-t 6/7] tests/kms_ccs: Generate compressed surfaces with rendercopy Dhinakaran Pandiyan
2019-02-22 16:13 ` Ville Syrjälä
2019-02-21 14:41 ` [igt-dev] [PATCH i-g-t 7/7] tests/kms_ccs: Larger fb to fully cover up the primary plane Dhinakaran Pandiyan
2019-02-22 14:19 ` Juha-Pekka Heikkila
2019-02-22 16:18 ` Clinton Taylor
2019-02-23 13:43 ` Juha-Pekka Heikkilä
2019-02-27 7:50 ` Dhinakaran Pandiyan [this message]
2019-02-27 14:18 ` Ville Syrjälä
2019-02-21 22:37 ` [igt-dev] ✓ Fi.CI.BAT: success for Use rendercopy for generating CCS buffers Patchwork
2019-02-22 10:57 ` [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=7b4023699fb3204387d2e1bad93f9f133db2baeb.camel@intel.com \
--to=dhinakaran.pandiyan@intel.com \
--cc=Clinton.A.Taylor@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox