Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Melissa Wen <melissa.srw@gmail.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org, twoerner@gmail.com,
	kernel-usp@googlegroups.com
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 1/2] test/kms_cursor_crc: release old pipe_crc before create a new one
Date: Thu, 16 Jul 2020 08:40:38 -0300	[thread overview]
Message-ID: <20200716114038.bfieynyqbsc2fsa3@smtp.gmail.com> (raw)
In-Reply-To: <20200715124706.f6bvf7g7dqbcnyaj@ahiler-desk1.fi.intel.com>

On 07/15, Arkadiusz Hiler wrote:
> On Mon, Jun 22, 2020 at 01:37:55PM -0300, Melissa Wen wrote:
> > When a subtest fails, it skips the cleanup, and its pipe_crc remains allocated.
> > As a consequence, the following subtest also fails (timeout) when trying to
> > create a new one. This patch releases any remaining pipe_crc to enable the
> > creation of a new one for the next subtest.
> > 
> > Signed-off-by: Melissa Wen <melissa.srw@gmail.com>
> > ---
> >  tests/kms_cursor_crc.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/tests/kms_cursor_crc.c b/tests/kms_cursor_crc.c
> > index f105e295..5976df5f 100644
> > --- a/tests/kms_cursor_crc.c
> > +++ b/tests/kms_cursor_crc.c
> > @@ -423,6 +423,8 @@ static void prepare_crtc(data_t *data, igt_output_t *output,
> >  	igt_display_commit(display);
> >  
> >  	/* create the pipe_crc object for this pipe */
> > +	if (data->pipe_crc)
> > +		igt_pipe_crc_free(data->pipe_crc);
> 
> That's a welcome improvement, but you may want to also look at
> 06333955bf3d ("tests/kms_cursor_crc: start crc only once per test")
> for some extra inspiration for future work on this.
> 
> It should be possible to initiate pipe crc to be initalized only once
> per each tested pipe in run_tests_on_pipe() - igt_pipe_crc_new() can be
> costly on some real panels.

Hi,

Thanks for the advice! 
As I have one more refactoring in mind for this test, I will add this in
the works and send a patchset with everything together.

For now, I just submitted a v2 of this patch because I dropped the other
one that was in the same patchset.

Melissa
> 
> Anyway,
> Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> 
> 
> >  	data->pipe_crc = igt_pipe_crc_new(data->drm_fd, data->pipe,
> >  					  INTEL_PIPE_CRC_SOURCE_AUTO);
> >  
> > -- 
> > 2.27.0
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2020-07-16 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 10:34 [igt-dev] [PATCH i-g-t 0/2] test/kms_cursor_crc: tie some loose ends in prepare_crtc Melissa Wen
2020-06-25 10:35 ` [igt-dev] [PATCH i-g-t 1/2] test/kms_cursor_crc: release old pipe_crc before create a new one Melissa Wen
     [not found]   ` <20200715124706.f6bvf7g7dqbcnyaj@ahiler-desk1.fi.intel.com>
2020-07-16 11:40     ` Melissa Wen [this message]
2020-06-25 10:36 ` [igt-dev] [PATCH i-g-t 2/2] test/kms_cursor_crc: align the start of the CRC capture to a vblank Melissa Wen
2020-06-25 15:14 ` [igt-dev] ✓ Fi.CI.BAT: success for test/kms_cursor_crc: tie some loose ends in prepare_crtc Patchwork
2020-06-25 16:11 ` [igt-dev] ✗ 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=20200716114038.bfieynyqbsc2fsa3@smtp.gmail.com \
    --to=melissa.srw@gmail.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kernel-usp@googlegroups.com \
    --cc=twoerner@gmail.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