From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>, Borislav Petkov <bp@suse.de>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
tony.luck@intel.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: Clarify the affected CPUs list for Processor MMIO Stale Data
Date: Tue, 14 Jun 2022 20:37:59 -0700 [thread overview]
Message-ID: <442705df67230c7cab00ac6647a68d6e73b6835c.1655243963.git.pawan.kumar.gupta@linux.intel.com> (raw)
Add clarifying text that list of affected processors is limited to the
processors that are within the support window.
Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
---
.../admin-guide/hw-vuln/processor_mmio_stale_data.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst b/Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst
index 9393c50b5afc..49c30ae53894 100644
--- a/Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst
+++ b/Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst
@@ -80,7 +80,8 @@ Not all the CPUs are affected by all the variants. For instance, most
processors for the server market (excluding Intel Xeon E3 processors) are
impacted by only Device Register Partial Write (DRPW).
-Below is the list of affected Intel processors [#f1]_:
+Below is the list of affected Intel processors within the support window at the
+time of disclosure [#f1]_:
=================== ============ =========
Common name Family_Model Steppings
--
2.35.3
reply other threads:[~2022-06-15 3:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=442705df67230c7cab00ac6647a68d6e73b6835c.1655243963.git.pawan.kumar.gupta@linux.intel.com \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®