From: Christoph Hellwig <hch@infradead.org>
To: Jane Chu <jane.chu@oracle.com>
Cc: dan.j.williams@intel.com, bp@alien8.de, hch@infradead.org,
dave.hansen@intel.com, peterz@infradead.org, luto@kernel.org,
david@fromorbit.com, djwong@kernel.org,
linux-fsdevel@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
vishal.l.verma@intel.com, dave.jiang@intel.com, agk@redhat.com,
snitzer@redhat.com, dm-devel@redhat.com, ira.weiny@intel.com,
willy@infradead.org, vgoyal@redhat.com
Subject: Re: [PATCH v8 2/7] x86/mce: relocate set{clear}_mce_nospec() functions
Date: Wed, 20 Apr 2022 23:50:54 -0700 [thread overview]
Message-ID: <YmD+zgFf9Vih52gZ@infradead.org> (raw)
In-Reply-To: <20220420020435.90326-3-jane.chu@oracle.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2022-04-21 6:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 2:04 [PATCH v8 0/7] DAX poison recovery Jane Chu
2022-04-20 2:04 ` [PATCH v8 1/7] acpi/nfit: rely on mce->misc to determine poison granularity Jane Chu
2022-04-21 19:25 ` Dan Williams
2022-04-20 2:04 ` [PATCH v8 2/7] x86/mce: relocate set{clear}_mce_nospec() functions Jane Chu
2022-04-21 6:50 ` Christoph Hellwig [this message]
2022-04-22 3:46 ` Jane Chu
2022-04-20 2:04 ` [PATCH v8 3/7] mce: fix set_mce_nospec to always unmap the whole page Jane Chu
2022-04-21 6:51 ` Christoph Hellwig
2022-04-22 3:47 ` Jane Chu
2022-04-21 19:26 ` Dan Williams
2022-04-20 2:04 ` [PATCH v8 4/7] dax: introduce DAX_RECOVERY_WRITE dax access mode Jane Chu
2022-04-21 6:57 ` Christoph Hellwig
2022-04-22 4:15 ` Jane Chu
2022-04-21 19:35 ` Dan Williams
2022-04-22 4:15 ` Jane Chu
2022-04-20 2:04 ` [PATCH v8 5/7] dax: add .recovery_write dax_operation Jane Chu
2022-04-21 6:57 ` Christoph Hellwig
2022-04-20 2:04 ` [PATCH v8 6/7] pmem: refactor pmem_clear_poison() Jane Chu
2022-04-20 2:04 ` [PATCH v8 7/7] pmem: implement pmem_recovery_write() Jane Chu
2022-04-20 6:26 ` Dan Williams
2022-04-20 17:01 ` Jane Chu
2022-04-20 17:05 ` 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=YmD+zgFf9Vih52gZ@infradead.org \
--to=hch@infradead.org \
--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=ira.weiny@intel.com \
--cc=jane.chu@oracle.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).