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,
koby.elbaz@intel.com, yaron.avizrat@intel.com
Subject: Re: [PATCH v5 3/5] drm/xe: move memirq out of VF
Date: Tue, 17 Sep 2024 22:14:36 +0200 [thread overview]
Message-ID: <5509c3ea-7997-4125-9b3b-a7737deb41f3@intel.com> (raw)
In-Reply-To: <20240917112307.1242329-4-illevi@habana.ai>
On 17.09.2024 13:23, Ilia Levi wrote:
> From: Ilia Levi <ilia.levi@intel.com>
>
> Up until now only VF used Memory Based Interrupts (memirq).
> Moving it out of VF to cater for other usages, specifically MSI-X.
>
> Signed-off-by: Ilia Levi <ilia.levi@intel.com>
> ---
...
> diff --git a/drivers/gpu/drm/xe/xe_memirq.c b/drivers/gpu/drm/xe/xe_memirq.c
> index 464cb9d7fee2..8b12209d995a 100644
> --- a/drivers/gpu/drm/xe/xe_memirq.c
> +++ b/drivers/gpu/drm/xe/xe_memirq.c
> @@ -19,15 +19,25 @@
> #include "xe_hw_engine.h"
> #include "xe_map.h"
> #include "xe_memirq.h"
> -#include "xe_sriov.h"
> -#include "xe_sriov_printk.h"
>
> #define memirq_assert(m, condition) xe_tile_assert(memirq_to_tile(m), condition)
> -#define memirq_debug(m, msg...) xe_sriov_dbg_verbose(memirq_to_xe(m), "MEMIRQ: " msg)
> +#define memirq_printk(m, _level, _fmt, ...) \
> + drm_##_level(&memirq_to_xe(m)->drm, "MEMIRQ%u: " _fmt, \
> + memirq_to_tile(m)->id, ##__VA_ARGS__)
> +
> +#ifdef CONFIG_DRM_XE_DEBUG_MEMIRQ
> +#define memirq_debug(m, _fmt, ...) memirq_printk(m, dbg, _fmt, ##__VA_ARGS__)
> +#else
> +#define memirq_debug(...)
> +#endif
> +
> +#define memirq_err(m, _fmt, ...) memirq_printk(m, err, _fmt, ##__VA_ARGS__)
> +#define memirq_err_ratelimited(m, _fmt, ...) \
> + memirq_printk(m, err_ratelimited, _fmt, ##__VA_ARGS__)
>
with memirq_dbg() changes moved to patch 1/5
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
next prev parent reply other threads:[~2024-09-17 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 11:23 [PATCH v5 0/5] memirq infra changes Ilia Levi
2024-09-17 11:23 ` [PATCH v5 1/5] drm/xe: Introduce dedicated config for memirq debug Ilia Levi
2024-09-17 20:07 ` Michal Wajdeczko
2024-09-17 11:23 ` [PATCH v5 2/5] drm/xe: Introduce xe_device_uses_memirq() Ilia Levi
2024-09-17 19:16 ` Michal Wajdeczko
2024-09-17 11:23 ` [PATCH v5 3/5] drm/xe: move memirq out of VF Ilia Levi
2024-09-17 20:14 ` Michal Wajdeczko [this message]
2024-09-17 11:23 ` [PATCH v5 4/5] drm/xe: memirq infra changes for MSI-X Ilia Levi
2024-09-17 19:29 ` Michal Wajdeczko
2024-09-17 11:23 ` [PATCH v5 5/5] drm/xe: memirq handler changes Ilia Levi
2024-09-17 19:53 ` Michal Wajdeczko
2024-09-17 11:41 ` ✓ CI.Patch_applied: success for memirq infra changes (rev6) Patchwork
2024-09-17 11:42 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-17 11:43 ` ✓ CI.KUnit: success " Patchwork
2024-09-17 11:55 ` ✓ CI.Build: " Patchwork
2024-09-17 11:57 ` ✓ CI.Hooks: " Patchwork
2024-09-17 11:58 ` ✓ CI.checksparse: " Patchwork
2024-09-17 13:13 ` ✗ CI.BAT: failure " Patchwork
2024-09-17 15:16 ` ✗ CI.FULL: " 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=5509c3ea-7997-4125-9b3b-a7737deb41f3@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=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