mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vijay Balakrishna <vijayb@linux.microsoft.com>
To: "Tyler Hicks (Microsoft)" <code@tyhicks.com>
Cc: Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
	James Morse <james.morse@arm.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Robert Richter <rric@kernel.org>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	Marc Zyngier <maz@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/2] drivers/edac: Add L1 and L2 error detection for A53, A57 and A72
Date: Thu, 10 Apr 2025 15:27:18 -0700	[thread overview]
Message-ID: <eff8d726-d25e-4424-846f-fd3cfa249315@linux.microsoft.com> (raw)
In-Reply-To: <Z/gkWCiveESbvdxS@redbud>

On 4/10/2025 1:04 PM, Tyler Hicks (Microsoft) wrote:
>> +		snprintf(msg, MESSAGE_SIZE, "%s %s error(s) on CPU %d",
>> +			 str, fatal ? "fatal" : "correctable", cpu);
>> +
>> +		if (fatal)
>> +			edac_device_handle_ue(edac_ctl, cpu, 0, msg);
>> +		else
>> +			edac_device_handle_ce(edac_ctl, cpu, 0, msg);
>> +
>> +		write_sysreg_s(0, SYS_CPUMERRSR_EL1);
>> +		isb();
> I think the register writes and barriers should happen much closer to the
> register reads, in read_errors(). Looking back at Marc's feedback on v5, I
> think his most important piece of feedback was to only clear the register when
> the valid bit is set to avoid accidentally clobbering an error that came in
> between the register read and write.
> 
> By moving the register writes into report_errors() in this v6 series, there's
> now a much larger window where new errors could occur between the register
> read and the register write. Those new errors would be silently lost/ignored.
> Reducing the window to the least number of cycles seems important for accurate
> reporting.

Moving clear to report_errors() is wrong actually, it has be cleared 
from the CPU, from read_errors() which is a SMP call. Let me share new 
version with changes.

Thanks,
Vijay

  reply	other threads:[~2025-04-10 22:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 23:36 [PATCH v6 0/2] " Vijay Balakrishna
2025-04-09 23:36 ` [PATCH 1/2] drivers/edac: " Vijay Balakrishna
2025-04-10 20:04   ` Tyler Hicks (Microsoft)
2025-04-10 22:27     ` Vijay Balakrishna [this message]
2025-04-10 22:29     ` Vijay Balakrishna
2025-04-09 23:36 ` [PATCH 2/2] dt-bindings: arm: cpus: Add edac-enabled property Vijay Balakrishna
2025-04-10  6:00   ` Krzysztof Kozlowski
2025-04-10  7:10     ` Marc Zyngier
2025-04-10 14:30       ` Tyler Hicks (Microsoft)
2025-04-10 16:23         ` Marc Zyngier
2025-04-10 16:42           ` Tyler Hicks (Microsoft)
2025-04-11 20:02           ` Borislav Petkov
2025-04-13 10:38             ` Marc Zyngier
2025-04-11 22:08 [v7 PATCH 0/2] Add L1 and L2 error detection for A53, A57 and A72 Vijay Balakrishna
2025-04-11 22:08 ` [PATCH 1/2] drivers/edac: " Vijay Balakrishna
2025-05-05  0:27 [v8 PATCH 0/2] " Vijay Balakrishna
2025-05-05  0:27 ` [PATCH 1/2] drivers/edac: " Vijay Balakrishna

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=eff8d726-d25e-4424-846f-fd3cfa249315@linux.microsoft.com \
    --to=vijayb@linux.microsoft.com \
    --cc=bp@alien8.de \
    --cc=code@tyhicks.com \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rric@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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

all inboxes | Powered by JetHome®