All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Kulkarni, Vandita" <vandita.kulkarni@intel.com>
Cc: "juhapekka.heikkila@gmail.com" <juhapekka.heikkila@gmail.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"B S, Karthik" <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 19:12:49 +0200	[thread overview]
Message-ID: <ZcULkcsD6d4LgRn8@intel.com> (raw)
In-Reply-To: <SJ0PR11MB67899FCB90CF101777DDA1C98D442@SJ0PR11MB6789.namprd11.prod.outlook.com>

On Thu, Feb 08, 2024 at 04:03:49PM +0000, Kulkarni, Vandita wrote:
> > -----Original Message-----
> > From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> > Sent: Thursday, February 8, 2024 7:39 PM
> > To: Kulkarni, Vandita <vandita.kulkarni@intel.com>; igt-
> > dev@lists.freedesktop.org
> > Cc: ville.syrjala@linux.intel.com; B S, Karthik <karthik.b.s@intel.com>
> > Subject: Re: [PATCH i-g-t] tests/kms_async_flip: Reduce the clobbering area
> > used for CRC test
> > 
> > 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.
> Thanks JP for the feedback, you are right, for async flip we might not know if
> the previous fb is still being scanned until we check the last line.
> This might not be the solution then.
> 
> Other option(on non fixed panels) where we can optimize is by selecting the
> smallest mode, where as  now mode[0] is being picked.

I already did that once, but it broke something, and was reverted.
See commit 79483e9ae4fe ("Revert "tests/kms_async_flips: Make the crc test faster"")

Hmm. Looking at that revert maybe the problem was that I just used that
hardcoded 1024x768 mode, which perhaps didn't work due to i915 still
missing the PLL algorithm for the newer platforms. Picking a smallish
mode from the connector's mode list might work better.

> Incase we pick the smallest mode we might have to write a new case to test
> async flips with bigjoiner.
> Also it is really not clear on which platforms and drivers, how much time it would take to
> paint 1xh fb. I will try to check further on this.
> 
> Thanks,
> Vandita
> > 
> > >
> > >   		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);
> 

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-02-08 17:13 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
2024-02-08 16:03   ` Kulkarni, Vandita
2024-02-08 17:12     ` Ville Syrjälä [this message]
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=ZcULkcsD6d4LgRn8@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.com \
    --cc=karthik.b.s@intel.com \
    --cc=vandita.kulkarni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.