dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Zhi Wang <zhi.a.wang@intel.com>, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 07/11] drm/i915/pvc: Engines definitions for new copy engines
Date: Tue, 3 May 2022 09:05:43 +0100	[thread overview]
Message-ID: <472e2679-abc5-8881-6f93-f64ec1feb365@linux.intel.com> (raw)
In-Reply-To: <20220502163417.2635462-8-matthew.d.roper@intel.com>


On 02/05/2022 17:34, Matt Roper wrote:
> This patch adds the basic definitions needed to support
> new copy engines. Also updating the cmd_info to accommodate
> new engines, as the engine id's of legacy engines have been
> changed.
> 
> Original-author: CQ Tang
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
>   drivers/gpu/drm/i915/gt/intel_engine_cs.c    | 56 ++++++++++++++++++++
>   drivers/gpu/drm/i915/gt/intel_engine_types.h | 10 +++-
>   drivers/gpu/drm/i915/gt/intel_gt_regs.h      |  8 +++
>   drivers/gpu/drm/i915/gvt/cmd_parser.c        |  2 +-
>   drivers/gpu/drm/i915/i915_reg.h              |  8 +++
>   5 files changed, 82 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_cs.c b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
> index 14c6ddbbfde8..4532c3ea9ace 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_cs.c
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_cs.c
> @@ -71,6 +71,62 @@ static const struct engine_info intel_engines[] = {
>   			{ .graphics_ver = 6, .base = BLT_RING_BASE }
>   		},
>   	},
> +	[BCS1] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 1,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS1_RING_BASE }
> +		},
> +	},
> +	[BCS2] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 2,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS2_RING_BASE }
> +		},
> +	},
> +	[BCS3] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 3,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS3_RING_BASE }
> +		},
> +	},
> +	[BCS4] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 4,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS4_RING_BASE }
> +		},
> +	},
> +	[BCS5] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 5,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS5_RING_BASE }
> +		},
> +	},
> +	[BCS6] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 6,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS6_RING_BASE }
> +		},
> +	},
> +	[BCS7] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 7,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS7_RING_BASE }
> +		},
> +	},
> +	[BCS8] = {
> +		.class = COPY_ENGINE_CLASS,
> +		.instance = 8,
> +		.mmio_bases = {
> +			{ .graphics_ver = 12, .base = XEHPC_BCS8_RING_BASE }
> +		},
> +	},
>   	[VCS0] = {
>   		.class = VIDEO_DECODE_CLASS,
>   		.instance = 0,
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_types.h b/drivers/gpu/drm/i915/gt/intel_engine_types.h
> index 298f2cc7a879..356c15cdccf0 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_types.h
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_types.h
> @@ -35,7 +35,7 @@
>   #define OTHER_CLASS		4
>   #define COMPUTE_CLASS		5
>   #define MAX_ENGINE_CLASS	5
> -#define MAX_ENGINE_INSTANCE	7
> +#define MAX_ENGINE_INSTANCE	8
>   
>   #define I915_MAX_SLICES	3
>   #define I915_MAX_SUBSLICES 8
> @@ -107,6 +107,14 @@ struct i915_ctx_workarounds {
>   enum intel_engine_id {
>   	RCS0 = 0,
>   	BCS0,
> +	BCS1,
> +	BCS2,
> +	BCS3,
> +	BCS4,
> +	BCS5,
> +	BCS6,
> +	BCS7,
> +	BCS8,

_BCS(n) macro will not be required?

>   	VCS0,
>   	VCS1,
>   	VCS2,
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
> index a0a49c16babd..aa2c0974b02c 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
> @@ -1476,6 +1476,14 @@
>   #define   GEN11_KCR				(19)
>   #define   GEN11_GTPM				(16)
>   #define   GEN11_BCS				(15)
> +#define   XEHPC_BCS1				(14)
> +#define   XEHPC_BCS2				(13)
> +#define   XEHPC_BCS3				(12)
> +#define   XEHPC_BCS4				(11)
> +#define   XEHPC_BCS5				(10)
> +#define   XEHPC_BCS6				(9)
> +#define   XEHPC_BCS7				(8)
> +#define   XEHPC_BCS8				(23)
>   #define   GEN12_CCS3				(7)
>   #define   GEN12_CCS2				(6)
>   #define   GEN12_CCS1				(5)
> diff --git a/drivers/gpu/drm/i915/gvt/cmd_parser.c b/drivers/gpu/drm/i915/gvt/cmd_parser.c
> index b9eb75a2b400..0ba2a3455d99 100644
> --- a/drivers/gpu/drm/i915/gvt/cmd_parser.c
> +++ b/drivers/gpu/drm/i915/gvt/cmd_parser.c
> @@ -428,7 +428,7 @@ struct cmd_info {
>   #define R_VECS	BIT(VECS0)
>   #define R_ALL (R_RCS | R_VCS | R_BCS | R_VECS)
>   	/* rings that support this cmd: BLT/RCS/VCS/VECS */
> -	u16 rings;
> +	intel_engine_mask_t rings;

Looks like mask already overflows u16 even without the blitter engines. 
(When CCS were added.) Meaning maybe there should be a separate patch to 
fix it.

But good question though is GVT supporting CCS and should it be part of 
R_ALL? Or should this patch even be touching GVT since CCS enablement 
did not? Adding Zhi to comment.

Regards,

Tvrtko

>   
>   	/* devices that support this cmd: SNB/IVB/HSW/... */
>   	u16 devices;
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 4a3d7b96ef43..ab64ab4317b3 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -976,6 +976,14 @@
>   #define GEN12_COMPUTE2_RING_BASE	0x1e000
>   #define GEN12_COMPUTE3_RING_BASE	0x26000
>   #define BLT_RING_BASE		0x22000
> +#define XEHPC_BCS1_RING_BASE	0x3e0000
> +#define XEHPC_BCS2_RING_BASE	0x3e2000
> +#define XEHPC_BCS3_RING_BASE	0x3e4000
> +#define XEHPC_BCS4_RING_BASE	0x3e6000
> +#define XEHPC_BCS5_RING_BASE	0x3e8000
> +#define XEHPC_BCS6_RING_BASE	0x3ea000
> +#define XEHPC_BCS7_RING_BASE	0x3ec000
> +#define XEHPC_BCS8_RING_BASE	0x3ee000
>   #define DG1_GSC_HECI1_BASE	0x00258000
>   #define DG1_GSC_HECI2_BASE	0x00259000
>   #define DG2_GSC_HECI1_BASE	0x00373000

  parent reply	other threads:[~2022-05-03  8:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 16:34 [PATCH 00/11] i915: Introduce Ponte Vecchio Matt Roper
2022-05-02 16:34 ` [PATCH 01/11] drm/i915/pvc: add initial Ponte Vecchio definitions Matt Roper
2022-05-02 20:44   ` Lucas De Marchi
2022-05-02 16:34 ` [PATCH 02/11] drm/i915/pvc: Add forcewake support Matt Roper
2022-05-02 22:33   ` Summers, Stuart
2022-05-05  0:34     ` Matt Roper
2022-05-02 16:34 ` [PATCH 03/11] drm/i915/pvc: Define MOCS table for PVC Matt Roper
2022-05-02 16:50   ` Matt Roper
2022-05-02 18:39     ` [Intel-gfx] " Lucas De Marchi
2022-05-02 18:50       ` Matt Roper
2022-05-02 19:27         ` Lucas De Marchi
2022-05-02 19:42           ` Matt Roper
2022-05-02 21:03   ` Lucas De Marchi
2022-05-02 21:14     ` Matt Roper
2022-05-03  6:22       ` Lucas De Marchi
2022-05-02 16:34 ` [PATCH 04/11] drm/i915/pvc: Read correct RP_STATE_CAP register Matt Roper
2022-05-02 16:55   ` Rodrigo Vivi
2022-05-02 16:34 ` [PATCH 05/11] drm/i915/pvc: Remove additional 3D flags from PIPE_CONTROL Matt Roper
2022-05-02 16:34 ` [PATCH 06/11] drm/i915/pvc: Reduce stack usage in reset selftest with extra blitter engine Matt Roper
2022-05-02 18:46   ` Souza, Jose
2022-05-03  8:25   ` [Intel-gfx] " Tvrtko Ursulin
2022-05-02 16:34 ` [PATCH 07/11] drm/i915/pvc: Engines definitions for new copy engines Matt Roper
2022-05-02 18:45   ` [Intel-gfx] " Souza, Jose
2022-05-03  8:05   ` Tvrtko Ursulin [this message]
2022-05-05 20:59     ` Matt Roper
2022-05-06  7:21       ` Tvrtko Ursulin
2022-05-06 14:29         ` Matt Roper
2022-05-02 16:34 ` [PATCH 08/11] drm/i915/pvc: Interrupt support " Matt Roper
2022-05-02 22:23   ` Summers, Stuart
2022-05-02 16:34 ` [PATCH 09/11] drm/i915/pvc: Reset " Matt Roper
2022-05-02 18:44   ` [Intel-gfx] " Souza, Jose
2022-05-02 22:23   ` Summers, Stuart
2022-05-02 16:34 ` [PATCH 10/11] drm/i915/pvc: skip all copy engines from aux table invalidate Matt Roper
2022-05-02 18:40   ` [Intel-gfx] " Souza, Jose
2022-05-02 22:58   ` Kumar Valsan, Prathap
2022-05-02 16:34 ` [PATCH 11/11] drm/i915/pvc: read fuses for link copy engines Matt Roper
2022-05-02 18:48   ` Souza, Jose
2022-05-03  8:19   ` [Intel-gfx] " Tvrtko Ursulin
2022-05-03  8:21 ` [Intel-gfx] [PATCH 00/11] i915: Introduce Ponte Vecchio Tvrtko Ursulin
2022-05-03 14:56   ` Matt Roper
2022-05-03 15:01     ` Tvrtko Ursulin

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=472e2679-abc5-8881-6f93-f64ec1feb365@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 \
    --cc=zhi.a.wang@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;
as well as URLs for NNTP newsgroup(s).