From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 3/6] drm/i915/sseu: Simplify gen11+ SSEU handling
Date: Fri, 20 May 2022 10:21:00 +0100 [thread overview]
Message-ID: <75d7a224-9395-4a18-8e34-a6e86d7dc4cd@linux.intel.com> (raw)
In-Reply-To: <20220517032005.2694737-4-matthew.d.roper@intel.com>
On 17/05/2022 04:20, Matt Roper wrote:
> Although gen11 and gen12 architectures supported the concept of multiple
> slices, in practice all the platforms that were actually designed only
> had a single slice (i.e., note the parameters to 'intel_sseu_set_info'
> that we pass for each platform). We can simplify the code slightly by
> dropping the multi-slice logic from gen11+ platforms.
>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_sseu.c | 80 ++++++++++++++--------------
> 1 file changed, 40 insertions(+), 40 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_sseu.c b/drivers/gpu/drm/i915/gt/intel_sseu.c
> index b5fd479a7b85..ade3e1805782 100644
> --- a/drivers/gpu/drm/i915/gt/intel_sseu.c
> +++ b/drivers/gpu/drm/i915/gt/intel_sseu.c
> @@ -119,52 +119,37 @@ static u16 compute_eu_total(const struct sseu_dev_info *sseu)
> return total;
> }
>
> -static u32 get_ss_stride_mask(struct sseu_dev_info *sseu, u8 s, u32 ss_en)
> -{
> - u32 ss_mask;
> -
> - ss_mask = ss_en >> (s * sseu->max_subslices);
> - ss_mask &= GENMASK(sseu->max_subslices - 1, 0);
> -
> - return ss_mask;
> -}
> -
> -static void gen11_compute_sseu_info(struct sseu_dev_info *sseu, u8 s_en,
> +static void gen11_compute_sseu_info(struct sseu_dev_info *sseu,
> u32 g_ss_en, u32 c_ss_en, u16 eu_en)
> {
> - int s, ss;
> + u32 valid_ss_mask = GENMASK(sseu->max_subslices - 1, 0);
> + int ss;
>
> /* g_ss_en/c_ss_en represent entire subslice mask across all slices */
> GEM_BUG_ON(sseu->max_slices * sseu->max_subslices >
> sizeof(g_ss_en) * BITS_PER_BYTE);
>
> - for (s = 0; s < sseu->max_slices; s++) {
> - if ((s_en & BIT(s)) == 0)
> - continue;
> + sseu->slice_mask |= BIT(0);
>
> - sseu->slice_mask |= BIT(s);
> -
> - /*
> - * XeHP introduces the concept of compute vs geometry DSS. To
> - * reduce variation between GENs around subslice usage, store a
> - * mask for both the geometry and compute enabled masks since
> - * userspace will need to be able to query these masks
> - * independently. Also compute a total enabled subslice count
> - * for the purposes of selecting subslices to use in a
> - * particular GEM context.
> - */
> - intel_sseu_set_subslices(sseu, s, sseu->compute_subslice_mask,
> - get_ss_stride_mask(sseu, s, c_ss_en));
> - intel_sseu_set_subslices(sseu, s, sseu->geometry_subslice_mask,
> - get_ss_stride_mask(sseu, s, g_ss_en));
> - intel_sseu_set_subslices(sseu, s, sseu->subslice_mask,
> - get_ss_stride_mask(sseu, s,
> - g_ss_en | c_ss_en));
> + /*
> + * XeHP introduces the concept of compute vs geometry DSS. To reduce
> + * variation between GENs around subslice usage, store a mask for both
> + * the geometry and compute enabled masks since userspace will need to
> + * be able to query these masks independently. Also compute a total
> + * enabled subslice count for the purposes of selecting subslices to
> + * use in a particular GEM context.
> + */
> + intel_sseu_set_subslices(sseu, 0, sseu->compute_subslice_mask,
> + c_ss_en & valid_ss_mask);
> + intel_sseu_set_subslices(sseu, 0, sseu->geometry_subslice_mask,
> + g_ss_en & valid_ss_mask);
> + intel_sseu_set_subslices(sseu, 0, sseu->subslice_mask,
> + (g_ss_en | c_ss_en) & valid_ss_mask);
> +
> + for (ss = 0; ss < sseu->max_subslices; ss++)
> + if (intel_sseu_has_subslice(sseu, 0, ss))
> + sseu_set_eus(sseu, 0, ss, eu_en);
>
> - for (ss = 0; ss < sseu->max_subslices; ss++)
> - if (intel_sseu_has_subslice(sseu, s, ss))
> - sseu_set_eus(sseu, s, ss, eu_en);
> - }
> sseu->eu_per_subslice = hweight16(eu_en);
> sseu->eu_total = compute_eu_total(sseu);
> }
> @@ -196,7 +181,7 @@ static void xehp_sseu_info_init(struct intel_gt *gt)
> if (eu_en_fuse & BIT(eu))
> eu_en |= BIT(eu * 2) | BIT(eu * 2 + 1);
>
> - gen11_compute_sseu_info(sseu, 0x1, g_dss_en, c_dss_en, eu_en);
> + gen11_compute_sseu_info(sseu, g_dss_en, c_dss_en, eu_en);
> }
>
> static void gen12_sseu_info_init(struct intel_gt *gt)
> @@ -216,8 +201,15 @@ static void gen12_sseu_info_init(struct intel_gt *gt)
> */
> intel_sseu_set_info(sseu, 1, 6, 16);
>
> + /*
> + * Although gen12 architecture supported multiple slices, TGL, RKL,
> + * DG1, and ADL only had a single slice.
> + */
> s_en = intel_uncore_read(uncore, GEN11_GT_SLICE_ENABLE) &
> GEN11_GT_S_ENA_MASK;
> + if (s_en != 0x1)
> + drm_dbg(>->i915->drm, "Slice mask %#x is not the expected 0x1!\n",
I'd make these drm_warn - drm_dbg feels pointless. Possibly even
drm_WARN_ON since it is supposed to be an impossible condition which
needs to be super loud if it happens.
Regards,
Tvrtko
> + s_en);
>
> g_dss_en = intel_uncore_read(uncore, GEN12_GT_GEOMETRY_DSS_ENABLE);
>
> @@ -229,7 +221,7 @@ static void gen12_sseu_info_init(struct intel_gt *gt)
> if (eu_en_fuse & BIT(eu))
> eu_en |= BIT(eu * 2) | BIT(eu * 2 + 1);
>
> - gen11_compute_sseu_info(sseu, s_en, g_dss_en, 0, eu_en);
> + gen11_compute_sseu_info(sseu, g_dss_en, 0, eu_en);
>
> /* TGL only supports slice-level power gating */
> sseu->has_slice_pg = 1;
> @@ -248,14 +240,22 @@ static void gen11_sseu_info_init(struct intel_gt *gt)
> else
> intel_sseu_set_info(sseu, 1, 8, 8);
>
> + /*
> + * Although gen11 architecture supported multiple slices, ICL and
> + * EHL/JSL only had a single slice in practice.
> + */
> s_en = intel_uncore_read(uncore, GEN11_GT_SLICE_ENABLE) &
> GEN11_GT_S_ENA_MASK;
> + if (s_en != 0x1)
> + drm_dbg(>->i915->drm, "Slice mask %#x is not the expected 0x1!\n",
> + s_en);
> +
> ss_en = ~intel_uncore_read(uncore, GEN11_GT_SUBSLICE_DISABLE);
>
> eu_en = ~(intel_uncore_read(uncore, GEN11_EU_DISABLE) &
> GEN11_EU_DIS_MASK);
>
> - gen11_compute_sseu_info(sseu, s_en, ss_en, 0, eu_en);
> + gen11_compute_sseu_info(sseu, ss_en, 0, eu_en);
>
> /* ICL has no power gating restrictions. */
> sseu->has_slice_pg = 1;
next prev parent reply other threads:[~2022-05-20 9:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 3:19 [Intel-gfx] [PATCH v2 0/6] i915: SSEU handling updates Matt Roper
2022-05-17 3:20 ` [Intel-gfx] [PATCH v2 1/6] drm/i915/xehp: Use separate sseu init function Matt Roper
2022-05-17 3:20 ` [Intel-gfx] [PATCH v2 2/6] drm/i915/xehp: Drop GETPARAM lookups of I915_PARAM_[SUB]SLICE_MASK Matt Roper
2022-05-20 9:15 ` Tvrtko Ursulin
2022-05-20 20:42 ` Matt Roper
2022-05-24 8:51 ` Tvrtko Ursulin
2022-06-01 5:59 ` Lionel Landwerlin
2022-05-17 3:20 ` [Intel-gfx] [PATCH v2 3/6] drm/i915/sseu: Simplify gen11+ SSEU handling Matt Roper
2022-05-20 9:21 ` Tvrtko Ursulin [this message]
2022-05-17 3:20 ` [Intel-gfx] [PATCH v2 4/6] drm/i915/sseu: Don't try to store EU mask internally in UAPI format Matt Roper
2022-05-20 9:32 ` Tvrtko Ursulin
2022-05-17 3:20 ` [Intel-gfx] [PATCH v2 5/6] drm/i915/sseu: Disassociate internal subslice mask representation from uapi Matt Roper
2022-05-17 15:15 ` [Intel-gfx] [PATCH v3 " Matt Roper
2022-05-20 10:07 ` Tvrtko Ursulin
2022-05-17 3:20 ` [Intel-gfx] [PATCH v2 6/6] drm/i915/pvc: Add SSEU changes Matt Roper
2022-05-17 3:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: SSEU handling updates (rev3) Patchwork
2022-05-17 3:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-05-17 4:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-17 6:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-17 18:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: SSEU handling updates (rev4) Patchwork
2022-05-17 18:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-05-17 19:08 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-05-17 19:19 ` Matt Roper
2022-05-17 20:44 ` Vudum, Lakshminarayana
2022-05-17 20:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-18 0:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-18 3:24 ` Matt Roper
2022-05-18 16:51 ` Vudum, Lakshminarayana
2022-05-18 15:55 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=75d7a224-9395-4a18-8e34-a6e86d7dc4cd@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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