Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Poosa, Karthik" <karthik.poosa@intel.com>
To: Riana Tauro <riana.tauro@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_pm_residency: Print execution and sleep times
Date: Thu, 19 Sep 2024 13:44:25 +0530	[thread overview]
Message-ID: <b1011235-0cb1-4531-956b-5ae3cb2e4c2e@intel.com> (raw)
In-Reply-To: <6374b703-48ee-45eb-9529-f2bf04622ff8@intel.com>

That is debug patch, we dont need it here.

On 19-09-2024 12:37, Riana Tauro wrote:
> Hi Karthik
>
> you had sent a patch with assert prior to this. Don't we need
> that?
>
> Thanks,
> Riana
>
> On 9/19/2024 12:03 PM, Karthik Poosa wrote:
>> Print the workload execution and sleep times of the test to help 
>> diagnose
>> timeouts.
>> This will show how long the workload ran and how long the test slept.
>>
>> Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
>> ---
>>   tests/intel/xe_pm_residency.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/intel/xe_pm_residency.c 
>> b/tests/intel/xe_pm_residency.c
>> index 0e687558b..3c3b33ab1 100644
>> --- a/tests/intel/xe_pm_residency.c
>> +++ b/tests/intel/xe_pm_residency.c
>> @@ -139,7 +139,7 @@ static void exec_load(int fd, struct 
>> drm_xe_engine_class_instance *hwe, unsigned
>>           elapsed = igt_nsec_elapsed(&tv);
>>           igt_assert_eq(data->data, done[1]);
>>   -        igt_debug("Execution took %.3fms (submit %.1fus, wait 
>> %.1fus)\n",
>> +        igt_info("Execution took %.3fms (submit %.1fus, wait 
>> %.1fus)\n",
>>                 1e-6 * elapsed,
>>                 1e-3 * submit,
>>                 1e-3 * (elapsed - submit));
>> @@ -150,6 +150,8 @@ static void exec_load(int fd, struct 
>> drm_xe_engine_class_instance *hwe, unsigned
>>            * Execute the above workload for ~1% of the elapsed time 
>> and sleep for
>>            * the rest of the time (~99%)
>>            */
>> +        igt_info("Sleeping for %ld ms\n", ((elapsed / 10)/1000));
>> +
>>           usleep(elapsed / 10);
>>       } while (!READ_ONCE(*done));

  reply	other threads:[~2024-09-19  8:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  6:33 [PATCH i-g-t] tests/intel/xe_pm_residency: Print execution and sleep times Karthik Poosa
2024-09-19  6:54 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-09-19  7:07 ` [PATCH i-g-t] " Riana Tauro
2024-09-19  8:14   ` Poosa, Karthik [this message]
2024-09-19  8:35     ` Riana Tauro
2024-09-19  7:22 ` ✗ CI.xeBAT: failure for " Patchwork
2024-09-19  7:26 ` [PATCH i-g-t] " Gupta, Anshuman
2024-09-19  8:40   ` Poosa, Karthik
2024-09-19 16:58 ` ✗ CI.xeFULL: failure for " Patchwork
2024-09-20  0:01 ` ✓ CI.xeBAT: success for tests/intel/xe_pm_residency: Print execution and sleep times (rev2) Patchwork
2024-09-20  0:10 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-09-20  2:41 ` ✗ CI.xeFULL: " Patchwork
2024-09-20  4:46 ` ✓ Fi.CI.IGT: success for tests/intel/xe_pm_residency: Print execution and sleep times 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=b1011235-0cb1-4531-956b-5ae3cb2e4c2e@intel.com \
    --to=karthik.poosa@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=riana.tauro@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