From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Ashok Raj <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Cc: Sukumar Ghorai <sukumar.ghorai@intel.com>,
Srikanth Nandamuri <srikanth.nandamuri@intel.com>,
Evan Green <evgreen@chromium.org>,
Bjorn Helgaas <bhelgaas@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/hotplug: Silence APIC only after all irq's are migrated
Date: Thu, 20 Aug 2020 15:11:45 +0300 [thread overview]
Message-ID: <563d77c0-ab5b-df9c-8f4d-b16a0d1211a2@linux.intel.com> (raw)
In-Reply-To: <20200814213842.31151-1-ashok.raj@intel.com>
On 15.8.2020 0.38, Ashok Raj wrote:
> When offlining CPU's, fixup_irqs() migrates all interrupts away from the
> outgoing CPU to an online CPU. Its always possible the device sent an
> interrupt to the previous CPU destination. Pending interrupt bit in IRR in
> lapic identifies such interrupts. apic_soft_disable() will not capture any
> new interrupts in IRR. This causes interrupts from device to be lost during
> cpu offline. The issue was found when explicitly setting MSI affinity to a
> CPU and immediately offlining it. It was simple to recreate with a USB
> ethernet device and doing I/O to it while the CPU is offlined. Lost
> interrupts happen even when Interrupt Remapping is enabled.
>
> Current code does apic_soft_disable() before migrating interrupts.
>
> native_cpu_disable()
> {
> ...
> apic_soft_disable();
> cpu_disable_common();
> --> fixup_irqs(); // Too late to capture anything in IRR.
> }
>
> Just fliping the above call sequence seems to hit the IRR checks
> and the lost interrupt is fixed for both legacy MSI and when
> interrupt remapping is enabled.
>
>
> Fixes: 60dcaad5736f ("x86/hotplug: Silence APIC and NMI when CPU is dead")
> Link: https://lore.kernel.org/lkml/875zdarr4h.fsf@nanos.tec.linutronix.de/
> Signed-off-by: Ashok Raj <ashok.raj@intel.com>
>
> To: linux-kernel@vger.kernel.org
> To: Thomas Gleixner <tglx@linutronix.de>
> Cc: Sukumar Ghorai <sukumar.ghorai@intel.com>
> Cc: Srikanth Nandamuri <srikanth.nandamuri@intel.com>
> Cc: Evan Green <evgreen@chromium.org>
> Cc: Mathias Nyman <mathias.nyman@linux.intel.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: stable@vger.kernel.org
> ---
This fixes the lost xhci interrupt for me.
Before this patch a msi interupt was lost after ~200 cycles of toggling CPUs
offline/online under heavy usb traffic.
With this patch I ran 3x2000 cycles without any issues (Comet lake, patch on top of 5.8)
Tried both with and without CONFIG_IRQ_REMAP. No issues seen.
Tested-by: Mathias Nyman <mathias.nyman@linux.intel.com>
prev parent reply other threads:[~2020-08-20 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 21:38 [PATCH] x86/hotplug: Silence APIC only after all irq's are migrated Ashok Raj
2020-08-14 23:25 ` Randy Dunlap
2020-08-15 5:58 ` Raj, Ashok
2020-08-15 19:53 ` Raj, Ashok
2020-08-17 18:12 ` Evan Green
2020-08-17 18:33 ` Raj, Ashok
2020-08-20 18:21 ` Evan Green
2020-08-20 19:58 ` Raj, Ashok
2020-08-20 12:11 ` Mathias Nyman [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=563d77c0-ab5b-df9c-8f4d-b16a0d1211a2@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=evgreen@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srikanth.nandamuri@intel.com \
--cc=stable@vger.kernel.org \
--cc=sukumar.ghorai@intel.com \
--cc=tglx@linutronix.de \
/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