From: Dave Hansen <dave.hansen@intel.com>
To: Vasily Averin <vvs@openvz.org>,
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>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: kernel@openvz.org, linux-kernel@vger.kernel.org,
Konstantin Khorenko <khorenko@virtuozzo.com>,
steve.sipes@comandsolutions.com
Subject: Re: [PATCH] x86/fault: ignore RSVD flag in error code if P flag is 0
Date: Thu, 30 Jun 2022 07:22:08 -0700 [thread overview]
Message-ID: <3e39adad-3b1d-18c0-29d5-e0268c0fa083@intel.com> (raw)
In-Reply-To: <85bd8614-9a55-3113-e5a8-b7e73f636135@openvz.org>
On 6/29/22 22:58, Vasily Averin wrote:
> Some older Intel CPUs have errata:
> "Not-Present Page Faults May Set the RSVD Flag in the Error Code
Please include a link to the documentation when you cite things like
this. For example, this is very helpful:
Several older Intel CPUs have this or a similar erratum. For
instance, the "Intel Xeon Processor 5400 Series Specification
Update" has "AX74 ... Not-Present Page Faults May Set the RSVD
Flag in the Error Code".
https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-5400-spec-update.pdf
That makes it a *LOT* easier to find the actual erratum and its text. I
honestly also woudln't mind if you just copy a chunk of the problem text
verbatim into the changelog. Intel does have a habit of updating text
in documents like that and it's quite handy to have a snapshot of what
you were reading when you wrote the patch.
next prev parent reply other threads:[~2022-06-30 14:35 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
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 [this message]
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=3e39adad-3b1d-18c0-29d5-e0268c0fa083@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--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=vvs@openvz.org \
--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
all inboxes | Powered by JetHome®