From: Thomas Gleixner <tglx@kernel.org>
To: Keith Busch <kbusch@kernel.org>
Cc: Keith Busch <kbusch@meta.com>,
bhelgaas@google.com, maz@kernel.org, lrizzo@google.com,
hch@lst.de, changfengnan@bytedance.com,
namjain@linux.microsoft.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org,
Vidya Sagar <vidyas@nvidia.com>
Subject: Re: [PATCH v3 2/2] PCI/MSI: Implement irq_mask_noflush() for MSI-X
Date: Wed, 11 Nov 2026 00:41:37 +0100 [thread overview]
Message-ID: <87o6bwtfta.ffs@fw13> (raw)
In-Reply-To: <avHxSog2_rsJKGUy@kbusch-mbp>
On Mon, Nov 09 2026 at 09:14, Keith Busch wrote:
> On Sat, Nov 07, 2026 at 10:53:47PM +0100, Thomas Gleixner wrote:
>> On Sat, Nov 07 2026 at 13:00, Keith Busch wrote:
>> > This is done on purpose: pci_msix_write_vector_ctrl() already has the
>> > same offline check, so nothing actually gets written, same as before.
>> >
>> > And regardless of whether it's offline or not, we have to set the
>> > PCI_MSIX_ENTRY_CTRL_MASKBIT in the cached msxi_ctrl. That's common to
>> > both paths, so it lives in the noflush helper to avoid duplicating it.
>>
>> Indeed, but that's an unreadable mess TBH.
>
> No disagreement there! I was just going for a minimal diff, but we can
> refactor a bit on the way. I'll take a stab at it.
Yes, please. The minimal diff approch is what creates the most problems
down the road.
> I also don't really get the rationale for putting the check in
> write_vector. The commit message says the checks are to avoid having to
> deal with errors, but posted writes don't produce errors, so not sure
> what it's actually guarding against.
To me the explaination made sense and there were no objections within
month from any of the people involved. I'm not a DPC (or whatever is
involved) expert. I just work here.
I've Cc'ed the author of the patch for you as that might be a better way
to answer your question, no?
Thanks,
tglx
prev parent reply other threads:[~2026-11-10 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:34 [PATCH v3 0/2] genirq, PCI/MSI: mask without flushing Keith Busch
2026-11-06 17:34 ` [PATCH v3 1/2] genirq: Add disable_irq_noflush() Keith Busch
2026-11-06 17:48 ` sashiko-bot
2026-11-06 17:34 ` [PATCH v3 2/2] PCI/MSI: Implement irq_mask_noflush() for MSI-X Keith Busch
2026-11-06 17:47 ` sashiko-bot
2026-11-06 20:53 ` Thomas Gleixner
2026-11-07 20:00 ` Keith Busch
2026-11-07 21:53 ` Thomas Gleixner
2026-11-09 16:14 ` Keith Busch
2026-11-10 23:41 ` Thomas Gleixner [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=87o6bwtfta.ffs@fw13 \
--to=tglx@kernel.org \
--cc=bhelgaas@google.com \
--cc=changfengnan@bytedance.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lrizzo@google.com \
--cc=maz@kernel.org \
--cc=namjain@linux.microsoft.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.