All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/7] drm/i915: Don't try to partition WOPCM without GuC firmware
Date: Wed, 07 Aug 2019 18:31:59 +0100	[thread overview]
Message-ID: <156519911945.6198.13711947654484594460@skylake-alporthouse-com> (raw)
In-Reply-To: <20190807170034.8440-5-michal.wajdeczko@intel.com>

Quoting Michal Wajdeczko (2019-08-07 18:00:31)
> For meaningful WOPCM partitioning we need GuC (and optionally HuC)
> firmware size(s) and we shouldn't just rely on GuC support flag,
> as we might fail to fetch GuC firmware and it's size will be 0
> and all calculations will be just wrong/useless.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  drivers/gpu/drm/i915/intel_wopcm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_wopcm.c b/drivers/gpu/drm/i915/intel_wopcm.c
> index 4c22143ee84f..5e5c3fd3472d 100644
> --- a/drivers/gpu/drm/i915/intel_wopcm.c
> +++ b/drivers/gpu/drm/i915/intel_wopcm.c
> @@ -170,7 +170,7 @@ void intel_wopcm_init(struct intel_wopcm *wopcm)
>         u32 guc_wopcm_rsvd;
>         int err;
>  
> -       if (!USES_GUC(i915))
> +       if (!guc_fw_size)
>                 return;

It looks like the calculations with huc_fw_size=0 are fine, just hope
the fw agrees.

Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-08-07 17:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 17:00 [PATCH 0/7] Hardening firmware fetch Michal Wajdeczko
2019-08-07 17:00 ` [PATCH 1/7] drm/i915/uc: Prefer dev_info for reporting options Michal Wajdeczko
2019-08-07 17:22   ` Chris Wilson
2019-08-07 17:00 ` [PATCH 2/7] drm/i915/uc: HuC firmware can't be supported without GuC Michal Wajdeczko
2019-08-07 17:27   ` Chris Wilson
2019-08-07 20:21   ` Kumar Valsan, Prathap
2019-08-07 20:12     ` Michal Wajdeczko
2019-08-07 17:00 ` [PATCH 3/7] drm/i915/uc: Don't fetch HuC fw if GuC fw fetch already failed Michal Wajdeczko
2019-08-07 17:29   ` Chris Wilson
2019-08-07 17:00 ` [PATCH 4/7] drm/i915: Don't try to partition WOPCM without GuC firmware Michal Wajdeczko
2019-08-07 17:31   ` Chris Wilson [this message]
2019-08-07 17:00 ` [PATCH 5/7] drm/i915: Make wopcm_to_i915() private Michal Wajdeczko
2019-08-07 17:32   ` Chris Wilson
2019-08-07 17:00 ` [PATCH 6/7] drm/i915/uc: WOPCM programming errors are not always real Michal Wajdeczko
2019-08-07 17:34   ` Chris Wilson
2019-08-07 17:00 ` [PATCH 7/7] drm/i915/uc: Hardening firmware fetch Michal Wajdeczko
2019-08-07 17:45   ` Chris Wilson
2019-08-07 18:37   ` Michal Wajdeczko
2019-08-07 18:50     ` Chris Wilson
2019-08-07 18:16 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-08-07 19:42 ` ✓ Fi.CI.BAT: success for Hardening firmware fetch (rev2) Patchwork
2019-08-07 20:19   ` Chris Wilson
2019-08-08  8:51 ` ✗ Fi.CI.IGT: failure " 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=156519911945.6198.13711947654484594460@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.wajdeczko@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.