From: Borislav Petkov <bp@alien8.de>
To: Jane Chu <jane.chu@oracle.com>
Cc: dan.j.williams@intel.com, 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 v9 2/7] x86/mce: relocate set{clear}_mce_nospec() functions
Date: Thu, 28 Apr 2022 15:09:31 +0200 [thread overview]
Message-ID: <YmqSC9K10Jlm5VFG@zn.tnic> (raw)
In-Reply-To: <20220422224508.440670-3-jane.chu@oracle.com>
On Fri, Apr 22, 2022 at 04:45:03PM -0600, Jane Chu wrote:
> Relocate the twin mce functions to arch/x86/mm/pat/set_memory.c
> file where they belong.
>
> While at it, fixup a function name in a comment.
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Jane Chu <jane.chu@oracle.com>
> ---
> arch/x86/include/asm/set_memory.h | 52 -------------------------------
> arch/x86/mm/pat/set_memory.c | 49 ++++++++++++++++++++++++++++-
> include/linux/set_memory.h | 8 ++---
> 3 files changed, 52 insertions(+), 57 deletions(-)
Acked-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-04-28 13:09 UTC|newest]
Thread overview: 24+ 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 [this message]
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
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
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=YmqSC9K10Jlm5VFG@zn.tnic \
--to=bp@alien8.de \
--cc=agk@redhat.com \
--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=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).