From: Petri Latvala <petri.latvala@intel.com>
To: Marta Lofstedt <marta.lofstedt@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2] tests/kms_frontbuffer_tracking: increase FBC wait timeout to 5s
Date: Fri, 25 Aug 2017 13:46:00 +0300 [thread overview]
Message-ID: <db0150bf-b8cc-2db3-2d63-1c8d345bdab1@intel.com> (raw)
In-Reply-To: <20170825104029.18440-1-marta.lofstedt@intel.com>
On 08/25/2017 01:40 PM, Marta Lofstedt wrote:
> After investigating the timeout needed, the conclusion is that
> the longer timeout is only needed when the test swaps between
> some specific draw domains, typically blt vs. mmap_cpu.
> The objective of the FBC part of the tests is not to benchmark
> draw domain changes, it is to check that FBC was (re-)enabled.
Can this explanation be added to the code as a comment too?
--
Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-25 10:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 11:16 [PATCH i-g-t] tests/kms_frontbuffer_tracking: increase FBC wait timeout to 5s Marta Lofstedt
2017-08-04 9:47 ` Lofstedt, Marta
2017-08-04 18:56 ` Paulo Zanoni
2017-08-07 6:51 ` Lofstedt, Marta
2017-08-07 14:54 ` Paulo Zanoni
2017-08-08 11:14 ` Lofstedt, Marta
2017-08-11 10:16 ` Lofstedt, Marta
2017-08-25 10:40 ` [PATCH i-g-t v2] " Marta Lofstedt
2017-08-25 10:46 ` Petri Latvala [this message]
2017-08-25 10:47 ` Chris Wilson
2017-08-25 11:54 ` Lofstedt, Marta
2017-08-25 12:50 ` Lofstedt, Marta
2017-08-25 13:11 ` Chris Wilson
2017-08-25 13:33 ` Lofstedt, Marta
2017-08-29 7:16 ` Lofstedt, Marta
2017-09-01 19:12 ` Paulo Zanoni
2017-09-04 10:45 ` Chris Wilson
2017-09-04 18:26 ` Paulo Zanoni
2017-08-25 12:24 ` ✓ Fi.CI.BAT: success for tests/kms_frontbuffer_tracking: increase FBC wait timeout to 5s (rev2) Patchwork
2017-08-25 17:40 ` ✓ 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=db0150bf-b8cc-2db3-2d63-1c8d345bdab1@intel.com \
--to=petri.latvala@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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