Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vivekanandan, Balasubramani" <balasubramani.vivekanandan@intel.com>
To: Venkata Ramana Nayana <venkata.ramana.nayana@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/irq: Handle msix vector0 interrupt
Date: Mon, 3 Nov 2025 20:34:34 +0530	[thread overview]
Message-ID: <aQjEgu0IhQzSOIOE@bvivekan-mobl1> (raw)
In-Reply-To: <20251030151020.2042207-1-venkata.ramana.nayana@intel.com>

On 30.10.2025 20:40, Venkata Ramana Nayana wrote:
> Current gu2host handler registered as MSI-X vector 0 and as per bspec for
> an msix vector 0 interrupt, the driver must check the legacy registers
> 190008(TILE_INT_REG), 190060h (GT INTR Identity Reg 0) and other registers
> mentioned in "Interrupt Service Routine Pseudocode" otherwise it's block
> the next interrupts. To overcome this issue replacing guc2host handler
> with legacy xe_irq_handler.
> 
> Bspec: 62357
> Signed-off-by: Venkata Ramana Nayana <venkata.ramana.nayana@intel.com>

Please add the Fixes tag.

Fixes: da889070be7b2 ("drm/xe/irq: Separate MSI and MSI-X flows")

Few nitpicks

s/an msix/a msix
s/it's block/it will block

Rest looks good.

Reviewed-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>

Regards,
Bala

> ---
>  drivers/gpu/drm/xe/xe_irq.c | 18 +-----------------
>  1 file changed, 1 insertion(+), 17 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_irq.c b/drivers/gpu/drm/xe/xe_irq.c
> index e5ed0242f7b1..024e13e606ec 100644
> --- a/drivers/gpu/drm/xe/xe_irq.c
> +++ b/drivers/gpu/drm/xe/xe_irq.c
> @@ -897,22 +897,6 @@ static int xe_irq_msix_init(struct xe_device *xe)
>  	return 0;
>  }
>  
> -static irqreturn_t guc2host_irq_handler(int irq, void *arg)
> -{
> -	struct xe_device *xe = arg;
> -	struct xe_tile *tile;
> -	u8 id;
> -
> -	if (!atomic_read(&xe->irq.enabled))
> -		return IRQ_NONE;
> -
> -	for_each_tile(tile, xe, id)
> -		xe_guc_irq_handler(&tile->primary_gt->uc.guc,
> -				   GUC_INTR_GUC2HOST);
> -
> -	return IRQ_HANDLED;
> -}
> -
>  static irqreturn_t xe_irq_msix_default_hwe_handler(int irq, void *arg)
>  {
>  	unsigned int tile_id, gt_id;
> @@ -1029,7 +1013,7 @@ int xe_irq_msix_request_irqs(struct xe_device *xe)
>  	u16 msix;
>  
>  	msix = GUC2HOST_MSIX;
> -	err = xe_irq_msix_request_irq(xe, guc2host_irq_handler, xe,
> +	err = xe_irq_msix_request_irq(xe, xe_irq_handler(xe), xe,
>  				      DRIVER_NAME "-guc2host", false, &msix);
>  	if (err)
>  		return err;
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2025-11-03 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 15:10 [PATCH] drm/xe/irq: Handle msix vector0 interrupt Venkata Ramana Nayana
2025-10-30 15:22 ` ✓ CI.KUnit: success for " Patchwork
2025-10-30 16:18 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-30 18:55 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-03 15:04 ` Vivekanandan, Balasubramani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-07  8:31 [PATCH] " Venkata Ramana Nayana

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=aQjEgu0IhQzSOIOE@bvivekan-mobl1 \
    --to=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=venkata.ramana.nayana@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