From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] i915_pm_freq_api: Add some debug to tests
Date: Mon, 17 Jul 2023 11:26:37 -0700 [thread overview]
Message-ID: <e132d009-2532-e675-9887-2a161dfd8780@intel.com> (raw)
In-Reply-To: <87zg46gpqo.wl-ashutosh.dixit@intel.com>
On 7/8/2023 12:36 PM, Dixit, Ashutosh wrote:
> On Fri, 07 Jul 2023 16:23:59 -0700, Vinay Belgaumkar wrote:
>> Some subtests seem to be failing in CI, use igt_assert_(lt/eq) which
>> print the values being compared and some additional debug as well.
>>
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> ---
>> tests/i915/i915_pm_freq_api.c | 18 ++++++++----------
>> 1 file changed, 8 insertions(+), 10 deletions(-)
>>
>> diff --git a/tests/i915/i915_pm_freq_api.c b/tests/i915/i915_pm_freq_api.c
>> index 522abee35..cdb2e70ca 100644
>> --- a/tests/i915/i915_pm_freq_api.c
>> +++ b/tests/i915/i915_pm_freq_api.c
>> @@ -55,6 +55,7 @@ static void test_freq_basic_api(int dirfd, int gt)
>> rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ);
>> rp0 = get_freq(dirfd, RPS_RP0_FREQ_MHZ);
>> rpe = get_freq(dirfd, RPS_RP1_FREQ_MHZ);
>> + igt_debug("RPn: %d, RPe: %d, RP0: %d", rpn, rpe, rp0);
> Print gt here too.
ok.
>
>> /*
>> * Negative bound tests
>> @@ -90,21 +91,18 @@ static void test_reset(int i915, int dirfd, int gt, int count)
>> int fd;
>>
>> for (int i = 0; i < count; i++) {
>> - igt_assert_f(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0,
>> - "Failed after %d good cycles\n", i);
>> - igt_assert_f(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0,
>> - "Failed after %d good cycles\n", i);
>> + igt_debug("Running cycle: %d", i);
>> + igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0);
>> + igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0);
>> usleep(ACT_FREQ_LATENCY_US);
>> - igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn,
>> - "Failed after %d good cycles\n", i);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>>
>> /* Manually trigger a GT reset */
>> fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY);
>> igt_require(fd >= 0);
>> igt_ignore_warn(write(fd, "1\n", 2));
>>
>> - igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn,
>> - "Failed after %d good cycles\n", i);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
> Probably ok but why the changes in this loop?
There are a couple of bugs that are failing around this area.
Thanks,
Vinay.
>
>> }
>> close(fd);
>> }
>> @@ -116,13 +114,13 @@ static void test_suspend(int i915, int dirfd, int gt)
>> igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0);
>> igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0);
>> usleep(ACT_FREQ_LATENCY_US);
>> - igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>>
>> /* Manually trigger a suspend */
>> igt_system_suspend_autoresume(SUSPEND_STATE_S3,
>> SUSPEND_TEST_NONE);
>>
>> - igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>> }
>>
>> int i915 = -1;
>> --
>> 2.38.1
>>
WARNING: multiple messages have this Message-ID (diff)
From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t] i915_pm_freq_api: Add some debug to tests
Date: Mon, 17 Jul 2023 11:26:37 -0700 [thread overview]
Message-ID: <e132d009-2532-e675-9887-2a161dfd8780@intel.com> (raw)
In-Reply-To: <87zg46gpqo.wl-ashutosh.dixit@intel.com>
On 7/8/2023 12:36 PM, Dixit, Ashutosh wrote:
> On Fri, 07 Jul 2023 16:23:59 -0700, Vinay Belgaumkar wrote:
>> Some subtests seem to be failing in CI, use igt_assert_(lt/eq) which
>> print the values being compared and some additional debug as well.
>>
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> ---
>> tests/i915/i915_pm_freq_api.c | 18 ++++++++----------
>> 1 file changed, 8 insertions(+), 10 deletions(-)
>>
>> diff --git a/tests/i915/i915_pm_freq_api.c b/tests/i915/i915_pm_freq_api.c
>> index 522abee35..cdb2e70ca 100644
>> --- a/tests/i915/i915_pm_freq_api.c
>> +++ b/tests/i915/i915_pm_freq_api.c
>> @@ -55,6 +55,7 @@ static void test_freq_basic_api(int dirfd, int gt)
>> rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ);
>> rp0 = get_freq(dirfd, RPS_RP0_FREQ_MHZ);
>> rpe = get_freq(dirfd, RPS_RP1_FREQ_MHZ);
>> + igt_debug("RPn: %d, RPe: %d, RP0: %d", rpn, rpe, rp0);
> Print gt here too.
ok.
>
>> /*
>> * Negative bound tests
>> @@ -90,21 +91,18 @@ static void test_reset(int i915, int dirfd, int gt, int count)
>> int fd;
>>
>> for (int i = 0; i < count; i++) {
>> - igt_assert_f(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0,
>> - "Failed after %d good cycles\n", i);
>> - igt_assert_f(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0,
>> - "Failed after %d good cycles\n", i);
>> + igt_debug("Running cycle: %d", i);
>> + igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0);
>> + igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0);
>> usleep(ACT_FREQ_LATENCY_US);
>> - igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn,
>> - "Failed after %d good cycles\n", i);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>>
>> /* Manually trigger a GT reset */
>> fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY);
>> igt_require(fd >= 0);
>> igt_ignore_warn(write(fd, "1\n", 2));
>>
>> - igt_assert_f(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn,
>> - "Failed after %d good cycles\n", i);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
> Probably ok but why the changes in this loop?
There are a couple of bugs that are failing around this area.
Thanks,
Vinay.
>
>> }
>> close(fd);
>> }
>> @@ -116,13 +114,13 @@ static void test_suspend(int i915, int dirfd, int gt)
>> igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0);
>> igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0);
>> usleep(ACT_FREQ_LATENCY_US);
>> - igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>>
>> /* Manually trigger a suspend */
>> igt_system_suspend_autoresume(SUSPEND_STATE_S3,
>> SUSPEND_TEST_NONE);
>>
>> - igt_assert(get_freq(dirfd, RPS_CUR_FREQ_MHZ) == rpn);
>> + igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>> }
>>
>> int i915 = -1;
>> --
>> 2.38.1
>>
next prev parent reply other threads:[~2023-07-17 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 23:23 [igt-dev] [PATCH i-g-t] i915_pm_freq_api: Add some debug to tests Vinay Belgaumkar
2023-07-07 23:23 ` [Intel-gfx] " Vinay Belgaumkar
2023-07-08 0:24 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-07-08 0:34 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-07-08 19:36 ` [igt-dev] [Intel-gfx] [PATCH i-g-t] " Dixit, Ashutosh
2023-07-08 19:36 ` Dixit, Ashutosh
2023-07-17 18:26 ` Belgaumkar, Vinay [this message]
2023-07-17 18:26 ` Belgaumkar, Vinay
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=e132d009-2532-e675-9887-2a161dfd8780@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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.