From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: don.hiatt@intel.com, intel-gfx@lists.freedesktop.org
Cc: "S . Zharkoff" <s.zharkoff@gmail.com>,
KiteStramuort <kitestramuort@autistici.org>,
Tomas Janousek <tomi@nomi.cz>
Subject: Re: [PATCH] drm/i915/guc: Skip suspend/resume GuC action on platforms w/o GuC submission
Date: Fri, 15 Nov 2019 14:02:01 -0800 [thread overview]
Message-ID: <7355e3c9-71ad-bcc2-f069-4e9be308aed4@intel.com> (raw)
In-Reply-To: <20191115182051.27182-1-don.hiatt@intel.com>
On 11/15/19 10:20 AM, don.hiatt@intel.com wrote:
> From: Don Hiatt <don.hiatt@intel.com>
>
> On some platforms (e.g. KBL) that do not support GuC submission, but
> the user enabled the GuC communication (e.g for HuC authentication)
> calling the GuC EXIT_S_STATE action results in lose of ability to
> enter RC6. We can remove the GuC suspend/resume entirely as we do
> not need to save the GuC submission status.
>
> Add intel_guc_submission_is_enabled() function to determine if
> GuC submission is active.
>
> v2: Do not suspend/resume the GuC on platforms that do not support
> Guc Submission.
> v3: Fix typo, move suspend logic to remove goto.
> v4: Use intel_guc_submission_is_enabled() to check GuC submission
> status.
> v5: No need to look at engine to determine if submission is enabled.
> Squash fix + intel_guc_submission_is_enabled() patch into one.
>
> Reported-by: KiteStramuort <kitestramuort@autistici.org>
> Reported-by: S. Zharkoff <s.zharkoff@gmail.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111594
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111623
> Fixes: f774f0964919 ("drm/i915/guc: Turn on GuC/HuC auto mode")
I don't think this Fixes tag is appropriate since we already reverted
that patch.
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceralo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Stuart Summers <stuart.summers@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Tested-by: Tomas Janousek <tomi@nomi.cz>
> Signed-off-by: Don Hiatt <don.hiatt@intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc.c | 7 +++++++
> drivers/gpu/drm/i915/gt/uc/intel_uc.c | 8 ++++++++
> drivers/gpu/drm/i915/i915_drv.h | 6 ++++++
> 3 files changed, 21 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc.c b/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> index 019ae6486e8d..92d9305c0d73 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> @@ -553,6 +553,13 @@ int intel_guc_suspend(struct intel_guc *guc)
> GUC_POWER_D1, /* any value greater than GUC_POWER_D0 */
> };
>
> + /*
> + * If GuC communication is enabled but submission is not supported,
> + * we do not need to suspend the GuC.
> + */
> + if (!intel_guc_submission_is_enabled(guc))
> + return 0;
> +
> /*
> * The ENTER_S_STATE action queues the save/restore operation in GuC FW
> * and then returns, so waiting on the H2G is not enough to guarantee
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc.c b/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> index 629b19377a29..4dd43b99a334 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> @@ -605,6 +605,14 @@ static int __uc_resume(struct intel_uc *uc, bool enable_communication)
> if (enable_communication)
> guc_enable_communication(guc);
>
> + /*
> + * If GuC communication is enabled but submission is not supported,
> + * we do not need to resume the GuC but we do need to enable the
> + * GuC communication on resume (above).
> + */
> + if (!intel_guc_submission_is_enabled(guc))
> + return 0;
> +
I would put this check inside intel_guc_resume(), for symmetry with the
one you put inside intel_guc_suspend().
Daniele
> err = intel_guc_resume(guc);
> if (err) {
> DRM_DEBUG_DRIVER("Failed to resume GuC, err=%d", err);
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 7bc1d8c102b2..2b879472e760 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -2044,4 +2044,10 @@ i915_coherent_map_type(struct drm_i915_private *i915)
> return HAS_LLC(i915) ? I915_MAP_WB : I915_MAP_WC;
> }
>
> +static inline bool intel_guc_submission_is_enabled(struct intel_guc *guc)
> +{
> + return intel_guc_is_submission_supported(guc) &&
> + intel_guc_is_running(guc);
> +}
> +
> #endif
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: don.hiatt@intel.com, intel-gfx@lists.freedesktop.org
Cc: "S . Zharkoff" <s.zharkoff@gmail.com>,
KiteStramuort <kitestramuort@autistici.org>,
Tomas Janousek <tomi@nomi.cz>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Skip suspend/resume GuC action on platforms w/o GuC submission
Date: Fri, 15 Nov 2019 14:02:01 -0800 [thread overview]
Message-ID: <7355e3c9-71ad-bcc2-f069-4e9be308aed4@intel.com> (raw)
Message-ID: <20191115220201.8VJxzpMwIFlC0SU3xC6wAJA9CZO723I70kNBEVer2co@z> (raw)
In-Reply-To: <20191115182051.27182-1-don.hiatt@intel.com>
On 11/15/19 10:20 AM, don.hiatt@intel.com wrote:
> From: Don Hiatt <don.hiatt@intel.com>
>
> On some platforms (e.g. KBL) that do not support GuC submission, but
> the user enabled the GuC communication (e.g for HuC authentication)
> calling the GuC EXIT_S_STATE action results in lose of ability to
> enter RC6. We can remove the GuC suspend/resume entirely as we do
> not need to save the GuC submission status.
>
> Add intel_guc_submission_is_enabled() function to determine if
> GuC submission is active.
>
> v2: Do not suspend/resume the GuC on platforms that do not support
> Guc Submission.
> v3: Fix typo, move suspend logic to remove goto.
> v4: Use intel_guc_submission_is_enabled() to check GuC submission
> status.
> v5: No need to look at engine to determine if submission is enabled.
> Squash fix + intel_guc_submission_is_enabled() patch into one.
>
> Reported-by: KiteStramuort <kitestramuort@autistici.org>
> Reported-by: S. Zharkoff <s.zharkoff@gmail.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111594
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111623
> Fixes: f774f0964919 ("drm/i915/guc: Turn on GuC/HuC auto mode")
I don't think this Fixes tag is appropriate since we already reverted
that patch.
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceralo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Stuart Summers <stuart.summers@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Tested-by: Tomas Janousek <tomi@nomi.cz>
> Signed-off-by: Don Hiatt <don.hiatt@intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc.c | 7 +++++++
> drivers/gpu/drm/i915/gt/uc/intel_uc.c | 8 ++++++++
> drivers/gpu/drm/i915/i915_drv.h | 6 ++++++
> 3 files changed, 21 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc.c b/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> index 019ae6486e8d..92d9305c0d73 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc.c
> @@ -553,6 +553,13 @@ int intel_guc_suspend(struct intel_guc *guc)
> GUC_POWER_D1, /* any value greater than GUC_POWER_D0 */
> };
>
> + /*
> + * If GuC communication is enabled but submission is not supported,
> + * we do not need to suspend the GuC.
> + */
> + if (!intel_guc_submission_is_enabled(guc))
> + return 0;
> +
> /*
> * The ENTER_S_STATE action queues the save/restore operation in GuC FW
> * and then returns, so waiting on the H2G is not enough to guarantee
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc.c b/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> index 629b19377a29..4dd43b99a334 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc.c
> @@ -605,6 +605,14 @@ static int __uc_resume(struct intel_uc *uc, bool enable_communication)
> if (enable_communication)
> guc_enable_communication(guc);
>
> + /*
> + * If GuC communication is enabled but submission is not supported,
> + * we do not need to resume the GuC but we do need to enable the
> + * GuC communication on resume (above).
> + */
> + if (!intel_guc_submission_is_enabled(guc))
> + return 0;
> +
I would put this check inside intel_guc_resume(), for symmetry with the
one you put inside intel_guc_suspend().
Daniele
> err = intel_guc_resume(guc);
> if (err) {
> DRM_DEBUG_DRIVER("Failed to resume GuC, err=%d", err);
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 7bc1d8c102b2..2b879472e760 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -2044,4 +2044,10 @@ i915_coherent_map_type(struct drm_i915_private *i915)
> return HAS_LLC(i915) ? I915_MAP_WB : I915_MAP_WC;
> }
>
> +static inline bool intel_guc_submission_is_enabled(struct intel_guc *guc)
> +{
> + return intel_guc_is_submission_supported(guc) &&
> + intel_guc_is_running(guc);
> +}
> +
> #endif
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-15 22:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 18:20 [PATCH] drm/i915/guc: Skip suspend/resume GuC action on platforms w/o GuC submission don.hiatt
2019-11-15 18:20 ` [Intel-gfx] " don.hiatt
2019-11-15 22:02 ` Daniele Ceraolo Spurio [this message]
2019-11-15 22:02 ` Daniele Ceraolo Spurio
2019-11-15 22:22 ` Hiatt, Don
2019-11-15 22:22 ` [Intel-gfx] " Hiatt, Don
2019-11-15 23:10 ` Daniele Ceraolo Spurio
2019-11-15 23:10 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-15 23:15 ` Hiatt, Don
2019-11-15 23:15 ` [Intel-gfx] " Hiatt, Don
2019-11-15 22:04 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Skip suspend/resume GuC action on platforms w/o GuC submission (rev4) Patchwork
2019-11-15 22:04 ` [Intel-gfx] " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-11-15 23:15 [PATCH] drm/i915/guc: Skip suspend/resume GuC action on platforms w/o GuC submission don.hiatt
2019-11-16 10:04 ` Chris Wilson
2019-10-30 21:22 don.hiatt
2019-10-28 21:25 don.hiatt
2019-10-29 12:33 ` Michal Wajdeczko
2019-10-29 21:15 ` Hiatt, Don
2019-10-30 7:25 ` Tomas Janousek
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=7355e3c9-71ad-bcc2-f069-4e9be308aed4@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=don.hiatt@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kitestramuort@autistici.org \
--cc=s.zharkoff@gmail.com \
--cc=tomi@nomi.cz \
/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