From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Vandita Kulkarni <vandita.kulkarni@intel.com>,
igt-dev@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, karthik.b.s@intel.com
Subject: Re: [PATCH i-g-t] tests/kms_async_flip: Reduce the clobbering area used for CRC test
Date: Thu, 8 Feb 2024 16:08:55 +0200 [thread overview]
Message-ID: <84ddef1c-d502-470d-8b05-2432416b8f9a@gmail.com> (raw)
In-Reply-To: <20240208121039.13701-1-vandita.kulkarni@intel.com>
Hi Vandita,
On 8.2.2024 14.10, Vandita Kulkarni wrote:
> On some platforms wc_mmap write takes longer to paint the fb,
> which we are using to clobber the already scanned buffer for
> CRC. Hence reducing the clobbered area.
>
> Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com>
> ---
> tests/kms_async_flips.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_async_flips.c b/tests/kms_async_flips.c
> index a0349fa03..2e5960943 100644
> --- a/tests/kms_async_flips.c
> +++ b/tests/kms_async_flips.c
> @@ -589,7 +589,7 @@ static void test_crc(data_t *data)
>
> while (clock_ms() - start < 2000) {
> /* fill the next fb with the expected color */
> - paint_fb(data, &data->bufs[frame], 1, height, 0xff0000ff);
> + paint_fb(data, &data->bufs[frame], 10, 10, 0xff0000ff);
Here really is needed to be painted full height of the framebuffer and
that width can be kept at 1 as any number higher will just increase the
work.
For async flip part of fb which will become visible is not known here so
the full height of the fb need to be painted on to catch if there was
something going wrong.
>
> data->flip_pending = true;
> ret = drmModePageFlip(data->drm_fd, data->crtc_id, data->bufs[frame].fb_id,
> @@ -600,7 +600,7 @@ static void test_crc(data_t *data)
>
> /* clobber the previous fb which should no longer be scanned out */
> frame = !frame;
> - paint_fb(data, &data->bufs[frame], 1, height, rand());
> + paint_fb(data, &data->bufs[frame], 10, 10, rand());
> }
>
> igt_pipe_crc_stop(data->pipe_crc);
next prev parent reply other threads:[~2024-02-08 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 12:10 [PATCH i-g-t] tests/kms_async_flip: Reduce the clobbering area used for CRC test Vandita Kulkarni
2024-02-08 14:08 ` Juha-Pekka Heikkila [this message]
2024-02-08 16:03 ` Kulkarni, Vandita
2024-02-08 17:12 ` Ville Syrjälä
2024-03-15 6:21 ` Kulkarni, Vandita
2024-02-08 16:08 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-02-08 17:03 ` ✓ CI.xeBAT: " Patchwork
2024-02-08 18:05 ` ✗ Fi.CI.IGT: failure " 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=84ddef1c-d502-470d-8b05-2432416b8f9a@gmail.com \
--to=juhapekka.heikkila@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=vandita.kulkarni@intel.com \
--cc=ville.syrjala@linux.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