From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>,
"Williams, Dan J" <dan.j.williams@intel.com>
Cc: Jane Chu <jane.chu@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
"Hansen, Dave" <dave.hansen@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>, david <david@fromorbit.com>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux NVDIMM <nvdimm@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
"Weiny, Ira" <ira.weiny@intel.com>,
Matthew Wilcox <willy@infradead.org>,
Vivek Goyal <vgoyal@redhat.com>, Jue Wang <juew@google.com>
Subject: RE: [PATCH v9 3/7] mce: fix set_mce_nospec to always unmap the whole page
Date: Wed, 11 May 2022 17:17:21 +0000 [thread overview]
Message-ID: <5aa1c9aacc5a4086a904440641062669@intel.com> (raw)
In-Reply-To: <Ynt3WlpcJwuqffDX@zn.tnic>
> I - just like you - am waiting for Tony to say whether he still needs
> this whole_page() thing. I already suggested removing it so I'm fine
> with this patch.
IIRC this new patch effectively reverts back to the original behavior that
I implemented back at the dawn of time. I.e. just always mark the whole
page "not present" and don't try to mess with UC mappings to allow
partial (but non-speculative) access to the not-poisoned parts of the
page.
If that is the case ... then Acked-by: Tony Luck <tony.luck@intel.com>
If I've misunderstood ... then please explain what it is doing.
Thanks
-Tony
next prev parent reply other threads:[~2022-05-11 17:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 22:45 [PATCH v9 0/7] DAX poison recovery Jane Chu
2022-04-22 22:45 ` [PATCH v9 1/7] acpi/nfit: rely on mce->misc to determine poison granularity Jane Chu
2022-04-22 22:45 ` [PATCH v9 2/7] x86/mce: relocate set{clear}_mce_nospec() functions Jane Chu
2022-04-28 13:09 ` Borislav Petkov
2022-05-13 21:41 ` [PATCH v10 " Dan Williams
2022-05-16 18:21 ` [PATCH v11 " Dan Williams
2022-05-16 20:30 ` [PATCH v9 " Dan Williams
2022-04-22 22:45 ` [PATCH v9 3/7] mce: fix set_mce_nospec to always unmap the whole page Jane Chu
2022-04-22 23:25 ` Dan Williams
2022-05-11 3:56 ` Dan Williams
2022-05-11 8:44 ` Borislav Petkov
2022-05-11 17:17 ` Luck, Tony [this message]
2022-05-13 3:41 ` Dan Williams
2022-05-16 18:38 ` [PATCH v10 " Dan Williams
2022-04-22 22:45 ` [PATCH v9 4/7] dax: introduce DAX_RECOVERY_WRITE dax access mode Jane Chu
2022-04-23 5:20 ` Christoph Hellwig
2022-05-13 21:55 ` [PATCH v10 " Dan Williams
2022-05-13 22:09 ` Dan Williams
2022-05-13 22:10 ` [PATCH v11 " Dan Williams
2022-05-16 12:40 ` [PATCH v10 " Vivek Goyal
2022-04-22 22:45 ` [PATCH v9 5/7] dax: add .recovery_write dax_operation Jane Chu
2022-04-22 22:45 ` [PATCH v9 6/7] pmem: refactor pmem_clear_poison() Jane Chu
2022-04-22 22:45 ` [PATCH v9 7/7] pmem: implement pmem_recovery_write() Jane Chu
2022-04-23 5:21 ` Christoph Hellwig
2022-05-13 22:13 ` [PATCH v10 " Dan Williams
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=5aa1c9aacc5a4086a904440641062669@intel.com \
--to=tony.luck@intel.com \
--cc=agk@redhat.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=jane.chu@oracle.com \
--cc=juew@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=snitzer@redhat.com \
--cc=vgoyal@redhat.com \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).