Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1471117

Re: [PATCH 0/4] Better memcpy_mcsafe()

From Ingo Molnar <mingo@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH 0/4] Better memcpy_mcsafe()
Date 2016-08-27 09:30 +0200
Message-ID <saGdX-1B0-1@gated-at.bofh.it> (permalink)
References <saElP-rV-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


* Tony Luck <tony.luck@intel.com> wrote:

> The original version of this used a check of the x86_model_id string
> for the magic "Intel(R) Xeon(R) CPU E7-" to determine whether we are
> running on a cpu that supports machine check recovery.
> 
> Boris tried to talk me out of that, but at the time I didn't think
> there was a viable alternate option, and somehow he fell for that line.
> 
> It turns out there is a better way, that isn't as painful as I thought
> it might be.  It does help guarantee future employment, as I'll
> have to add a new quirk for each CPU generation. But the check for "E7"
> would have eventually failed and required a patch too.
> 
> The downside of a quirk is that it runs after the X86_FEATURE patching
> code. So instead of "static_cpu_has()" we use "static_branch_unlikely(&mcsafe_key)"

So why not move it to the early PCI quirk code in arch/x86/ and get rid of this 
quirk within a quirk?

Thanks,

	Ingo

Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

Re: [PATCH 0/4] Better memcpy_mcsafe() Ingo Molnar <mingo@kernel.org> - 2016-08-27 09:30 +0200

csiph-web