From: Thomas Gleixner <tglx@linutronix.de>
To: Vidya Sagar <vidyas@nvidia.com>,
bhelgaas@google.com, rdunlap@infradead.org,
ilpo.jarvinen@linux.intel.com, jiang.liu@linux.intel.com
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 V3] PCI/MSI: Fix MSI hwirq truncation
Date: Mon, 15 Jan 2024 11:01:15 +0100 [thread overview]
Message-ID: <877ckahq50.ffs@tglx> (raw)
In-Reply-To: <b9a7b855-af2b-4858-b9d8-3340a0421cfe@nvidia.com>
On Fri, Jan 12 2024 at 23:03, Vidya Sagar wrote:
> On 1/12/2024 9:23 PM, Thomas Gleixner wrote:
>> On Thu, Jan 11 2024 at 10:58, Vidya Sagar wrote:
>>> So, cast the PCI domain number to 'irq_hw_number_t' before left shifting
>>> it to calculate hwirq number.
>>
>> This still does not explain that this fixes it only on 64-bit platforms
>> and why we don't care for 32-bit systems.
> Agree that this fixes the issue only on 64-bit platforms. It doesn't
> change the behavior on 32-bit platforms. My understanding is that the
> issue surfaces only if there are too many PCIe controllers in the system
> which usually is the case in modern server systems and it is arguable if
> the server systems really run 32-bit kernels.
Arguably people who do that can keep the pieces.
> One way to fix it for both 32-bit and 64-bit systems is by changing the
> type of 'hwirq' to u64. This may cause two memory reads in 32-bit
> systems whenever 'hwirq' is accessed and that may intern cause some perf
> impact?? Is this the way you think I should be handling it?
No. Leave it as is. What I'm asking for is that it's properly documented
in the changelog.
Thanks,
tglx
next prev parent reply other threads:[~2024-01-15 10:01 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
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 [this message]
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=877ckahq50.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jiang.liu@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.