public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Vidya Sagar <vidyas@nvidia.com>,
	bhelgaas@google.com, rdunlap@infradead.org,
	ilpo.jarvinen@linux.intel.com, tglx@linutronix.de
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	treding@nvidia.com, jonathanh@nvidia.com, sdonthineni@nvidia.com,
	kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V1] PCI/MSI: Fix MSI hwirq truncation
Date: Fri, 5 Jan 2024 09:02:06 -0800	[thread overview]
Message-ID: <e529aafc-7d97-4e38-b994-26ce99f2715d@linux.intel.com> (raw)
In-Reply-To: <20240105134339.3091497-1-vidyas@nvidia.com>



On 1/5/2024 5:43 AM, Vidya Sagar wrote:
> While calculating the hwirq number for an MSI interrupt, the higher
> bits (i.e. from bit-5 onwards a.k.a domain_nr >= 32) of the PCI domain
> number gets truncated because of the shifted value casting to u32. This
> for example is resulting in same hwirq number for devices 0019:00:00.0
> and 0039:00:00.0.
> 
> So, cast the PCI domain number to u64 before left shifting it to
> calculate hwirq number.

This seems like a bug fix. Why not add Fixes: tag?

Is this issue detected in a platform test? Maybe including the relevant
details about it will help reproduce the issue.

> 
> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> ---
>  drivers/pci/msi/irqdomain.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/pci/msi/irqdomain.c b/drivers/pci/msi/irqdomain.c
> index c8be056c248d..cfd84a899c82 100644
> --- a/drivers/pci/msi/irqdomain.c
> +++ b/drivers/pci/msi/irqdomain.c
> @@ -61,7 +61,7 @@ static irq_hw_number_t pci_msi_domain_calc_hwirq(struct msi_desc *desc)
>  
>  	return (irq_hw_number_t)desc->msi_index |
>  		pci_dev_id(dev) << 11 |
> -		(pci_domain_nr(dev->bus) & 0xFFFFFFFF) << 27;
> +		((irq_hw_number_t)(pci_domain_nr(dev->bus) & 0xFFFFFFFF)) << 27;
>  }
>  
>  static void pci_msi_domain_set_desc(msi_alloc_info_t *arg,

-- 
Sathyanarayanan Kuppuswamy
Linux Kernel Developer

  reply	other threads:[~2024-01-05 17:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 13:43 [PATCH V1] PCI/MSI: Fix MSI hwirq truncation Vidya Sagar
2024-01-05 17:02 ` Kuppuswamy Sathyanarayanan [this message]
2024-01-08 11:58   ` Vidya Sagar
2024-01-08 12:05 ` [PATCH V2] " Vidya Sagar
2024-01-08 14:09   ` Shanker Donthineni
2024-01-10 10:12   ` Thomas Gleixner
2024-01-10 18:04     ` Vidya Sagar
2024-01-11  5:28   ` [PATCH V3] " Vidya Sagar
2024-01-12 15:53     ` Thomas Gleixner
2024-01-12 17:33       ` Vidya Sagar
2024-01-15 10:01         ` Thomas Gleixner
2024-01-15 13:50           ` Vidya Sagar
2024-01-15 13:56     ` [PATCH V4] " Vidya Sagar
2024-01-23 16:01       ` Vidya Sagar
2024-01-31  3:15         ` Vidya Sagar
2024-02-07  6:59           ` Vidya Sagar
2024-02-07 10:01             ` Thomas Gleixner
2024-02-19 15:21       ` [tip: irq/urgent] PCI/MSI: Prevent MSI hardware interrupt number truncation tip-bot2 for Vidya Sagar

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=e529aafc-7d97-4e38-b994-26ce99f2715d@linux.intel.com \
    --to=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jonathanh@nvidia.com \
    --cc=kthota@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=rdunlap@infradead.org \
    --cc=sagar.tv@gmail.com \
    --cc=sdonthineni@nvidia.com \
    --cc=tglx@linutronix.de \
    --cc=treding@nvidia.com \
    --cc=vidyas@nvidia.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