What's Intel Microcode?

[DaemonWarrior44]

What's Intel Microcode? How does it affect me?
It my first time on Linux and I don't know almost anything about it, but I want to learn.

[dany_boy]

I would explain, but since there is a wiki, just read it: https://wiki.archlinux.org/index.php/microcode

 

[Mira Yurizaki]

1 minute ago, DaemonWarrior44 said:

What's Intel Microcode? How does it affect me?

The way most x86 processors work now is they break up x86 instructions into simpler instructions that are specific for that processor. This is called the microcode. The reason why they do this is because it makes out-of-order execution and filling up the execution pipelines simpler.

 

The only time microcode updates are pushed out is because there's a potentially game-breaking bug in the original microcode that shipped. You may not need it, but if you run into severe issues with your apps that you run and it can be traced to the microcode, then go ahead and update it.

 

[DaemonWarrior44]

@M.Yurizaki @dany_boy But how does enabling that option affect me?

[dany_boy]

Just now, DaemonWarrior44 said:

@M.Yurizaki @dany_boy But how does enabling that option affect me?

Well I would suppose it would attempt to update the μ-code in your CPU. Not entirely sure though.

[Electronics Wizardy]

2 minutes ago, DaemonWarrior44 said:

@M.Yurizaki @dany_boy But how does enabling that option affect me?

normally they fix issues in the cpu and can help fix errors on the hardware. Normally there a good thing. Why aren't they on by default then? cause there close source and you don't know what there really doing.

[Mira Yurizaki]

2 minutes ago, Electronics Wizardy said:

normally they fix issues in the cpu and can help fix errors on the hardware. Normally there a good thing. Why aren't they on by default then? cause there close source and you don't know what there really doing.

They're not on by default because unless you got a processor with the update already applied, it comes with whatever microcode it was shipped with.

 

And while I won't argue it's not a good thing, I also don't think you should update it if everything is running fine.

[DaemonWarrior44]

Just now, M.Yurizaki said:

They're not on by default because unless you got a processor with the update already applied, it comes with whatever microcode it was shipped with.

 

And while I won't argue it's not a good thing, I also don't think you should update it if everything is running fine.

So, I should only turn it on when something's going wrong, right?

[Mira Yurizaki]

3 minutes ago, DaemonWarrior44 said:

So, I should only turn it on when something's going wrong, right?

I don't think it's something you turn on. It's something you have to apply to the CPU itself. It's like a BIOS update, only for the CPU. Linux just has the capability of applying microcode updates on boot. i.e., once you do it, it's permanent.

 

Otherwise yes, it's something to consider if you're running into issues and you're certain the outdated microcode is the problem.

[DaemonWarrior44]

1 minute ago, M.Yurizaki said:

I don't think it's something you turn on. It's something you have to apply to the CPU itself. It's like a BIOS update, only for the CPU. Linux just has the capability of applying microcode updates on boot. i.e., once you do it, it's permanent.

 

Otherwise yes, it's something to consider if you're running into issues and you're certain the outdated microcode is the problem.

Oh, okay. I think it's better if I don't touch anything, haha. Thanks.

[SCHISCHKA]

I did it to my CPU and I noticed no difference

[DaemonWarrior44]

Just now, SCHISCHKA said:

I did it to my CPU and I noticed no difference

I just left everything by default, except peripherals (acceleration, sensitivity, etc.)...