Hello Borris, thank you both. It was about time... Thanks for your effort
though!
Ingo is right here any modification must be advertised.
The patch was sent on October but I didn't fell on it until...
yesterday when I saw that it was routed for 3.16!
[3.16,136/204] x86/cpu/AMD: Apply the
Hello Borris, thank you both. It was about time... Thanks for your effort
though!
Ingo is right here any modification must be advertised.
The patch was sent on October but I didn't fell on it until...
yesterday when I saw that it was routed for 3.16!
[3.16,136/204] x86/cpu/AMD: Apply the
* Borislav Petkov wrote:
> On Sun, Oct 22, 2017 at 01:04:38PM +0200, Ingo Molnar wrote:
> > Any objections to me adding a printk message that we applied a fix?
> >
> > pr_info("x86/cpu/AMD: CPU erratum 688 worked around\n");
> >
> > or so?
> >
> > That would also create
* Borislav Petkov wrote:
> On Sun, Oct 22, 2017 at 01:04:38PM +0200, Ingo Molnar wrote:
> > Any objections to me adding a printk message that we applied a fix?
> >
> > pr_info("x86/cpu/AMD: CPU erratum 688 worked around\n");
> >
> > or so?
> >
> > That would also create some pressure for
On Sun, Oct 22, 2017 at 01:04:38PM +0200, Ingo Molnar wrote:
> Any objections to me adding a printk message that we applied a fix?
>
> pr_info("x86/cpu/AMD: CPU erratum 688 worked around\n");
>
> or so?
>
> That would also create some pressure for customers to prod manufacturers to
>
On Sun, Oct 22, 2017 at 01:04:38PM +0200, Ingo Molnar wrote:
> Any objections to me adding a printk message that we applied a fix?
>
> pr_info("x86/cpu/AMD: CPU erratum 688 worked around\n");
>
> or so?
>
> That would also create some pressure for customers to prod manufacturers to
>
* Borislav Petkov wrote:
> From: Borislav Petkov
>
> Some F14h machines have an erratum which, "under a highly specific
> and detailed set of internal timing conditions" can lead to skipping
> instructions and rIP corruption. Add the fix for those machines when
>
* Borislav Petkov wrote:
> From: Borislav Petkov
>
> Some F14h machines have an erratum which, "under a highly specific
> and detailed set of internal timing conditions" can lead to skipping
> instructions and rIP corruption. Add the fix for those machines when
> their BIOS doesn't apply it
From: Borislav Petkov
Some F14h machines have an erratum which, "under a highly specific
and detailed set of internal timing conditions" can lead to skipping
instructions and rIP corruption. Add the fix for those machines when
their BIOS doesn't apply it or there simply isn't BIOS
From: Borislav Petkov
Some F14h machines have an erratum which, "under a highly specific
and detailed set of internal timing conditions" can lead to skipping
instructions and rIP corruption. Add the fix for those machines when
their BIOS doesn't apply it or there simply isn't BIOS update for
10 matches
Mail list logo