Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v8 1/1] drm/xe: Add helper macro to loop each dss
Date: Thu, 8 Feb 2024 23:53:06 +0000	[thread overview]
Message-ID: <5e6380adbc46c0b309681f23fddd579362e36853.camel@intel.com> (raw)
In-Reply-To: <20240201001417.354270-2-zhanjun.dong@intel.com>

On Wed, 2024-01-31 at 16:14 -0800, Zhanjun Dong wrote:
> 
alan:snip


> @@ -167,3 +164,28 @@ bool xe_gt_topology_has_dss_in_quadrant(struct
> xe_gt *gt, int quad)
>  
>         return quad_first < (quad + 1) * dss_per_quad;
>  }
> +
> +/**
> + * xe_gt_topology_get_next_dss - returns the next DSS id from a
> start position
> 
> + * @gt: GT structure
> + * @from: An index to start search form
> + *
> + * Search from topology dss masks, returns the dss ID indicate the
> next bit was set.
> + * Depends on platform construction, dss could be on geometry or on
> compute mask.
> + * The combined bit mask supports it all.
alan: nit.. i could over editting this so feel free to ignore or clip,
but I believe this documentation might read better as:

Search from this GT's DSS-fuses-topology and return the DSS-ID of the
next valid DSS instance after DSS-ID 'from'. Depending on the platform
construction, DSS instances could be for geometry (RENDER engine) or
compute (COMPUTE engine). However, all current platforms that have
both engines have the same instances thus we can combine both masks
internally before performing this operation.
> + *
> + * Return -1 if not found since given "from" position.
> + */
alan:snip

alan: Going thru v6's review comments from Matt, it looks like you've
addressed them all. Since above is a nit, here is my RB:

Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>

  reply	other threads:[~2024-02-08 23:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  0:14 [PATCH v8 0/1] drm/xe: Add helper macro to loop each dss Zhanjun Dong
2024-02-01  0:14 ` [PATCH v8 1/1] " Zhanjun Dong
2024-02-08 23:53   ` Teres Alexis, Alan Previn [this message]
2024-02-01  0:49 ` ✓ CI.Patch_applied: success for drm/xe: Add helper macro to loop each dss (rev2) Patchwork
2024-02-01  0:49 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-01  0:50 ` ✓ CI.KUnit: success " Patchwork
2024-02-01  0:57 ` ✓ CI.Build: " Patchwork
2024-02-01  0:58 ` ✓ CI.Hooks: " Patchwork
2024-02-01  0:59 ` ✓ CI.checksparse: " Patchwork
2024-02-01  1:22 ` ✓ CI.BAT: " 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=5e6380adbc46c0b309681f23fddd579362e36853.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=zhanjun.dong@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