Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Ilia Levi <illevi@habana.ai>, intel-xe@lists.freedesktop.org
Cc: ilia.levi@intel.com, jonathan.cavitt@intel.com,
	niranjana.vishwanathapura@intel.com, koby.elbaz@intel.com,
	yaron.avizrat@intel.com
Subject: Re: [PATCH v4 0/3] memirq infra changes
Date: Sat, 14 Sep 2024 16:12:26 +0200	[thread overview]
Message-ID: <78097dfa-a869-4465-afc5-77a3592c918f@intel.com> (raw)
In-Reply-To: <20240912085438.737015-1-illevi@habana.ai>



On 12.09.2024 10:54, Ilia Levi wrote:
> From: Ilia Levi <ilia.levi@intel.com>
> 
> This patch set contains Memory Based Interrupts (memirq) infrastructure
> changes to make it reusable for use cases other than VF 
> (specifically MSI-X). 
> 
> The main changes are separation from VF and a new mode where hardware
> engines report interrupt source and status to the offset of instance 0
> (for MSI-X support).
> 
> v2: Rebase
> v3: Rebase, refactor according to review comments (Michal)
> v4: Rebase, address review comments (Michal)
> 
> Ilia Levi (3):
>   drm/xe: move memirq out of VF

can we split above patch into:

	drm/xe: Introduce dedicated config for MEMIRQ debug
	drm/xe: Introduce xe_device_uses_memirq()
	drm/xe: Move memirq out of VF
and maybe
	drm/xe: Prepare to handle memirq outside VF

>   drm/xe: memirq infra changes for MSI-X
>   drm/xe: memirq handler changes
> 
>  drivers/gpu/drm/xe/Kconfig.debug     |  12 ++
>  drivers/gpu/drm/xe/xe_device.c       |   8 +-
>  drivers/gpu/drm/xe/xe_device.h       |  13 +++
>  drivers/gpu/drm/xe/xe_device_types.h |   6 +-
>  drivers/gpu/drm/xe/xe_guc.c          |   2 +-
>  drivers/gpu/drm/xe/xe_hw_engine.c    |  19 +++-
>  drivers/gpu/drm/xe/xe_irq.c          |  40 ++++---
>  drivers/gpu/drm/xe/xe_lrc.c          |   8 +-
>  drivers/gpu/drm/xe/xe_memirq.c       | 157 +++++++++++++++++----------
>  drivers/gpu/drm/xe/xe_memirq.h       |   6 +-
>  drivers/gpu/drm/xe/xe_memirq_types.h |   4 +-
>  11 files changed, 182 insertions(+), 93 deletions(-)
> 

      parent reply	other threads:[~2024-09-14 14:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  8:54 [PATCH v4 0/3] memirq infra changes Ilia Levi
2024-09-12  8:54 ` [PATCH v4 1/3] drm/xe: move memirq out of VF Ilia Levi
2024-09-14 13:37   ` Michal Wajdeczko
2024-09-17 11:28     ` Ilia Levi
2024-09-12  8:54 ` [PATCH v4 2/3] drm/xe: memirq infra changes for MSI-X Ilia Levi
2024-09-14 13:48   ` Michal Wajdeczko
2024-09-12  8:54 ` [PATCH v4 3/3] drm/xe: memirq handler changes Ilia Levi
2024-09-13 20:43   ` Rodrigo Vivi
2024-09-14 14:07   ` Michal Wajdeczko
2024-09-12  9:09 ` ✓ CI.Patch_applied: success for memirq infra changes (rev5) Patchwork
2024-09-12  9:10 ` ✓ CI.checkpatch: " Patchwork
2024-09-12  9:26 ` ✓ CI.KUnit: " Patchwork
2024-09-12  9:45 ` ✓ CI.Build: " Patchwork
2024-09-12  9:48 ` ✓ CI.Hooks: " Patchwork
2024-09-12  9:49 ` ✓ CI.checksparse: " Patchwork
2024-09-12 10:32 ` ✓ CI.BAT: " Patchwork
2024-09-12 17:51 ` ✗ CI.FULL: failure " Patchwork
2024-09-14 14:12 ` Michal Wajdeczko [this message]

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=78097dfa-a869-4465-afc5-77a3592c918f@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=ilia.levi@intel.com \
    --cc=illevi@habana.ai \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=koby.elbaz@intel.com \
    --cc=niranjana.vishwanathapura@intel.com \
    --cc=yaron.avizrat@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