From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: [CI 1/2] Revert "drm/i915/gt: Do not generate the command streamer for all the CCS"
Date: Mon, 22 Apr 2024 18:27:30 +0200 [thread overview]
Message-ID: <20240422162731.7046-2-andi.shyti@linux.intel.com> (raw)
In-Reply-To: <20240422162731.7046-1-andi.shyti@linux.intel.com>
This reverts commit ea315f98e5d6d3191b74beb0c3e5fc16081d517c.
---
drivers/gpu/drm/i915/gt/intel_engine_cs.c | 17 -----------------
1 file changed, 17 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_engine_cs.c b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
index 8c44af1c3451..476651bd0a21 100644
--- a/drivers/gpu/drm/i915/gt/intel_engine_cs.c
+++ b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
@@ -874,23 +874,6 @@ static intel_engine_mask_t init_engine_mask(struct intel_gt *gt)
info->engine_mask &= ~BIT(GSC0);
}
- /*
- * Do not create the command streamer for CCS slices beyond the first.
- * All the workload submitted to the first engine will be shared among
- * all the slices.
- *
- * Once the user will be allowed to customize the CCS mode, then this
- * check needs to be removed.
- */
- if (IS_DG2(gt->i915)) {
- u8 first_ccs = __ffs(CCS_MASK(gt));
-
- /* Mask off all the CCS engine */
- info->engine_mask &= ~GENMASK(CCS3, CCS0);
- /* Put back in the first CCS engine */
- info->engine_mask |= BIT(_CCS(first_ccs));
- }
-
return info->engine_mask;
}
--
2.43.0
next prev parent reply other threads:[~2024-04-22 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 16:27 [CI 0/2] Force CCS mode to the maximum Andi Shyti
2024-04-22 16:27 ` Andi Shyti [this message]
2024-04-22 16:27 ` [CI 2/2] drm/i915/gt: Force ccs_mode 4 Andi Shyti
2024-04-22 17:20 ` ✗ Fi.CI.CHECKPATCH: warning for Force CCS mode to the maximum Patchwork
2024-04-22 17:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-22 17:28 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-23 9:08 ` ✗ 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=20240422162731.7046-2-andi.shyti@linux.intel.com \
--to=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.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