Intel-GFX Archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] drm/xe: Add Indirect Ring State support
Date: Mon, 6 May 2024 08:35:02 -0400	[thread overview]
Message-ID: <ZjjOdrmCgpQfkiYi@intel.com> (raw)
In-Reply-To: <20240504232955.16022-1-niranjana.vishwanathapura@intel.com>

On Sat, May 04, 2024 at 04:29:48PM -0700, Niranjana Vishwanathapura wrote:

please use intel-xe@lists.freedesktop.org for patches touching only xe.

probably a good idea to use some gitconfig identities:

[sendemail "i915"]
        to = intel-gfx@lists.freedesktop.org
[sendemail "xe"]
        to = intel-xe@lists.freedesktop.org
[sendemail "both"]
	to = intel-gfx@lists.freedesktop.org
        to = intel-xe@lists.freedesktop.org
[sendemail "igt"]
        to = igt-dev@lists.freedesktop.org

> When Indirect Ring State is enabled, the Ring Buffer state and
> Batch Buffer state are context save/restored to/form Indirect
> Ring State instead of the LRC. It is the recommended mode for
> Xe2, hence enable it by default for Xe2 platforms.
> 
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> 
> Niranjana Vishwanathapura (4):
>   drm/xe: Minor cleanup in LRC handling
>   drm/xe: Add Indirect Ring State support
>   drm/xe: Dump Indirect Ring State registers
>   drm/xe/xe2: Enable Indirect Ring State support for Xe2
> 
>  drivers/gpu/drm/xe/regs/xe_engine_regs.h |   9 +-
>  drivers/gpu/drm/xe/regs/xe_lrc_layout.h  |   7 +
>  drivers/gpu/drm/xe/xe_gt.c               |   6 +-
>  drivers/gpu/drm/xe/xe_gt.h               |   7 +
>  drivers/gpu/drm/xe/xe_gt_types.h         |   6 +-
>  drivers/gpu/drm/xe/xe_guc_ads.c          |   5 +-
>  drivers/gpu/drm/xe/xe_guc_submit.c       |   2 +-
>  drivers/gpu/drm/xe/xe_hw_engine.c        |  11 ++
>  drivers/gpu/drm/xe/xe_hw_engine_types.h  |   4 +
>  drivers/gpu/drm/xe/xe_lrc.c              | 187 +++++++++++++++++++----
>  drivers/gpu/drm/xe/xe_lrc.h              |   5 +-
>  drivers/gpu/drm/xe/xe_lrc_types.h        |   4 +
>  drivers/gpu/drm/xe/xe_pci.c              |   3 +
>  drivers/gpu/drm/xe/xe_pci_types.h        |   3 +
>  14 files changed, 220 insertions(+), 39 deletions(-)
> 
> -- 
> 2.43.0
> 

  parent reply	other threads:[~2024-05-06 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04 23:29 [PATCH 0/4] drm/xe: Add Indirect Ring State support Niranjana Vishwanathapura
2024-05-04 23:29 ` [PATCH 1/4] drm/xe: Minor cleanup in LRC handling Niranjana Vishwanathapura
2024-05-04 23:29 ` [PATCH 2/4] drm/xe: Add Indirect Ring State support Niranjana Vishwanathapura
2024-05-04 23:29 ` [PATCH 3/4] drm/xe: Dump Indirect Ring State registers Niranjana Vishwanathapura
2024-05-04 23:29 ` [PATCH 4/4] drm/xe/xe2: Enable Indirect Ring State support for Xe2 Niranjana Vishwanathapura
2024-05-05  0:07 ` ✗ Fi.CI.BAT: failure for drm/xe: Add Indirect Ring State support (rev2) Patchwork
2024-05-06 12:35 ` Rodrigo Vivi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-04 23:15 [PATCH 0/4] drm/xe: Add Indirect Ring State support Niranjana Vishwanathapura

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=ZjjOdrmCgpQfkiYi@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=niranjana.vishwanathapura@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 read-only IMAP folder(s) and NNTP newsgroup(s).