From: Borislav Petkov <bp@alien8.de>
To: Tong Tiangen <tongtiangen@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
wangkefeng.wang@huawei.com,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Tony Luck <tony.luck@intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
linux-mm@kvack.org, Guohanjun <guohanjun@huawei.com>
Subject: Re: [PATCH -next v4 2/3] x86/mce: rename MCE_IN_KERNEL_COPYIN to MCE_IN_KERNEL_COPY_MC
Date: Wed, 31 Jan 2024 08:02:58 +0100 [thread overview]
Message-ID: <20240131070258.GGZbnwov0g918F-FGz@fat_crate.local> (raw)
In-Reply-To: <20240111135548.3207437-3-tongtiangen@huawei.com>
On Thu, Jan 11, 2024 at 09:55:47PM +0800, Tong Tiangen wrote:
> Currently, there are some kernel memory copy scenarios is also mc safe
> which use copy_mc_to_kernel() or copy_mc_user_highpage().
Both of those end up in copy_mc_enhanced_fast_string() which does
EX_TYPE_DEFAULT_MCE_SAFE.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-01-31 7:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 13:55 [PATCH -next v4 0/3] minor improvements for x86 mce processing Tong Tiangen
2024-01-11 13:55 ` [PATCH -next v4 1/3] x86/mce: remove redundant fixup type EX_TYPE_COPY Tong Tiangen
2024-01-30 21:09 ` Borislav Petkov
2024-02-01 11:02 ` Tong Tiangen
2024-02-01 12:43 ` Tong Tiangen
2024-01-11 13:55 ` [PATCH -next v4 2/3] x86/mce: rename MCE_IN_KERNEL_COPYIN to MCE_IN_KERNEL_COPY_MC Tong Tiangen
2024-01-31 7:02 ` Borislav Petkov [this message]
2024-02-01 11:37 ` Tong Tiangen
2024-02-01 14:20 ` Borislav Petkov
2024-02-02 7:51 ` Tong Tiangen
2024-02-02 13:39 ` Borislav Petkov
2024-02-02 18:44 ` Luck, Tony
2024-02-02 19:42 ` Borislav Petkov
2024-02-02 21:36 ` Luck, Tony
2024-02-02 22:22 ` Borislav Petkov
2024-02-02 22:46 ` Luck, Tony
2024-02-03 7:56 ` Tong Tiangen
2024-02-03 9:43 ` Borislav Petkov
2024-02-04 1:52 ` Tong Tiangen
2024-01-11 13:55 ` [PATCH -next v4 3/3] x86/mce: set MCE_IN_KERNEL_COPY_MC for DEFAULT_MCE_SAFE exception Tong Tiangen
2024-01-15 13:25 ` [PATCH -next v4 0/3] minor improvements for x86 mce processing Kefeng Wang
2024-01-15 13:33 ` Borislav Petkov
2024-01-16 1:14 ` Kefeng Wang
2024-01-16 10:30 ` Borislav Petkov
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=20240131070258.GGZbnwov0g918F-FGz@fat_crate.local \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=naoya.horiguchi@nec.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tongtiangen@huawei.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.com \
--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