Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Lofstedt, Marta" <marta.lofstedt@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] igt/kms_frontbuffer_tracking: Skip tests if FBC was disabled
Date: Tue, 06 Mar 2018 12:44:42 +0200	[thread overview]
Message-ID: <87fu5dscth.fsf@intel.com> (raw)
In-Reply-To: <CA5F6A4B62957246A95956419746064382B453BC@IRSMSX106.ger.corp.intel.com>

On Tue, 06 Mar 2018, "Lofstedt, Marta" <marta.lofstedt@intel.com> wrote:
>> -----Original Message-----
>> From: Chris Wilson [mailto:chris@chris-wilson.co.uk]
>> Sent: Tuesday, March 6, 2018 11:32 AM
>> To: Lofstedt, Marta <marta.lofstedt@intel.com>; igt-
>> dev@lists.freedesktop.org
>> Subject: Re: [igt-dev] [PATCH i-g-t] igt/kms_frontbuffer_tracking: Skip tests if
>> FBC was disabled
>> 
>> Quoting Marta Lofstedt (2018-03-06 09:24:57)
>> > If FBC has been disabled in the system due to previous malfuction, we
>> > would save time on CI if we bail out early.
>> >
>> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105359
>> > Signed-off-by: Marta Lofstedt <marta.lofstedt@intel.com>
>> 
>> Hmm, FBC starts inactive on a system, so we would need to ensure that we
>> enabled FBC and did a proper modeset first and wait for FBC to be enabled
>> first.
>
> On the SKL NUCi5 system I have been running this on, the FBC disabled
> sysfs, isn't re-set after a modeset. Maybe this is a driver error that
> should not be hidden by me suggesting to skip the tests.

That's what bugs me here. When should fbc be re-enabled after failure?
Who should be responsible for ensure it gets re-enabled in igt?

BR,
Jani.



>
> On the other hand, the kms_frontbuffer_tracking test should give
> different results if FBC is disabled compared to timeout in the
> fbc_wait_until_enabled() which up until some time ago was the most
> common way to fail this test.
>
>> 
>> Otherwise, it seems very reasonable that in this test we assume that FBC
>> works before we begin. We should have other tests that check that FBC
>> works under various different configurations, here we are checking that the
>> invalidate/flush do their jobs.
>> -Chris
>

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-03-06 10:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06  9:24 [igt-dev] [PATCH i-g-t] igt/kms_frontbuffer_tracking: Skip tests if FBC was disabled Marta Lofstedt
2018-03-06  9:32 ` Chris Wilson
2018-03-06 10:39   ` Lofstedt, Marta
2018-03-06 10:44     ` Jani Nikula [this message]
2018-03-06 10:45     ` Chris Wilson
2018-03-06 10:55       ` Jani Nikula
2018-03-06 11:03         ` Chris Wilson
2018-03-06 11:32           ` Lofstedt, Marta
2018-03-06 11:40             ` Chris Wilson
2018-03-06 10:27 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-03-06 13:34 ` [igt-dev] ✗ Fi.CI.IGT: warning " 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=87fu5dscth.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maarten.lankhorst@intel.com \
    --cc=marta.lofstedt@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