public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Ming <ming.li@zohomail.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: rafael@kernel.org, bp@alien8.de, dan.j.williams@intel.com,
	tony.luck@intel.com, dave@stgolabs.net,
	jonathan.cameron@huawei.com, alison.schofield@intel.com,
	ira.weiny@intel.com, linux-cxl@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v4 4/4] cxl: Add mce notifier to emit aliased address for extended linear cache
Date: Tue, 25 Feb 2025 22:11:44 +0800	[thread overview]
Message-ID: <3bff8405-d970-4e2d-b630-e84ed702359b@zohomail.com> (raw)
In-Reply-To: <20250224182202.1683380-5-dave.jiang@intel.com>

On 2/25/2025 2:21 AM, Dave Jiang wrote:
> Below is a setup with extended linear cache configuration with an example
> layout of memory region shown below presented as a single memory region
> consists of 256G memory where there's 128G of DRAM and 128G of CXL memory.
> The kernel sees a region of total 256G of system memory.
>
>               128G DRAM                          128G CXL memory
> |-----------------------------------|-------------------------------------|
>
> Data resides in either DRAM or far memory (FM) with no replication. Hot
> data is swapped into DRAM by the hardware behind the scenes. When error is
> detected in one location, it is possible that error also resides in the
> aliased location. Therefore when a memory location that is flagged by MCE
> is part of the special region, the aliased memory location needs to be
> offlined as well.
>
> Add an mce notify callback to identify if the MCE address location is part
> of an extended linear cache region and handle accordingly.
>
> Added symbol export to set_mce_nospec() in x86 code in order to call
> set_mce_nospec() from the CXL MCE notify callback.
>
> Link: https://lore.kernel.org/linux-cxl/668333b17e4b2_5639294fd@dwillia2-xfh.jf.intel.com.notmuch/
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Reviewed-by: Li Ming <ming.li@zohomail.com>

      reply	other threads:[~2025-02-25 14:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 18:20 [PATCH v4 0/4] acpi/hmat / cxl: Add exclusive caching enumeration and RAS support Dave Jiang
2025-02-24 18:20 ` [PATCH v4 1/4] acpi: numa: Add support to enumerate and store extended linear address mode Dave Jiang
2025-02-25 14:09   ` Li Ming
2025-02-24 18:21 ` [PATCH v4 2/4] acpi/hmat / cxl: Add extended linear cache support for CXL Dave Jiang
2025-02-25 14:10   ` Li Ming
2025-02-25 20:00   ` Alison Schofield
2025-02-25 20:35     ` Dave Jiang
2025-02-25 20:11   ` Alison Schofield
2025-02-24 18:21 ` [PATCH v4 3/4] cxl: Add extended linear cache address alias emission for cxl events Dave Jiang
2025-02-25 14:10   ` Li Ming
2025-02-25 20:34   ` Alison Schofield
2025-02-24 18:21 ` [PATCH v4 4/4] cxl: Add mce notifier to emit aliased address for extended linear cache Dave Jiang
2025-02-25 14:11   ` Li Ming [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=3bff8405-d970-4e2d-b630-e84ed702359b@zohomail.com \
    --to=ming.li@zohomail.com \
    --cc=alison.schofield@intel.com \
    --cc=bp@alien8.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=tony.luck@intel.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