public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Szwichtenberg, Radoslaw" <radoslaw.szwichtenberg@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Kamble, Sagar A" <sagar.a.kamble@intel.com>
Subject: Re: [PATCH i-g-t] tests/pm_rps: Move some test logic out of boost function
Date: Wed, 18 Oct 2017 11:03:13 +0000	[thread overview]
Message-ID: <1508324591.25374.8.camel@intel.com> (raw)
In-Reply-To: <114d5e78-49b2-8878-20eb-58ccbdd08062@intel.com>

On Wed, 2017-10-18 at 11:10 +0530, Sagar Arun Kamble wrote:
> 
> On 10/17/2017 6:13 PM, Radoslaw Szwichtenberg wrote:
> > Moving code out of the boost function will allow its usage
> > in other/new test scenarios.
> > 
> > Signed-off-by: Radoslaw Szwichtenberg <radoslaw.szwichtenberg@intel.com>
> > Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> > ---
> >   tests/pm_rps.c | 19 ++++++++++---------
> >   1 file changed, 10 insertions(+), 9 deletions(-)
> > 
> > diff --git a/tests/pm_rps.c b/tests/pm_rps.c
> > index 89f3e31c..dad87646 100644
> > --- a/tests/pm_rps.c
> > +++ b/tests/pm_rps.c
> > @@ -583,11 +583,6 @@ static void boost_freq(int fd, int *boost_freqs)
> >   	int64_t timeout = 1;
> >   	igt_spin_t *load;
> >   	unsigned int engine;
> > -	int fmid = (origfreqs[RPn] + origfreqs[RP0]) / 2;
> > -
> > -	fmid = get_hw_rounded_freq(fmid);
> > -	/* Set max freq to less then boost freq */
> > -	writeval(sysfs_files[MAX].filp, fmid);
> >   
> >   	/* Put boost on the same engine as low load */
> >   	engine = I915_EXEC_RENDER;
> > @@ -604,9 +599,6 @@ static void boost_freq(int fd, int *boost_freqs)
> >   	igt_spin_batch_end(load);
> >   	gem_sync(fd, load->handle);
> >   	igt_spin_batch_free(fd, load);
> > -
> > -	/* Set max freq to original softmax */
> > -	writeval(sysfs_files[MAX].filp, origfreqs[MAX]);
> >   }
> >   
> >   static void waitboost(int fd, bool reset)
> > @@ -615,6 +607,9 @@ static void waitboost(int fd, bool reset)
> >   	int boost_freqs[NUMFREQ];
> >   	int post_freqs[NUMFREQ];
> >   
> > +	int fmid = (origfreqs[RPn] + origfreqs[RP0]) / 2;
> > +	fmid = get_hw_rounded_freq(fmid);
> > +
> 
> How about function for getting mid? We can reuse in min_max_config too.
You think about something like:

static int get_fmid(void)
{
	int fmid = (origfreqs[RPn] + origfreqs[RP0]) / 2;
	return get_hw_rounded_freq(fmid);
}

Even though it wasn't scope of this change I think I can add it - do you think
it will be beneficial? We just use it two places so at this moment the benefit
will be minimal.
> >   	load_helper_run(LOW);
> >   
> >   	igt_debug("Apply low load...\n");
> > @@ -627,11 +622,17 @@ static void waitboost(int fd, bool reset)
> >   		sleep(1);
> >   	}
> >   
> > +	/* Set max freq to less than boost freq */
> > +	writeval(sysfs_files[MAX].filp, fmid);
> > +
> >   	/* When we wait upon the GPU, we want to temporarily boost it
> >   	 * to maximum.
> >   	 */
> >   	boost_freq(fd, boost_freqs);
> >   
> > +	/* Set max freq to original softmax */
> > +	writeval(sysfs_files[MAX].filp, origfreqs[MAX]);
> > +
> >   	igt_debug("Apply low load again...\n");
> >   	sleep(1);
> >   	stabilize_check(post_freqs);
> > @@ -643,7 +644,6 @@ static void waitboost(int fd, bool reset)
> >   	igt_assert_lt(pre_freqs[CUR], pre_freqs[MAX]);
> >   	igt_assert_eq(boost_freqs[CUR], boost_freqs[BOOST]);
> >   	igt_assert_lt(post_freqs[CUR], post_freqs[MAX]);
> > -
> >   }
> >   
> >   static void pm_rps_exit_handler(int sig)
> > @@ -656,6 +656,7 @@ static void pm_rps_exit_handler(int sig)
> >   		writeval(sysfs_files[MAX].filp, origfreqs[MAX]);
> >   	}
> >   
> > +	writeval(sysfs_files[BOOST].filp, origfreqs[BOOST]);
> 
> We are not changing boost_freq in current patch. Is this planned in new 
> testcase?
> Please defer this change until then.
Will remove!

Thanks for review!
Radek
> >   	load_helper_deinit();
> >   	close(drm_fd);
> >   }
> 
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-18 11:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 12:43 [PATCH i-g-t] tests/pm_rps: Move some test logic out of boost function Radoslaw Szwichtenberg
2017-10-17 13:54 ` [PATCH i-g-t] tests/pm_rps: Move some test logic out of boost functiony Katarzyna Dec
2017-10-17 14:16 ` ✓ Fi.CI.BAT: success for tests/pm_rps: Move some test logic out of boost function Patchwork
2017-10-18  0:55 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-18  5:40 ` [PATCH i-g-t] " Sagar Arun Kamble
2017-10-18 11:03   ` Szwichtenberg, Radoslaw [this message]
2017-10-18 13:43     ` Sagar Arun Kamble
2017-10-18 15:20 ` [PATCH i-g-t v2] " Radoslaw Szwichtenberg
2017-10-19  6:26   ` Sagar Arun Kamble
2017-10-18 15:57 ` ✓ Fi.CI.BAT: success for tests/pm_rps: Move some test logic out of boost function (rev2) Patchwork
2017-10-19  1:33 ` ✓ Fi.CI.IGT: " 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=1508324591.25374.8.camel@intel.com \
    --to=radoslaw.szwichtenberg@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sagar.a.kamble@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