From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu
Date: Thu, 11 Jan 2018 11:21:06 +0000 [thread overview]
Message-ID: <6ff059a5-886a-eac2-ed1b-d435a333e49a@linux.intel.com> (raw)
In-Reply-To: <20171218153520.14181-3-lionel.g.landwerlin@intel.com>
On 18/12/2017 15:35, Lionel Landwerlin wrote:
> Now that we have that information in topology fields, let's just reused it.
>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 26 ++++++++++----------------
> 1 file changed, 10 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 0c7890b695c5..6ec7543e698f 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -4308,11 +4308,11 @@ static void gen10_sseu_device_status(struct drm_i915_private *dev_priv,
> struct sseu_dev_info *sseu)
> {
> const struct intel_device_info *info = INTEL_INFO(dev_priv);
> - int s_max = 6, ss_max = 4;
> int s, ss;
> - u32 s_reg[s_max], eu_reg[2 * s_max], eu_mask[2];
> + u32 s_reg[info->sseu.max_slices],
> + eu_reg[2 * info->sseu.max_subslices], eu_mask[2];
This is a bit unusual style, perhaps split into separate declarations.
>
> - for (s = 0; s < s_max; s++) {
> + for (s = 0; s < info->sseu.max_slices; s++) {
> /*
> * FIXME: Valid SS Mask respects the spec and read
> * only valid bits for those registers, excluding reserverd
> @@ -4334,7 +4334,7 @@ static void gen10_sseu_device_status(struct drm_i915_private *dev_priv,
> GEN9_PGCTL_SSB_EU210_ACK |
> GEN9_PGCTL_SSB_EU311_ACK;
>
> - for (s = 0; s < s_max; s++) {
> + for (s = 0; s < info->sseu.max_slices; s++) {
> if ((s_reg[s] & GEN9_PGCTL_SLICE_ACK) == 0)
> /* skip disabled slice */
> continue;
> @@ -4342,7 +4342,7 @@ static void gen10_sseu_device_status(struct drm_i915_private *dev_priv,
> sseu->slice_mask |= BIT(s);
> sseu->subslices_mask[s] = info->sseu.subslices_mask[s];
>
> - for (ss = 0; ss < ss_max; ss++) {
> + for (ss = 0; ss < info->sseu.max_subslices; ss++) {
> unsigned int eu_cnt;
>
> if (!(s_reg[s] & (GEN9_PGCTL_SS_ACK(ss))))
> @@ -4362,17 +4362,11 @@ static void gen10_sseu_device_status(struct drm_i915_private *dev_priv,
> static void gen9_sseu_device_status(struct drm_i915_private *dev_priv,
> struct sseu_dev_info *sseu)
> {
> - int s_max = 3, ss_max = 4;
> + const struct intel_device_info *info = INTEL_INFO(dev_priv);
> int s, ss;
> - u32 s_reg[s_max], eu_reg[2*s_max], eu_mask[2];
> -
> - /* BXT has a single slice and at most 3 subslices. */
> - if (IS_GEN9_LP(dev_priv)) {
> - s_max = 1;
> - ss_max = 3;
> - }
> + u32 s_reg[info->sseu.max_slices], eu_reg[2*info->sseu.max_subslices], eu_mask[2];
Spaces around operators are preferred.
>
> - for (s = 0; s < s_max; s++) {
> + for (s = 0; s < info->sseu.max_slices; s++) {
> s_reg[s] = I915_READ(GEN9_SLICE_PGCTL_ACK(s));
> eu_reg[2*s] = I915_READ(GEN9_SS01_EU_PGCTL_ACK(s));
> eu_reg[2*s + 1] = I915_READ(GEN9_SS23_EU_PGCTL_ACK(s));
> @@ -4387,7 +4381,7 @@ static void gen9_sseu_device_status(struct drm_i915_private *dev_priv,
> GEN9_PGCTL_SSB_EU210_ACK |
> GEN9_PGCTL_SSB_EU311_ACK;
>
> - for (s = 0; s < s_max; s++) {
> + for (s = 0; s < info->sseu.max_slices; s++) {
> if ((s_reg[s] & GEN9_PGCTL_SLICE_ACK) == 0)
> /* skip disabled slice */
> continue;
> @@ -4398,7 +4392,7 @@ static void gen9_sseu_device_status(struct drm_i915_private *dev_priv,
> sseu->subslices_mask[s] =
> INTEL_INFO(dev_priv)->sseu.subslices_mask[s];
>
> - for (ss = 0; ss < ss_max; ss++) {
> + for (ss = 0; ss < info->sseu.max_subslices; ss++) {
> unsigned int eu_cnt;
>
> if (IS_GEN9_LP(dev_priv)) {
>
With the formatting tweaks,
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-11 11:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 15:35 [PATCH 0/6] drm/i915: expose RCS topology to userspace Lionel Landwerlin
2017-12-18 15:35 ` [PATCH 1/6] drm/i915: store all subslice masks Lionel Landwerlin
2018-01-11 11:12 ` Tvrtko Ursulin
2018-01-11 15:48 ` Lionel Landwerlin
2018-01-11 15:57 ` Tvrtko Ursulin
2018-01-11 16:00 ` Lionel Landwerlin
2017-12-18 15:35 ` [PATCH 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2018-01-11 11:21 ` Tvrtko Ursulin [this message]
2018-01-11 15:50 ` Lionel Landwerlin
2017-12-18 15:35 ` [PATCH 3/6] drm/i915/debugfs: add rcs topology entry Lionel Landwerlin
2018-01-11 11:31 ` Tvrtko Ursulin
2018-01-11 17:04 ` Lionel Landwerlin
2017-12-18 15:35 ` [PATCH 4/6] drm/i915: add rcs topology to error state Lionel Landwerlin
2017-12-18 15:43 ` Chris Wilson
2017-12-18 15:35 ` [PATCH 5/6] drm/i915: add query uAPI Lionel Landwerlin
2018-01-11 12:19 ` Tvrtko Ursulin
2018-01-11 17:08 ` Lionel Landwerlin
2017-12-18 15:35 ` [PATCH 6/6] drm/i915: expose rcs topology through " Lionel Landwerlin
2018-01-11 12:45 ` Tvrtko Ursulin
2018-01-11 18:38 ` Lionel Landwerlin
2018-01-12 8:55 ` Tvrtko Ursulin
2017-12-18 16:07 ` ✗ Fi.CI.BAT: warning for drm/i915: expose RCS topology to userspace Patchwork
2018-01-08 16:30 ` [PATCH 0/6] " Lionel Landwerlin
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=6ff059a5-886a-eac2-ed1b-d435a333e49a@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@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