On Thursday, 18 July 2019 13:33:36 BST Corbin wrote:
> On 7/17/19 3:51 PM, Ian Zimmerman wrote:
> > pti=0 ibrs=0 ibpb=1 retp=1 -> fix variant #1 #2 if the microcode
> > update is applied pti=0 ibrs=2 ibpb=1 retp=1 -> fix variant #1 #2 on
> > older processors that can disable indirect br
On 7/17/19 3:51 PM, Ian Zimmerman wrote:
> pti=0 ibrs=0 ibpb=1 retp=1 -> fix variant #1 #2 if the microcode update
> is applied
> pti=0 ibrs=2 ibpb=1 retp=1 -> fix variant #1 #2 on older processors that
> can disable indirect branch prediction without microcode updates
>
> Note: A m
On 2019-07-17 07:46, Corbin wrote:
> My kernel version : 4.19.59
>
> Please note that I am using the "experimental" USE FLAG for
> "sys-kernel/gentoo-sources".
>
> CPU selected is "AMD Piledriver"
>
> Also, I am using the latest firmware for "sys-kernel/linux-firmware" (
> 20190712:0 ).
>
> Ke
On Monday, 15 July 2019 22:18:12 BST Ian Zimmerman wrote:
> UH-OH, Self-followup:
>
> On 2019-07-14 21:30, Ian Zimmerman wrote:
> > I find it odd that there is apparently no central way to track which
> > firmwares are being loaded without a debugging kernel.
> >
> > The relevant messages in linu
UH-OH, Self-followup:
On 2019-07-14 21:30, Ian Zimmerman wrote:
> I find it odd that there is apparently no central way to track which
> firmwares are being loaded without a debugging kernel.
>
> The relevant messages in linux/drivers/base/firmware_loader/main.c are
> all dev_dbg(), which as I u
On 2019-07-13 19:06, Mick wrote:
> > If linux-firmware is emerged with the savedconfig use flag, then
> > only the firmware not deleted from the config file is left.
>
> Yes. I used to do this, but gave up after a while.
I find it odd that there is apparently no central way to track which
firmw
On Saturday, 13 July 2019 02:13:00 BST Adam Carter wrote:
> grep fam /proc/cpuinfo
>
> -> 21 = 15h
> -> 22 = 16h
Yep, here's the laptop:
$ grep fam -m1 /proc/cpuinfo
cpu family : 21
and here's the dekstop:
$ grep fam -m1 /proc/cpuinfo
cpu family : 21
--
Regards,
Mick
signature.a
Thank you both, for your replies.
On Saturday, 13 July 2019 01:56:30 BST Adam Carter wrote:
> > > $ dmesg | grep -i micro
> > > [0.622441] [drm] Loading ARUBA Microcode
> > > [5.763242] [drm] Loading hainan Microcode
> > > [6.653025] microcode: CPU0: patch_level=0x06001119
> > > [6
grep fam /proc/cpuinfo
-> 21 = 15h
-> 22 = 16h
> > $ dmesg | grep -i micro
> > [0.622441] [drm] Loading ARUBA Microcode
> > [5.763242] [drm] Loading hainan Microcode
> > [6.653025] microcode: CPU0: patch_level=0x06001119
> > [6.657962] microcode: CPU1: patch_level=0x06001119
> > [6.658890] microcode: CPU2: patch_level=0x0600
On 2019-07-12 13:18, Mick wrote:
> $ dmesg | grep -i micro
> [0.622441] [drm] Loading ARUBA Microcode
> [5.763242] [drm] Loading hainan Microcode
> [6.653025] microcode: CPU0: patch_level=0x06001119
> [6.657962] microcode: CPU1: patch_level=0x06001119
> [6.658890] microcode: CP
11 matches
Mail list logo
