From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>,
Emanuel Czirai <xftroxgpx@protonmail.com>,
Ashok Raj <ashok.raj@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86/microcode: Fix CPU synchronization routine
Date: Wed, 14 Mar 2018 22:00:14 -0300 [thread overview]
Message-ID: <20180315010014.xsedkarzrgqiunxf@khazad-dum.debian.net> (raw)
In-Reply-To: <20180314183615.17629-2-bp@alien8.de>
On Wed, 14 Mar 2018, Borislav Petkov wrote:
> Also, since the update is serialized and it also takes a couple of
> thousand cycles per microcode engine, increase the exit timeout by the
> number of CPUs on the system.
Maybe on AMD it is that fast ;-)
Intel takes anything from twenty thousand cycles to several *million*
cycles per core, proportional to microcode update size.
--
Henrique Holschuh
next prev parent reply other threads:[~2018-03-15 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 18:36 [PATCH 1/2] x86/microcode: Attempt late loading only when new microcode is present Borislav Petkov
2018-03-14 18:36 ` [PATCH 2/2] x86/microcode: Fix CPU synchronization routine Borislav Petkov
2018-03-15 1:00 ` Henrique de Moraes Holschuh [this message]
2018-03-15 1:01 ` Borislav Petkov
2018-03-15 4:01 ` Henrique de Moraes Holschuh
2018-03-15 9:58 ` Borislav Petkov
2018-03-15 14:54 ` Henrique de Moraes Holschuh
2018-03-16 20:01 ` [tip:x86/pti] " tip-bot for Borislav Petkov
2018-03-16 20:00 ` [tip:x86/pti] x86/microcode: Attempt late loading only when new microcode is present tip-bot for 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=20180315010014.xsedkarzrgqiunxf@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--cc=xftroxgpx@protonmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.