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


Groups > linux.kernel > #1508291

Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix

From sonofagun@openmailbox.org
Newsgroups linux.kernel
Subject Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
Date 2016-10-25 15:20 +0200
Message-ID <sw9O1-67F-29@gated-at.bofh.it> (permalink)
References (6 earlier) <svMHM-7B9-5@gated-at.bofh.it> <svNku-841-15@gated-at.bofh.it> <svR4K-2cv-29@gated-at.bofh.it> <svUlY-4eX-7@gated-at.bofh.it> <sw6ds-3Ia-29@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


> Why not? It all depends on the load type, working set and the access
> patterns. There's no strong correlation between the load of a machine
> and the amount of branch misses...
Yes I did not say that there is a linear correlation but that does not 
mean that those two numbers move opposite to each other. On all our 
systems running more tasks that consume more CPU and memory result in 
increased branch misses.
  It is normal as one thread might block another and a third thread might 
wait for the first thread to finish in order to resume.
  It is not normal to have increased misses only when the OS is loaded 
and running in idle without doing anything. Unless you are talking for 
AMD F14.

I wonder if we should just flush the L2 and disable it completely on AMD 
F14. Since this is an APU I have no idea if the onboard graphics can 
operate properly without L2.

> setpci -s 0x18.4 0x164.l
> 
> and looking at bit 2. If it is set, the erratum is fixed.
Will do but there is no meaning as I already told you on the first mail 
that D18F4x164 is 00000003h. It will not change.

> No, I don't mean that - I'm talking about *not* applying it by default
> and when people start seeing issues like that, they can boot their
> machines with something like "enable_e688_workaround" or so and it will
> get applied then. I.e., an "opt-in" deal.
Yes I got it. I have no problem, you are free to do what you think is 
the best solution. Just ensure that it will not be possible to apply the 
fix to F16.

Even if you decide to not include the fix at all in the kernel, I still 
have the patch for my system and it works.

Did you get any crashes on your B0 box with Ubuntu? Is it a desktop 
system or a laptop?

The irony is that this laptop was bought without USB3 on purpose to 
achieve maximum stability... Luckily we didn't stick to the original 
plan to buy two laptops :)

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-21 18:20 +0200
  Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-21 18:50 +0200
    Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-22 00:00 +0200
      Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-22 01:10 +0200
        Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-22 13:20 +0200
          Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-22 17:10 +0200
            Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-23 11:40 +0200
              Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-23 12:00 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-23 19:10 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-23 19:30 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-23 23:10 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-23 23:40 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-24 14:40 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-24 15:20 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-24 19:20 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-24 22:50 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Borislav Petkov <bp@alien8.de> - 2016-10-25 11:30 +0200
                Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun@openmailbox.org - 2016-10-25 15:20 +0200

csiph-web