From: "Luck, Tony" <tony.luck@intel.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"lenb@kernel.org" <lenb@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"bp@alien8.de" <bp@alien8.de>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"graeme.gregory@linaro.org" <graeme.gregory@linaro.org>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"myron.stowe@redhat.com" <myron.stowe@redhat.com>,
"Brown, Len" <len.brown@intel.com>,
"Huang, Ying" <ying.huang@intel.com>
Subject: RE: [BUG] kernel side can NOT trigger memory error with einj
Date: Thu, 17 Mar 2022 16:57:41 +0000 [thread overview]
Message-ID: <1421c3ac3d3c4438a6ff18f193f8a41c@intel.com> (raw)
In-Reply-To: <f93a5532-3e07-edf4-38ca-142a0f1d78d7@linux.alibaba.com>
> - rc = apei_exec_run(&trigger_ctx, ACPI_EINJ_TRIGGER_ERROR);
> + ptr = kmap(pfn_to_page(pfn));
> + tmp = *(ptr + (param1 & ~ PAGE_MASK));
That hack works when the trigger action is just trying to access the injected
location. But on Intel platforms the trigger "kicks" the patrol scrubber in the
memory controller to access the address. So the error is triggered not by
an access from the core, but by internal memory controller access.
This results in a different error signature (for an uncorrected error injection
it will be a UCNA or SRAO in Intel acronym-speak).
-Tony
next prev parent reply other threads:[~2022-03-17 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 5:19 [BUG] kernel side can NOT trigger memory error with einj Shuai Xue
2022-03-16 17:29 ` Luck, Tony
2022-03-17 2:56 ` Shuai Xue
2022-03-17 16:57 ` Luck, Tony [this message]
2022-03-20 13:11 ` Shuai Xue
2022-03-21 2:43 ` Huang, Ying
2022-03-22 3:36 ` Shuai Xue
2022-03-21 15:54 ` Luck, Tony
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=1421c3ac3d3c4438a6ff18f193f8a41c@intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=graeme.gregory@linaro.org \
--cc=james.morse@arm.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myron.stowe@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=will.deacon@arm.com \
--cc=xueshuai@linux.alibaba.com \
--cc=ying.huang@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;
as well as URLs for NNTP newsgroup(s).