public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Yazen Ghannam <yazen.ghannam@amd.com>, linux-edac@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com,
	x86@kernel.org, avadhut.naik@amd.com, john.allen@amd.com,
	boris.ostrovsky@oracle.com, Yazen Ghannam <yazen.ghannam@amd.com>
Subject: Re: [PATCH] x86/MCE: Prevent CPU offline for SMCA CPUs with non-core banks
Date: Sun, 25 Aug 2024 13:16:37 +0200	[thread overview]
Message-ID: <87jzg4g8dm.ffs@tglx> (raw)
In-Reply-To: <20240821140017.330105-1-yazen.ghannam@amd.com>

On Wed, Aug 21 2024 at 09:00, Yazen Ghannam wrote:
> Logical CPUs in AMD Scalable MCA (SMCA) systems can manage non-core
> banks. Each of these banks represents unique and separate hardware
> located within the system. Each bank is managed by a single logical CPU;
> they are not shared. Furthermore, the "CPU to MCA bank" assignment
> cannot be modified at run time.
>
> The MCE subsystem supports run time CPU hotplug. Many vendors have
> non-core MCA banks, so MCA settings are not cleared when a CPU is
> offlined for these vendors.
>
> Even though the non-core MCA banks remain enabled, MCA errors will not
> be handled (reported, cleared, etc.) on SMCA systems when the managing
> CPU is offline.
>
> Check if a CPU manages non-core MCA banks and, if so, prevent it from
> being taken offline.

Which in turn breaks hibernation and kexec...

Thanks,

        tglx



  parent reply	other threads:[~2024-08-25 11:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 14:00 [PATCH] x86/MCE: Prevent CPU offline for SMCA CPUs with non-core banks Yazen Ghannam
2024-08-21 18:35 ` boris.ostrovsky
2024-08-22 14:14   ` Yazen Ghannam
2024-08-25 11:16 ` Thomas Gleixner [this message]
2024-08-26 13:20   ` Yazen Ghannam
2024-08-27 12:50     ` Borislav Petkov
2024-08-27 13:47       ` Yazen Ghannam
2024-08-29  8:39         ` Borislav Petkov
2024-08-29 14:03           ` Yazen Ghannam
2024-08-29 14:14             ` Borislav Petkov
2024-08-29 14:18               ` Yazen Ghannam

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=87jzg4g8dm.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=avadhut.naik@amd.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=john.allen@amd.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=yazen.ghannam@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox