linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Ruidong Tian <tianruidong@linux.alibaba.com>
Cc: yazen.ghannam@amd.com, baolin.wang@linux.alibaba.com,
	bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, tglx@linutronix.de, tony.luck@intel.com,
	x86@kernel.org, xueshuai@linux.alibaba.com
Subject: Re: [PATCH] x86/mce/amd: init mce severity to handle deferred memory failure
Date: Thu, 18 Apr 2024 09:23:07 -0400	[thread overview]
Message-ID: <36a20694-de04-41fa-a637-1de0a4aa5da4@amd.com> (raw)
In-Reply-To: <9f9b0af3-669e-493b-9a26-475115410435@linux.alibaba.com>

On 4/18/24 04:42, Ruidong Tian wrote:
> 
> AMD ATL has merged to upstream, can we merge this patch to process 
> deferred error with memory_failure()?
>

Hi Ruidong,

Thanks for the follow up.

This patch is made redundant by the following patch in review.
https://lore.kernel.org/linux-edac/20240404151359.47970-11-yazen.ghannam@amd.com/

Also, this is still not sufficient. The address translation still needs
to be invoked in order for memory_failure() to have a valid system
physical address.

Please see the following work-in-progress patch.
https://github.com/AMDESE/linux/commit/6ddd8e90d08edb4a2730ccd02981baef4645bb43

Thanks,
Yazen

      reply	other threads:[~2024-04-18 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 12:18 [PATCH] x86/mce/amd: init mce severity to handle deferred memory failure Shuai Xue
2023-05-09 14:25 ` Yazen Ghannam
2023-05-10  2:17   ` Shuai Xue
2023-05-10 13:59     ` Yazen Ghannam
2024-04-18  8:42       ` Ruidong Tian
2024-04-18 13:23         ` Yazen Ghannam [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=36a20694-de04-41fa-a637-1de0a4aa5da4@amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tianruidong@linux.alibaba.com \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=xueshuai@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).