All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Nilawar, Badal" <badal.nilawar@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/xe: Verify actual frequency on the basis of GT state
Date: Mon, 17 Jul 2023 21:42:14 -0700	[thread overview]
Message-ID: <87lefdj0ex.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <aa1e803f-f24b-21ff-405e-a1259298daa8@intel.com>

On Mon, 17 Jul 2023 21:27:02 -0700, Nilawar, Badal wrote:
>
> >> @@ -226,6 +226,9 @@ static void test_freq_fixed(int fd, int gt_id)
> >>
> >>	igt_debug("Starting testing fixed request\n");
> >>
> >> +	if (gt_idle)
> >> +		igt_require(igt_wait(xe_is_gt_in_c6(fd, gt_id), 1000, 1));
> >> +
> >>	/*
> >>	 * For Fixed freq we need to set both min and max to the desired value
> >>	 * Then we check if hardware is actually operating at the desired freq
> >> @@ -235,13 +238,25 @@ static void test_freq_fixed(int fd, int gt_id)
> >>	igt_assert(set_freq(fd, gt_id, "max", rpn) > 0);
> >>	usleep(ACT_FREQ_LATENCY_US);
> >>	igt_assert(get_freq(fd, gt_id, "cur") == rpn);
> >> -	igt_assert(get_freq(fd, gt_id, "act") == rpn);
> >> +
> >> +	if (gt_idle) {
> >> +		usleep(ACT_FREQ_LATENCY_US);
> >
> > Looks like this usleep should in the else? Since we've already igt_wait'ed
> > above for the idle case? In all places in this patch.
>
> As get_freq(fd, gt_id, "cur") will forcewake the gt so added usleep to gt
> to settle down.

Ah good point. I missed that reading requested freq takes forcewake (unlike
act freq).

> Else case is covering exec case so it is expected that act
> freq is already reached to set freq with the delay added after set_freq.

Missed this too, so this is ok too.

> >
> >> +		igt_assert(get_freq(fd, gt_id, "act") == 0);
> >> +	} else {
> >> +		igt_assert(get_freq(fd, gt_id, "act") == rpn);
> >> +	}
> >>
> >>	igt_assert(set_freq(fd, gt_id, "min", rpe) > 0);
> >>	igt_assert(set_freq(fd, gt_id, "max", rpe) > 0);
> >>	usleep(ACT_FREQ_LATENCY_US);
> >>	igt_assert(get_freq(fd, gt_id, "cur") == rpe);
> >> -	igt_assert(get_freq(fd, gt_id, "act") == rpe);
> >> +
> >> +	if (gt_idle) {
> >> +		usleep(ACT_FREQ_LATENCY_US);
> >> +		igt_assert(get_freq(fd, gt_id, "act") == 0);
> >> +	} else {
> >> +		igt_assert(get_freq(fd, gt_id, "act") == rpe);
> >> +	}
> >>
> >>	igt_assert(set_freq(fd, gt_id, "min", rp0) > 0);
> >>	igt_assert(set_freq(fd, gt_id, "max", rp0) > 0);
> >
> > We can't check for 0 act freq in this rp0 case?
> Yes we can check. I will add this check.
> >
> >> diff --git a/tests/xe/xe_pm_residency.c b/tests/xe/xe_pm_residency.c
> >> index a20c4449c..5c4516d03 100644
> >> --- a/tests/xe/xe_pm_residency.c
> >> +++ b/tests/xe/xe_pm_residency.c
> >> @@ -28,6 +28,16 @@ const double tolerance = 0.1;
> >>		     (tol) * 100.0, (tol) * 100.0, \
> >>		     (double)(ref))
> >>
> >> +/**
> >> + * SUBTEST: gt-c6-on-idle
> >> + * Description: Validate GT C6 state on idle
> >> + * Run type: BAT
> >> + *
> >> + * SUBTEST: idle-residency
> >> + * Description: basic residency test to validate idle residency
> >> + *		measured over a time interval is within the tolerance
> >> + * Run type: FULL
> >> + */
> >
> > Why combine these two doc sections? idle-residency description should be
> > above test_idle_residency?
> Since gt-c6-on-idle moved to lib I moved its doc here. To maintain
> uniformity I combined all the docs. tests/xe/xe_ccs.c is following this
> practice.

