public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Microcode updates for "old" Intel CPU's
Date: Sun, 7 Jan 2018 18:55:03 -0600	[thread overview]
Message-ID: <CAAD4mYj27pMOMsJM0PUkchHBZpH6-U2TL7sWN7Wb+tNQkB2=+A@mail.gmail.com> (raw)
In-Reply-To: <15310596.tlLjEkevsN@peak>

On Sunday, 7 January 2018 20:46:52 GMT Taiidan@gmx.com wrote:
> I have several sandy/ivybridge CPU's and I was wondering if anyone knows
> as to if intel is releasing microcode updates for them.
>
> It sure would be funny if intel wanted you to buy a new CPU to fix a
> problem that was their fault to begin with.

As I found explained elsewhere, what can be done with microcode
updates is actually very limited. It was claimed that most often Intel
would use updates to disable features, permanently, and could not do
much more with microcode. This agrees with my understanding of
electronics, though I originally did think that slightly more was
possible. Perhaps they could disable some cache functionality or
speculative execution, but you would still be left with the
performance penalties of most of the code-based fixes.

In any case, using my original expectations, I would not expect them
to be able to modify the behavior of the execution units in such a
fundamental way. If great changes are possible with microcode then
Intel's processors are actually closer to FPGAs, which I do not think
is likely, as FPGAs are very power and space inefficient.


On Sun, Jan 7, 2018 at 6:00 PM, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> Welcome to unbridled capitalism, USA-style.
>

I have a mobile device that I noticed had a severe reduction in
battery life mid-November, about the time the patches were rolled out
by Microsoft. I may have to look at legal action in this regard, as
now the device is unusable. I assumed it was compromised anyway and
would prefer the performance back.

Cheers,
     R0b0t1


  reply	other threads:[~2018-01-08  0:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 20:46 [gentoo-user] Microcode updates for "old" Intel CPU's Taiidan
2018-01-08  0:00 ` Peter Humphrey
2018-01-08  0:55   ` R0b0t1 [this message]
2018-01-09  8:43   ` Luigi Mantellini
2018-01-08  4:47 ` Adam Carter
2018-01-08 17:47 ` Corbin Bird
2018-01-09  7:56   ` Mick
2018-01-10  1:33     ` Corbin Bird
2018-01-10  1:46       ` Rich Freeman
2018-01-11 22:41         ` Mick
2018-01-11 23:02           ` Rich Freeman
2018-01-12 16:23             ` Corbin Bird
2018-01-12 17:21               ` Taiidan
     [not found]                 ` <1542759.NuuG9cTaQ6@dell_xps>
2018-01-13 18:14                   ` Taiidan
2018-01-12 17:47               ` Rich Freeman
2018-01-12 18:42                 ` Mick
2018-01-12 19:06                   ` Rich Freeman
2018-01-12 20:32                     ` Taiidan
2018-01-12 19:58                   ` Corbin Bird
2018-01-12 20:18                     ` Rich Freeman
2018-01-13  0:03                       ` Adam Carter
2018-01-13  0:06                       ` Adam Carter
2018-01-12 16:23           ` Daniel Frey

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='CAAD4mYj27pMOMsJM0PUkchHBZpH6-U2TL7sWN7Wb+tNQkB2=+A@mail.gmail.com' \
    --to=r030t1@gmail.com \
    --cc=gentoo-user@lists.gentoo.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