From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jackie Li <yaodong.li@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
Subject: Re: [PATCH 1/2] drm/i915: implemented dynamic WOPCM partition.
Date: Mon, 6 Nov 2017 15:24:38 +0200 [thread overview]
Message-ID: <20171106132438.GG10981@intel.com> (raw)
In-Reply-To: <1509753670-27369-1-git-send-email-yaodong.li@intel.com>
On Fri, Nov 03, 2017 at 05:01:09PM -0700, Jackie Li wrote:
> Static WOPCM partitioning would lead to GuC loading failure
> if the GuC/HuC firmware size exceeded current static 512KB
> partition boundary.
>
> This patch enabled the dynamical calculation of the WOPCM aperture
> used by GuC/HuC firmware. GuC WOPCM offset was set to
> HuC size + reserved WOPCM size. GuC WOPCM size was set to
> total WOPCM size - GuC WOPCM offset - RC6CTX size.
>
> Signed-off-by: Jackie Li <yaodong.li@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> Cc: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
> Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Reviewed-by: John Spotswood <john.a.spotswood@intel.com>
> Reviewed-by: Oscar Mateo <oscar.mateo@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.c | 15 ++++
> drivers/gpu/drm/i915/i915_drv.h | 13 ++++
> drivers/gpu/drm/i915/i915_gem_context.c | 4 +-
> drivers/gpu/drm/i915/i915_guc_reg.h | 18 ++++-
> drivers/gpu/drm/i915/intel_guc.c | 46 ++++++++++--
> drivers/gpu/drm/i915/intel_guc.h | 18 +----
> drivers/gpu/drm/i915/intel_huc.c | 3 +-
> drivers/gpu/drm/i915/intel_uc.c | 128 +++++++++++++++++++++++++++++++-
> drivers/gpu/drm/i915/intel_uc_fw.c | 12 ++-
> 9 files changed, 223 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index e7e9e06..19509fd 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -623,6 +623,15 @@ static void i915_gem_fini(struct drm_i915_private *dev_priv)
> WARN_ON(!list_empty(&dev_priv->contexts.list));
> }
>
> +static void i915_wopcm_init(struct drm_i915_private *dev_priv)
> +{
> + struct intel_wopcm_info *wopcm = &dev_priv->wopcm;
> +
> + wopcm->size = WOPCM_DEFAULT_SIZE;
> +
> + DRM_DEBUG_DRIVER("WOPCM size: %dKB\n", wopcm->size >> 10);
> +}
> +
> static int i915_load_modeset_init(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = to_i915(dev);
> @@ -670,6 +679,12 @@ static int i915_load_modeset_init(struct drm_device *dev)
> if (ret)
> goto cleanup_irq;
>
> + /*
> + * Get the wopcm memory info.
> + * NOTE: this need to be called before init FW.
> + */
> + i915_wopcm_init(dev_priv);
Is this guc wopcm somehow related to the normal wopcm? And if so
are you planning to use the wopcm information we extract from the
hardware in stolen init? If this is just related to the guc then
it would seem better to bury this in some guc code.
> +
> intel_uc_init_fw(dev_priv);
>
> ret = i915_gem_init(dev_priv);
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-06 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 0:01 [PATCH 1/2] drm/i915: implemented dynamic WOPCM partition Jackie Li
2017-11-04 0:01 ` [PATCH 2/2] HAX enable guc submission for CI Jackie Li
2017-11-04 0:16 ` [PATCH 1/2] drm/i915: implemented dynamic WOPCM partition Yaodong Li
2017-11-04 0:20 ` ✗ Fi.CI.BAT: warning for series starting with [1/2] " Patchwork
2017-11-06 13:24 ` Ville Syrjälä [this message]
2017-11-06 18:20 ` [PATCH 1/2] " Yaodong Li
2017-11-08 12:33 ` ✗ Fi.CI.BAT: warning for series starting with [1/2] " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-11-04 0:18 [PATCH 1/2] " Jackie Li
2017-11-06 8:16 ` Sagar Arun Kamble
2017-11-06 20:22 ` Yaodong Li
2017-11-07 10:52 ` Joonas Lahtinen
2017-11-09 22:18 ` Yaodong Li
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=20171106132438.GG10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sujaritha.sundaresan@intel.com \
--cc=yaodong.li@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;
as well as URLs for NNTP newsgroup(s).