From: Michel Thierry <michel.thierry@intel.com>
To: "Piotr Piórkowski" <piotr.piorkowski@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/guc: Remove GUC_CTL_DEVICE_INFO parameter
Date: Mon, 5 Mar 2018 10:12:23 -0800 [thread overview]
Message-ID: <68658b4f-b08c-36dd-0bd6-41afde2acec3@intel.com> (raw)
In-Reply-To: <20180305131311.359-1-piotr.piorkowski@intel.com>
On 3/5/2018 5:13 AM, Piotr Piórkowski wrote:
> It looks that GuC does not actively use GUC_CTL_DEVICE_INFO parameter
> where we are passing GT type and Core family values.
> Lets stop setup this parameter and remove related definitions.
>
> v2: (this time without squashed HAX)
> - New title and description
> - Remove also GUC_CORE_FAMILY_* definitions (Michel)
>
> Signed-off-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: John A Spotswood <john.a.spotswood@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michel Thierry <michel.thierry@intel.com>
> ---
> drivers/gpu/drm/i915/intel_guc.c | 24 ------------------------
> drivers/gpu/drm/i915/intel_guc_fwif.h | 7 -------
> 2 files changed, 31 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc.c b/drivers/gpu/drm/i915/intel_guc.c
> index ff08ea0ebf49..efc413137a89 100644
> --- a/drivers/gpu/drm/i915/intel_guc.c
> +++ b/drivers/gpu/drm/i915/intel_guc.c
> @@ -200,26 +200,6 @@ void intel_guc_fini(struct intel_guc *guc)
> guc_shared_data_destroy(guc);
> }
>
> -static u32 get_gt_type(struct drm_i915_private *dev_priv)
> -{
> - /* XXX: GT type based on PCI device ID? field seems unused by fw */
> - return 0;
> -}
> -
> -static u32 get_core_family(struct drm_i915_private *dev_priv)
> -{
> - u32 gen = INTEL_GEN(dev_priv);
> -
> - switch (gen) {
> - case 9:
> - return GUC_CORE_FAMILY_GEN9;
> -
> - default:
> - MISSING_CASE(gen);
> - return GUC_CORE_FAMILY_UNKNOWN;
> - }
> -}
> -
> static u32 get_log_verbosity_flags(void)
> {
> if (i915_modparams.guc_log_level > 0) {
> @@ -246,10 +226,6 @@ void intel_guc_init_params(struct intel_guc *guc)
>
> memset(params, 0, sizeof(params));
>
> - params[GUC_CTL_DEVICE_INFO] |=
> - (get_gt_type(dev_priv) << GUC_CTL_GT_TYPE_SHIFT) |
> - (get_core_family(dev_priv) << GUC_CTL_CORE_FAMILY_SHIFT);
> -
> /*
> * GuC ARAT increment is 10 ns. GuC default scheduler quantum is one
> * second. This ARAR is calculated by:
> diff --git a/drivers/gpu/drm/i915/intel_guc_fwif.h b/drivers/gpu/drm/i915/intel_guc_fwif.h
> index 6a10aa6f04d3..5131e67e663f 100644
> --- a/drivers/gpu/drm/i915/intel_guc_fwif.h
> +++ b/drivers/gpu/drm/i915/intel_guc_fwif.h
> @@ -23,9 +23,6 @@
> #ifndef _INTEL_GUC_FWIF_H
> #define _INTEL_GUC_FWIF_H
>
> -#define GUC_CORE_FAMILY_GEN9 12
> -#define GUC_CORE_FAMILY_UNKNOWN 0x7fffffff
> -
> #define GUC_CLIENT_PRIORITY_KMD_HIGH 0
> #define GUC_CLIENT_PRIORITY_HIGH 1
> #define GUC_CLIENT_PRIORITY_KMD_NORMAL 2
> @@ -81,10 +78,6 @@
> #define GUC_CTL_ARAT_HIGH 1
> #define GUC_CTL_ARAT_LOW 2
>
> -#define GUC_CTL_DEVICE_INFO 3
I would keep GUC_CTL_DEVICE_INFO (still removing _GT_TYPE_SHIFT and
_CORE_FAMILY_SHIFT). The reason is that these constants kindof also
document what the guc_control is. Other people may even suggest to
rename it GUC_CTL_RSRVD0.
That's why we have GUC_CTL_PAGE_FAULT_CONTROL and GUC_CTL_RSRVD defined
but not used.
> -#define GUC_CTL_GT_TYPE_SHIFT 0
> -#define GUC_CTL_CORE_FAMILY_SHIFT 7
> -
> #define GUC_CTL_LOG_PARAMS 4
> #define GUC_LOG_VALID (1 << 0)
> #define GUC_LOG_NOTIFY_ON_HALF_FULL (1 << 1)
>
I think the consensus was that gt_type and core_family are not needed
now, and if someone needs them at some point in the very very distant
future, then the same person can re-add them, so
Acked-by: Michel Thierry <michel.thierry@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-05 18:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 18:42 [PATCH] drm/i915/guc: Removed unused GuC parameters Piotr Piórkowski
2018-02-28 19:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-28 20:26 ` [PATCH] " Michel Thierry
2018-02-28 22:07 ` Michel Thierry
2018-03-01 8:02 ` Chris Wilson
2018-03-01 12:05 ` Sagar Arun Kamble
2018-03-01 19:14 ` John Spotswood
2018-03-02 7:23 ` Sagar Arun Kamble
2018-03-05 11:12 ` Piorkowski, Piotr
2018-03-06 23:50 ` John Spotswood
2018-02-28 23:57 ` ✗ Fi.CI.IGT: failure for " Patchwork
2018-03-05 13:13 ` [PATCH v2] drm/i915/guc: Remove GUC_CTL_DEVICE_INFO parameter Piotr Piórkowski
2018-03-05 18:12 ` Michel Thierry [this message]
2018-03-06 4:37 ` Sagar Arun Kamble
2018-04-13 8:55 ` Piorkowski, Piotr
2018-03-06 12:06 ` [PATCH v3] " Piotr Piórkowski
2018-04-13 8:52 ` [PATCH v4] " Piotr Piórkowski
2018-04-13 12:23 ` Chris Wilson
2018-03-05 13:37 ` ✗ Fi.CI.BAT: failure for drm/i915/guc: Removed unused GuC parameters. (rev2) Patchwork
2018-03-06 13:23 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Removed unused GuC parameters. (rev3) Patchwork
2018-03-06 17:41 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-04-13 10:33 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Removed unused GuC parameters. (rev4) Patchwork
2018-04-13 11:22 ` ✓ 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=68658b4f-b08c-36dd-0bd6-41afde2acec3@intel.com \
--to=michel.thierry@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=piotr.piorkowski@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