From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/3] drm/i915/guc/slpc: Add waitboost functionality for SLPC
Date: Wed, 03 Nov 2021 17:23:35 -0700 [thread overview]
Message-ID: <87k0hodb08.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20211102012608.8609-3-vinay.belgaumkar@intel.com>
On Mon, 01 Nov 2021 18:26:07 -0700, Vinay Belgaumkar wrote:
>
> Add helper in RPS code for handling SLPC and non-SLPC paths.
> When boost is requested in the SLPC path, we can ask GuC to ramp
> up the frequency req by setting the minimum frequency to boost freq.
> Reset freq back to the min softlimit when there are no more waiters.
>
> v2: Schedule a worker thread which can boost freq from within
> an interrupt context as well.
>
> v3: No need to check against requested freq before scheduling boost
> work (Ashutosh)
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915/guc/slpc: Add waitboost functionality for SLPC
Date: Wed, 03 Nov 2021 17:23:35 -0700 [thread overview]
Message-ID: <87k0hodb08.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20211102012608.8609-3-vinay.belgaumkar@intel.com>
On Mon, 01 Nov 2021 18:26:07 -0700, Vinay Belgaumkar wrote:
>
> Add helper in RPS code for handling SLPC and non-SLPC paths.
> When boost is requested in the SLPC path, we can ask GuC to ramp
> up the frequency req by setting the minimum frequency to boost freq.
> Reset freq back to the min softlimit when there are no more waiters.
>
> v2: Schedule a worker thread which can boost freq from within
> an interrupt context as well.
>
> v3: No need to check against requested freq before scheduling boost
> work (Ashutosh)
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
next prev parent reply other threads:[~2021-11-04 0:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 1:26 [Intel-gfx] [PATCH v3 0/3] drm/i915/guc/slpc: Implement waitboost for SLPC Vinay Belgaumkar
2021-11-02 1:26 ` Vinay Belgaumkar
2021-11-02 1:26 ` [Intel-gfx] [PATCH 1/3] drm/i915/guc/slpc: Define and initialize boost frequency Vinay Belgaumkar
2021-11-02 1:26 ` Vinay Belgaumkar
2021-11-04 0:23 ` [Intel-gfx] " Dixit, Ashutosh
2021-11-04 0:23 ` Dixit, Ashutosh
2021-11-02 1:26 ` [Intel-gfx] [PATCH 2/3] drm/i915/guc/slpc: Add waitboost functionality for SLPC Vinay Belgaumkar
2021-11-02 1:26 ` Vinay Belgaumkar
2021-11-04 0:23 ` Dixit, Ashutosh [this message]
2021-11-04 0:23 ` Dixit, Ashutosh
2021-11-02 1:26 ` [Intel-gfx] [PATCH 3/3] drm/i915/guc/slpc: Update boost sysfs hooks " Vinay Belgaumkar
2021-11-02 1:26 ` Vinay Belgaumkar
2021-11-04 0:41 ` [Intel-gfx] " Dixit, Ashutosh
2021-11-04 0:41 ` Dixit, Ashutosh
2021-11-02 1:35 ` [Intel-gfx] [PATCH v3 0/3] drm/i915/guc/slpc: Implement waitboost " Dixit, Ashutosh
2021-11-02 1:35 ` Dixit, Ashutosh
2021-11-02 1:38 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc/slpc: Implement waitboost for SLPC (rev3) Patchwork
2021-11-02 2:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-02 3:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-11-01 4:39 [Intel-gfx] [PATCH v2 0/3] drm/i915/guc/slpc: Implement waitboost for SLPC Vinay Belgaumkar
2021-11-01 4:39 ` [Intel-gfx] [PATCH 2/3] drm/i915/guc/slpc: Add waitboost functionality " Vinay Belgaumkar
2021-11-01 20:28 ` Dixit, Ashutosh
2021-11-02 0:19 ` Belgaumkar, Vinay
2021-10-20 19:52 [Intel-gfx] [PATCH 0/3] drm/i915/guc/slpc: Implement waitboost " Vinay Belgaumkar
2021-10-20 19:52 ` [Intel-gfx] [PATCH 2/3] drm/i915/guc/slpc: Add waitboost functionality " 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=87k0hodb08.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinay.belgaumkar@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 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.