intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Jackie Li <yaodong.li@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 1/5] drm/i915/guc: Move GuC WOPCM related code into separate files
Date: Mon, 11 Dec 2017 11:31:41 +0200	[thread overview]
Message-ID: <1512984701.5315.15.camel@linux.intel.com> (raw)
In-Reply-To: <1512769312-21993-1-git-send-email-yaodong.li@intel.com>

On Fri, 2017-12-08 at 13:41 -0800, Jackie Li wrote:
> intel_guc_reg.h should only include definition for GuC registers
> and related register bits. GuC WOPCM related values should not
> be defined in intel_guc_reg.h
> 
> This patch creates a better file structure by moving GuC WOPCM
> related definitions int to a new header intel_guc_wopcm.h
> and moving GuC WOPCM related functions to a new source file
> intel_guc_wopcm.c
> 
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> Signed-off-by: Jackie Li <yaodong.li@intel.com>

Please add Cc:s to patches for people who comment on the previous
iterations of the patches.

> +++ b/drivers/gpu/drm/i915/intel_guc_wopcm.c
> +u32 intel_guc_wopcm_size(struct intel_guc *guc)
> +{
> +	struct drm_i915_private *i915 = guc_to_i915(guc);
> +
> +	u32 wopcm_size = GUC_WOPCM_TOP;
> +
> +	/* On BXT, the top of WOPCM is reserved for RC6 context */
> +	if (IS_GEN9_LP(i915))
> +		wopcm_size -= BXT_GUC_WOPCM_RC6_RESERVED;

This is still bit confusing. How exactly is WOPCM size different from
the WOPCM top? If the WOPCM is used also by the hardware, when GuC is
disabled, then it should be intel_wopcm_*. If we only need this
information for the single GuC register programming, then I think this
should instead be local to programming that GuC register.

There should be a very clear split in the registers/functions to show
what is specific to the some hardware function and what is more
generic.

If this is all GuC related and only ever needs to be programmed for GuC
as the current naming suggest, then it's a great question why we are
not programming the register according to some firmware reported size
instead of replicating here.

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-12-11  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 21:41 [PATCH v3 1/5] drm/i915/guc: Move GuC WOPCM related code into separate files Jackie Li
2017-12-08 21:41 ` [PATCH v3 2/5] drm/i915/guc: Rename guc_ggtt_offset to intel_guc_ggtt_offset Jackie Li
2017-12-08 21:41 ` [PATCH v3 3/5] drm/i915/guc: Implement dynamic WOPCM partitioning Jackie Li
2017-12-08 21:57   ` Chris Wilson
2017-12-08 22:47     ` Yaodong Li
2017-12-08 21:41 ` [PATCH v3 4/5] drm/i915/guc: Add WOPCM partitioning support for CNL Jackie Li
2017-12-08 23:03   ` Chris Wilson
2017-12-12  0:16     ` Yaodong Li
2017-12-08 21:41 ` [PATCH v3 5/5] HAX Enable GuC Submission for CI Jackie Li
2017-12-08 22:30 ` ✗ Fi.CI.BAT: failure for series starting with [v3,1/5] drm/i915/guc: Move GuC WOPCM related code into separate files Patchwork
2017-12-11  9:31 ` Joonas Lahtinen [this message]

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=1512984701.5315.15.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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).