All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] i915/gem_pipe_control_store_loop: added description for test case
Date: Wed, 27 Apr 2022 18:01:01 +0200	[thread overview]
Message-ID: <Ymlovfq1MJcp0VNX@kamilkon-DESK1> (raw)
In-Reply-To: <20220426052331.3453-2-sai.gowtham.ch@intel.com>

Hi Sai,

On 2022-04-26 at 10:53:30 +0530, sai.gowtham.ch@intel.com wrote:
> From: Ch Sai Gowtham <sai.gowtham.ch@intel.com>
> 
> Added test description for subtest that are available.
> 
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Signed-off-by: Ch Sai Gowtham <sai.gowtham.ch@intel.com>
---------------- ^
Correct this (see my other letter on gem_partial_pwrite_pread).

> ---
>  tests/i915/gem_pipe_control_store_loop.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/tests/i915/gem_pipe_control_store_loop.c b/tests/i915/gem_pipe_control_store_loop.c
> index 983605e3..070e767f 100644
> --- a/tests/i915/gem_pipe_control_store_loop.c
> +++ b/tests/i915/gem_pipe_control_store_loop.c
> @@ -183,9 +183,13 @@ igt_main
>  		igt_skip_on(devid == PCI_CHIP_I965_G); /* has totally broken pipe control */
>  	}
>  
> +	igt_describe("checks tlb consistency of the pipe_control target so creates new buffer"
--------------------- ^
Use capital letter at begin of sentence, so s/checks/Checks/

> +		     " each time, emit commands and send it to ring for execution and target"
> +		     " buffer won't get reused.");

Looks a little too long, you do not need to describe every
single step used, so imho shorten this to something like

	igt_describe("Checks tlb consistency of the pipe_control with fresh buffer.");

should be ok.

>  	igt_subtest("fresh-buffer")
>  		store_pipe_control_loop(false, 2);
>  
> +	igt_describe("Emit commands in reused buffer and send it to ring for execution.");

Here just reuse previous one with s/fresh/reused/ buffer change.

Regards,
Kamil

>  	igt_subtest("reused-buffer")
>  		store_pipe_control_loop(true, 2);
>  
> -- 
> 2.35.1
> 

  reply	other threads:[~2022-04-27 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  5:23 [igt-dev] [PATCH i-g-t 0/2] HAX add description to gem_pipe_control_store_loop sai.gowtham.ch
2022-04-26  5:23 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_pipe_control_store_loop: added description for test case sai.gowtham.ch
2022-04-27 16:01   ` Kamil Konieczny [this message]
2022-04-26  5:23 ` [igt-dev] [PATCH i-g-t 2/2] HAX: don't do full run sai.gowtham.ch
2022-04-26  5:36 ` [igt-dev] ✗ GitLab.Pipeline: warning for HAX add description to gem_pipe_control_store_loop Patchwork
2022-04-26  5:42 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2022-05-18 13:56 [igt-dev] [PATCH i-g-t 0/2] " sai.gowtham.ch
2022-05-18 13:56 ` [igt-dev] [PATCH i-g-t 1/2] i915/gem_pipe_control_store_loop: added description for test case sai.gowtham.ch
2022-05-19 12:04   ` Kamil Konieczny

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=Ymlovfq1MJcp0VNX@kamilkon-DESK1 \
    --to=kamil.konieczny@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sai.gowtham.ch@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.