From: Mark Shinwell <mshinwell@janestreet.com>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] [IMPORTANT] Intel Skylake / Kaby Lake hardware bug affects OCaml programs
Date: Fri, 30 Jun 2017 16:28:38 +0100 [thread overview]
Message-ID: <CAM3Ki76c0t-8OD-r32hgc36F1g20BhTGgWdPeoiobGhS9kc6=g@mail.gmail.com> (raw)
In-Reply-To: <a9379c12-2552-ade2-0ca3-035f5f8e0664@inria.fr>
The problem with Kaby Lake systems is that the microcode update is
currently only available via a BIOS update rather than, for example, a
package in a typical Linux distribution (e.g. intel-microcode on
Debian). As such you may find at present that an update is not
available; in these cases you should disable hyperthreading.
Mark
On 30 June 2017 at 15:15, Xavier Leroy <xavier.leroy@inria.fr> wrote:
> Clarification:
>
>> Possible fixes include:
>>
>> - Apply the microcode update recently released by Intel [...]
>
> Contradicting what I wrote before, microcode updates are available both for Skylake and for Kaby Lake processors. It's only how to apply those updates that differs slightly between Skylake and Kaby Lake. Again, see the excellent instructions at
> https://lists.debian.org/debian-devel/2017/06/msg00308.html
>
> Sorry for the confusion.
>
> - Xavier Leroy
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2017-06-30 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:51 Xavier Leroy
2017-06-30 14:15 ` Xavier Leroy
2017-06-30 15:17 ` Gabriel Scherer
2017-06-30 15:31 ` Emilio Jesús Gallego Arias
2017-06-30 16:30 ` Julia Lawall
2017-06-30 16:46 ` Anton Bachin
2017-06-30 17:03 ` Xavier Leroy
2017-07-05 1:01 ` Johannes Kanig
2017-06-30 15:28 ` Mark Shinwell [this message]
2017-06-30 15:19 ` Maxime Dénès
2017-06-30 15:38 ` Anton Bachin
2017-07-21 13:00 ` David MENTRÉ
2017-07-22 7:27 ` Gabriel Scherer
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='CAM3Ki76c0t-8OD-r32hgc36F1g20BhTGgWdPeoiobGhS9kc6=g@mail.gmail.com' \
--to=mshinwell@janestreet.com \
--cc=caml-list@inria.fr \
--cc=xavier.leroy@inria.fr \
/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).