public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc/slpc: Disable rps_boost debugfs
Date: Mon, 15 May 2023 15:23:58 -0700	[thread overview]
Message-ID: <35ab4783-ab78-a245-7067-d7a3f35d0063@intel.com> (raw)
In-Reply-To: <87fs81dpz6.wl-ashutosh.dixit@intel.com>


On 5/12/2023 5:39 PM, Dixit, Ashutosh wrote:
> On Fri, 12 May 2023 16:56:03 -0700, Vinay Belgaumkar wrote:
> Hi Vinay,
>
>> rps_boost debugfs shows host turbo related info. This is not valid
>> when SLPC is enabled.
> A couple of thoughts about this. It appears people are know only about
> rps_boost_info and don't know about guc_slpc_info? So:
>
> a. Instead of hiding the rps_boost_info file do we need to print there
>     saying "SLPC is enabled, go look at guc_slpc_info"?
rps_boost_info has an eval() function which disables the interface when 
RPS is OFF. This is indeed the case here, so shouldn't we just follow 
that instead of trying to link the two?
>
> b. Or, even just call guc_slpc_info_show from rps_boost_show (so the two
>     files will show the same SLPC information)?

slpc_info has a lot of other info like the SLPC state, not sure that 
matches up with the rps_boost_info name.

Thanks,

Vinay.

>
> Ashutosh
>
>
>> guc_slpc_info already shows the number of boosts.  Add num_waiters there
>> as well and disable rps_boost when SLPC is enabled.
>>
>> Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/7632
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>

  reply	other threads:[~2023-05-15 22:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 23:56 [Intel-gfx] [PATCH] drm/i915/guc/slpc: Disable rps_boost debugfs Vinay Belgaumkar
2023-05-13  0:39 ` Dixit, Ashutosh
2023-05-15 22:23   ` Belgaumkar, Vinay [this message]
2023-05-15 22:58     ` Dixit, Ashutosh
2023-05-16  0:22       ` Dixit, Ashutosh
2023-05-13  0:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-05-13  0:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-13  3:57 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-05-16 15:49 [Intel-gfx] [PATCH] " Vinay Belgaumkar

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=35ab4783-ab78-a245-7067-d7a3f35d0063@intel.com \
    --to=vinay.belgaumkar@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox