From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH RESEND i-g-t 2/2] kms_frontbuffer_tracking: Don't poke compressing status for old cpus
Date: Wed, 26 Apr 2017 21:12:18 +0300 [thread overview]
Message-ID: <20170426181218.GH30290@intel.com> (raw)
In-Reply-To: <87fugv6ogy.fsf@dilma.collabora.co.uk>
On Wed, Apr 26, 2017 at 02:57:49PM -0300, Gabriel Krisman Bertazi wrote:
> Paulo Zanoni <paulo.r.zanoni@intel.com> writes:
>
> > Ouch... Good catch!
> >
> > Can you please move the logic to the setup_fbc() function?
> >
> > if (gen < 7)
> > opt.fbc_check_compression = false;
> >
> > This way we avoid redoing the same check a trillion times during
> > kms_frontbuffer_tracking execution.
> >
> > Also, I think this one also lacks a Bugzilla tag:
> > https://bugs.freedesktop.org/show_bug.cgi?id=100677
>
> Hmm, yeah, I forgot CC'ing the list when resending. Sorry about that.
>
> Thanks for reviewing. Can you take a look at the following version
> instead?
>
> >8
> Subject: [PATCH] kms_frontbuffer_tracking: Don't poke compressing status for
> old cpus
>
> Commit 2804afc606f8 ("kms_frontbuffer_tracking: fix compression
> checking") removes the check whether the kernel supports reporting the
> compression status before asserting on it. This breaks the test for no
> good reason on old CPUs (SNB and earlier) where the kernel can't report
> the compression status. Instead, we can check if the cpu doesn't
> support reporting and adopt the same behavior as if
I have a feeling I asked this before, but why aren't we just fixing
the kernel to report it correctly? For any platform with FBC2 it
should be trivial, for FBC1 slightly more complicate as you probably
have to check each individual tag.
> --no-fbc-compression-check was used.
>
> Changes since v1:
> - Move verification to setup_fbc (Paulo)
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100677
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
> ---
> tests/kms_frontbuffer_tracking.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c
> index b49f1abacae8..a655730b4ad3 100644
> --- a/tests/kms_frontbuffer_tracking.c
> +++ b/tests/kms_frontbuffer_tracking.c
> @@ -1524,6 +1524,7 @@ static bool fbc_supported_on_chipset(void)
> static void setup_fbc(void)
> {
> drmModeConnectorPtr c = get_connector(prim_mode_params.connector_id);
> + int devid = intel_get_drm_devid(drm.fd);
>
> if (!fbc_supported_on_chipset()) {
> igt_info("Can't test FBC: not supported on this chipset\n");
> @@ -1540,6 +1541,11 @@ static void setup_fbc(void)
> "pipe A\n");
> return;
> }
> +
> + /* Early Generations are not able to report compression status. */
> + if (!AT_LEAST_GEN(devid, 7))
> + opt.fbc_check_compression = false;
> +
> fbc.can_test = true;
>
> fbc_setup_last_action();
> --
> 2.11.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-26 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170420141144.14597-1-krisman@collabora.co.uk>
[not found] ` <20170420141144.14597-2-krisman@collabora.co.uk>
[not found] ` <1493164489.2504.112.camel@intel.com>
2017-04-26 17:57 ` [PATCH RESEND i-g-t 2/2] kms_frontbuffer_tracking: Don't poke compressing status for old cpus Gabriel Krisman Bertazi
2017-04-26 18:12 ` Ville Syrjälä [this message]
2017-04-26 18:36 ` Paulo Zanoni
2017-05-04 8:29 ` Petri Latvala
[not found] ` <1493163781.2504.107.camel@intel.com>
2017-04-26 18:40 ` [PATCH RESEND i-g-t 1/2] tests/kms_frontbuffer_tracking: Skip if CRTC not selected Gabriel Krisman Bertazi
2017-04-26 19:04 ` Zanoni, Paulo R
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=20170426181218.GH30290@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krisman@collabora.co.uk \
--cc=paulo.r.zanoni@intel.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