From: Thomas Gleixner <tglx@linutronix.de>
To: Luigi Rizzo <lrizzo@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, stable@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>
Subject: Re: [patch 1/3] x86/msi: Make irq_retrigger() functional for posted MSI
Date: Tue, 25 Nov 2025 20:04:31 +0100 [thread overview]
Message-ID: <87ldjugchs.ffs@tglx> (raw)
In-Reply-To: <CAMOZA0LB1UEEib1WWpUW0X-5+LKx28Ko9eGLi5ZSvU8d2yXkBQ@mail.gmail.com>
On Tue, Nov 25 2025 at 18:54, Luigi Rizzo wrote:
> On Tue, Nov 25, 2025 at 11:20 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> Luigi reported that retriggering a posted MSI interrupt does not work
>> correctly.
>> [...]
>>
>> So instead of playing games with the PIR, this can be actually solved
>> for both cases by:
>>
>> 1) Keeping track of the posted interrupt vector handler state
>
> Tangential comment, but I see that this patch uses this_cpu_read()/write()
> whereas the rest of the file uses __this_cpu_read()/write()
You're right. I've missed that. Let me redo it.
next prev parent reply other threads:[~2025-11-25 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 10:20 [patch 0/3] x86/irq: Bugfix and cleanup for posted MSI interrupts Thomas Gleixner
2025-11-25 10:20 ` [patch 1/3] x86/msi: Make irq_retrigger() functional for posted MSI Thomas Gleixner
2025-11-25 17:54 ` Luigi Rizzo
2025-11-25 19:04 ` Thomas Gleixner [this message]
2025-11-25 10:20 ` [patch 2/3] x86/irq: Cleanup posted MSI code Thomas Gleixner
2025-11-25 10:20 ` [patch 3/3] x86/irq_remapping: Sanitize posted_msi_supported() Thomas Gleixner
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=87ldjugchs.ffs@tglx \
--to=tglx@linutronix.de \
--cc=baolu.lu@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrizzo@google.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
/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.