All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Anthony PERARD <anthony.perard@vates.tech>,
	Michal Orzel <michal.orzel@amd.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 0/5] xen/x86: prevent local APIC errors at shutdown
Date: Tue, 11 Feb 2025 09:50:27 +0100	[thread overview]
Message-ID: <Z6sPU2y7qHMjAZ30@macbook.local> (raw)
In-Reply-To: <c9b8ae2c-ed90-4256-8a61-19ed85b1a774@suse.com>

On Tue, Feb 11, 2025 at 07:39:12AM +0100, Jan Beulich wrote:
> On 06.02.2025 16:06, Roger Pau Monne wrote:
> > The following series aims to prevent local APIC errors from stalling the
> > shtudown process.  On XenServer testing we have seen reports of AMD
> > boxes sporadically getting stuck in a spam of:
> > 
> > APIC error on CPU0: 00(08), Receive accept error
> > 
> > Messages during shutdown, as a result of device interrupts targeting
> > CPUs that are offline (and have the local APIC disabled).
> 
> One more thought here: Have you/we perhaps discovered the reason why there
> was that 1ms delay at the end of fixup_irqs() that was badly commented,
> and that you removed in e2bb28d62158 ("x86/irq: forward pending interrupts
> to new destination in fixup_irqs()")? May be worth mentioning that by way
> of a Fixes: tag.

Hm, so you think the delay was added there as a way to ensure any
pending interrupts would get drained (ie: serviced) on the old target?

I'm maybe a bit confused, but I don't think the delay would help much
with preventing the local APIC errors?  Regardless of the wait, if the
interrupts target offline CPUs there's a chance receive accept errors
will be triggered on AMD.

Thanks, Roger.


  reply	other threads:[~2025-02-11  8:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 15:06 [PATCH v2 0/5] xen/x86: prevent local APIC errors at shutdown Roger Pau Monne
2025-02-06 15:06 ` [PATCH v2 1/5] x86/shutdown: offline APs with interrupts disabled on all CPUs Roger Pau Monne
2025-02-10 10:20   ` Jan Beulich
2025-02-10 10:46     ` Roger Pau Monné
2025-02-10 11:09       ` Jan Beulich
2025-02-06 15:06 ` [PATCH v2 2/5] x86/irq: drop fixup_irqs() parameters Roger Pau Monne
2025-02-06 15:06 ` [PATCH v2 3/5] x86/smp: perform disabling on interrupts ahead of AP shutdown Roger Pau Monne
2025-02-10 10:24   ` Jan Beulich
2025-02-10 10:47     ` Roger Pau Monné
2025-02-06 15:06 ` [PATCH v2 4/5] x86/pci: disable MSI(-X) on all devices at shutdown Roger Pau Monne
2025-02-10 10:41   ` Jan Beulich
2025-02-06 15:06 ` [PATCH v2 5/5] x86/iommu: disable interrupts " Roger Pau Monne
2025-02-10 11:04   ` Jan Beulich
2025-02-10 10:02 ` [PATCH for-4.20? v2 0/5] xen/x86: prevent local APIC errors " Roger Pau Monné
2025-02-10 18:29   ` Oleksii Kurochko
2025-02-11  8:38     ` Roger Pau Monné
2025-02-11  9:26       ` Jan Beulich
2025-02-11  6:39 ` [PATCH " Jan Beulich
2025-02-11  8:50   ` Roger Pau Monné [this message]
2025-02-11  9:20     ` Jan Beulich

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=Z6sPU2y7qHMjAZ30@macbook.local \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.