From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/5] drm/i915/mtl: add initial definitions for GSC CS
Date: Mon, 31 Oct 2022 09:43:33 -0700 [thread overview]
Message-ID: <d9b96da5-0995-1c11-5484-fb2518b4a563@intel.com> (raw)
In-Reply-To: <Y1/3QfxBQt5Hs0m0@mdroper-desk1.amr.corp.intel.com>
On 10/31/2022 9:26 AM, Matt Roper wrote:
> On Thu, Oct 27, 2022 at 03:15:50PM -0700, Daniele Ceraolo Spurio wrote:
>> Starting on MTL, the GSC is no longer managed with direct MMIO access,
>> but we instead have a dedicated command streamer for it. As a first step
>> for adding support for this CS, add the required definitions.
>> Note that, although it is now a CS, the GSC retains its old
>> class:instance value (OTHER_CLASS instance 6)
>>
>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
> Now that we have an OTHER_CLASS engine, I think we also need to deal
> with the class -> reg mapping table in mmio_invalidate_full(). I think
> the register we want is 0xCF04?
I missed that. Looks like the the situation is a bit more complex than
just adding the new register, because on pre-MTL platforms CF04 is the
compute class invalidation register. On MTL as you said CF04 is marked
as the GSC CS invalidation register, but I can't find the compute one.
Do you know if it re-uses the render one or something like that?
Given that there seem to be non-GSC related changes as well, IMO this
should probably be a separate patch to specifically handle the TLB inval
changes on MTL.
Daniele
>
> Matt
>
>> ---
>> drivers/gpu/drm/i915/gt/intel_engine_cs.c | 8 ++++++++
>> drivers/gpu/drm/i915/gt/intel_engine_types.h | 1 +
>> drivers/gpu/drm/i915/gt/intel_engine_user.c | 1 +
>> drivers/gpu/drm/i915/i915_reg.h | 1 +
>> 4 files changed, 11 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_cs.c b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
>> index 3b7d750ad054..e0fbfac03979 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_engine_cs.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
>> @@ -244,6 +244,13 @@ static const struct engine_info intel_engines[] = {
>> { .graphics_ver = 12, .base = GEN12_COMPUTE3_RING_BASE }
>> }
>> },
>> + [GSC0] = {
>> + .class = OTHER_CLASS,
>> + .instance = OTHER_GSC_INSTANCE,
>> + .mmio_bases = {
>> + { .graphics_ver = 12, .base = MTL_GSC_RING_BASE }
>> + }
>> + },
>> };
>>
>> /**
>> @@ -324,6 +331,7 @@ u32 intel_engine_context_size(struct intel_gt *gt, u8 class)
>> case VIDEO_DECODE_CLASS:
>> case VIDEO_ENHANCEMENT_CLASS:
>> case COPY_ENGINE_CLASS:
>> + case OTHER_CLASS:
>> if (GRAPHICS_VER(gt->i915) < 8)
>> return 0;
>> return GEN8_LR_CONTEXT_OTHER_SIZE;
>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_types.h b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>> index 6b5d4ea22b67..4fd54fb8810f 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_engine_types.h
>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_types.h
>> @@ -136,6 +136,7 @@ enum intel_engine_id {
>> CCS2,
>> CCS3,
>> #define _CCS(n) (CCS0 + (n))
>> + GSC0,
>> I915_NUM_ENGINES
>> #define INVALID_ENGINE ((enum intel_engine_id)-1)
>> };
>> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_user.c b/drivers/gpu/drm/i915/gt/intel_engine_user.c
>> index 46a174f8aa00..79312b734690 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_engine_user.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_engine_user.c
>> @@ -140,6 +140,7 @@ const char *intel_engine_class_repr(u8 class)
>> [COPY_ENGINE_CLASS] = "bcs",
>> [VIDEO_DECODE_CLASS] = "vcs",
>> [VIDEO_ENHANCEMENT_CLASS] = "vecs",
>> + [OTHER_CLASS] = "other",
>> [COMPUTE_CLASS] = "ccs",
>> };
>>
>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>> index 1c0da50c0dc7..d056c3117ef2 100644
>> --- a/drivers/gpu/drm/i915/i915_reg.h
>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>> @@ -970,6 +970,7 @@
>> #define GEN11_VEBOX2_RING_BASE 0x1d8000
>> #define XEHP_VEBOX3_RING_BASE 0x1e8000
>> #define XEHP_VEBOX4_RING_BASE 0x1f8000
>> +#define MTL_GSC_RING_BASE 0x11a000
>> #define GEN12_COMPUTE0_RING_BASE 0x1a000
>> #define GEN12_COMPUTE1_RING_BASE 0x1c000
>> #define GEN12_COMPUTE2_RING_BASE 0x1e000
>> --
>> 2.37.3
>>
next prev parent reply other threads:[~2022-10-31 16:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 22:15 [Intel-gfx] [PATCH 0/5] Introduce the GSC CS Daniele Ceraolo Spurio
2022-10-27 22:15 ` [Intel-gfx] [PATCH 1/5] drm/i915/mtl: add initial definitions for " Daniele Ceraolo Spurio
2022-10-27 23:25 ` Matt Roper
2022-10-31 16:26 ` Matt Roper
2022-10-31 16:43 ` Ceraolo Spurio, Daniele [this message]
2022-10-31 18:36 ` Matt Roper
2022-10-27 22:15 ` [Intel-gfx] [PATCH 2/5] drm/i915/mtl: pass the GSC CS info to the GuC Daniele Ceraolo Spurio
2022-10-27 23:50 ` Matt Roper
2022-10-27 22:15 ` [Intel-gfx] [PATCH 3/5] drm/i915/mtl: add GSC CS interrupt support Daniele Ceraolo Spurio
2022-10-28 3:11 ` Matt Roper
2022-10-28 8:38 ` Tvrtko Ursulin
2022-10-28 17:00 ` Ceraolo Spurio, Daniele
2022-10-31 12:55 ` Tvrtko Ursulin
2022-10-31 14:54 ` Ceraolo Spurio, Daniele
2022-10-27 22:15 ` [Intel-gfx] [PATCH 4/5] drm/i915/mtl: add GSC CS reset support Daniele Ceraolo Spurio
2022-10-28 3:31 ` Matt Roper
2022-10-27 22:15 ` [Intel-gfx] [PATCH 5/5] drm/i915/mtl: don't expose GSC command streamer to the user Daniele Ceraolo Spurio
2022-10-28 3:40 ` Matt Roper
2022-10-28 17:14 ` Ceraolo Spurio, Daniele
2022-10-28 18:01 ` Matt Roper
2022-10-27 23:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce the GSC CS Patchwork
2022-10-27 23:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-27 23:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-28 13:45 ` [Intel-gfx] ✗ 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=d9b96da5-0995-1c11-5484-fb2518b4a563@intel.com \
--to=daniele.ceraolospurio@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