From: Vasily Averin <vvs@openvz.org>
To: Dave Hansen <dave.hansen@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: kernel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>,
steve.sipes@comandsolutions.com, x86@kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: "Bad pagetable: 000c" crashes and errata "Not-Present Page Faults May Set the RSVD Flag in the Error Code"
Date: Mon, 20 Jun 2022 11:00:55 +0300 [thread overview]
Message-ID: <9bc8de5f-fd80-57fe-0169-0ec942638299@openvz.org> (raw)
In-Reply-To: <04db74ce-4e43-1edb-34e6-ca162f483680@intel.com>
On 6/20/22 10:18, Dave Hansen wrote:
> On 6/19/22 22:29, Vasily Averin wrote:
>> Some (old?) Intel CPU's have errata:
>> "Not-Present Page Faults May Set the RSVD Flag in the Error Code
>
> Do you happen to have a link to the actual erratum document? It's
> usually a "Specification Update" for some model or another.
For Intel Xeon E5400 used on affected node:
https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5400-spec-update.pdf
Intel® Xeon® Processor 5400 Series
Specification Update
August 2013
Document Number: 318585-021
page 39
AX74. Not-Present Page Faults May Set the RSVD Flag in the Error Cod
Later I've found similar articles for another processors too.
Thank you,
Vasily Averin
next prev parent reply other threads:[~2022-06-20 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 5:29 "Bad pagetable: 000c" crashes and errata "Not-Present Page Faults May Set the RSVD Flag in the Error Code" Vasily Averin
2022-06-20 7:18 ` Dave Hansen
2022-06-20 8:00 ` Vasily Averin [this message]
2022-06-30 5:58 ` [PATCH] x86/fault: ignore RSVD flag in error code if P flag is 0 Vasily Averin
2022-06-30 14:22 ` Dave Hansen
2022-06-30 23:58 ` [PATCH v2] " Vasily Averin
2022-07-01 0:42 ` [PATCH] " H. Peter Anvin
2022-07-01 4:56 ` Vasily Averin
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=9bc8de5f-fd80-57fe-0169-0ec942638299@openvz.org \
--to=vvs@openvz.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel@openvz.org \
--cc=khorenko@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=steve.sipes@comandsolutions.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).