OK, this is fine too.

Thanks.
--
Ashutosh


> >
> >>   IGT_TEST_DESCRIPTION("Tests for gtidle properties");
> >>
> >>   static unsigned int measured_usleep(unsigned int usec)
> >> @@ -45,24 +55,6 @@ static unsigned int measured_usleep(unsigned int usec)
> >>	return igt_nsec_elapsed(&ts) / 1000;
> >>   }
> >>
> >> -/**
> >> - * SUBTEST: gt-c6-on-idle
> >> - * Description: Validate GT C6 state on idle
> >> - * Run type: BAT
> >> - */
> >> -static bool is_gt_in_c6(int fd, int gt)
> >> -{
> >> -	char gt_c_state[16];
> >> -	int gt_fd;
> >> -
> >> -	gt_fd = xe_sysfs_gt_open(fd, gt);
> >> -	igt_assert(gt_fd >= 0);
> >> -	igt_assert(igt_sysfs_scanf(gt_fd, "gtidle/idle_status", "%s", gt_c_state) == 1);
> >> -	close(gt_fd);
> >> -
> >> -	return strcmp(gt_c_state, "gt-c6") == 0;
> >> -}
> >> -
> >>   static unsigned long read_idle_residency(int fd, int gt)
> >>   {
> >>	unsigned long residency = 0;
> >> @@ -76,17 +68,11 @@ static unsigned long read_idle_residency(int fd, int gt)
> >>	return residency;
> >>   }
> >>
> >> -/**
> >> - * SUBTEST: idle-residency
> >> - * Description: basic residency test to validate idle residency
> >> - *		measured over a time interval is within the tolerance
> >> - * Run type: FULL
> >> - */
> >>   static void test_idle_residency(int fd, int gt)
> >>   {
> >>	unsigned long elapsed_ms, residency_start, residency_end;
> >>
> >> -	igt_assert_f(igt_wait(is_gt_in_c6(fd, gt), 1000, 1), "GT not in C6\n");
> >> +	igt_assert_f(igt_wait(xe_is_gt_in_c6(fd, gt), 1000, 1), "GT not in C6\n");
> >>
> >>	residency_start = read_idle_residency(fd, gt);
> >>	elapsed_ms = measured_usleep(SLEEP_DURATION * 1000) / 1000;
> >> @@ -110,7 +96,7 @@ igt_main
> >>	igt_describe("Validate GT C6 on idle");
> >>	igt_subtest("gt-c6-on-idle")
> >>		xe_for_each_gt(fd, gt)
> >> -			igt_assert_f(igt_wait(is_gt_in_c6(fd, gt), 1000, 1), "GT not in C6\n");
> >> +			igt_assert_f(igt_wait(xe_is_gt_in_c6(fd, gt), 1000, 1), "GT not in C6\n");
> >>
> >>	igt_describe("Validate idle residency measured over a time interval is within the tolerance");
> >>	igt_subtest("idle-residency")
> >> --
> >> 2.25.1
> >
> > Thanks.
> > --
> > Ashutosh

  reply	other threads:[~2023-07-18  4:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 10:57 [igt-dev] [PATCH i-g-t v2] tests/xe: Verify actual frequency on the basis of GT state Badal Nilawar
2023-07-17 12:42 ` [igt-dev] ○ CI.xeBAT: info for " Patchwork
2023-07-17 12:50 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-07-17 16:21 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-07-18  2:32 ` [igt-dev] [PATCH i-g-t v2] " Dixit, Ashutosh
2023-07-18  4:27   ` Nilawar, Badal
2023-07-18  4:42     ` Dixit, Ashutosh [this message]
2023-07-18  4:51       ` Dixit, Ashutosh
2023-07-18  8:51         ` Nilawar, Badal

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=87lefdj0ex.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=igt-dev@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.