On Tue, Jan 14, 2014 at 07:14:48AM -0800, H. Peter Anvin wrote:
> Seriously, though, if this MSR can be set at runtime without problems
> (which covers 98% of all workarounds, but not 100%) then it seems
> like a no-brainer to just do it as long as the offending CPUs can be
> identified by the
On 01/14/2014 03:55 AM, Borislav Petkov wrote:
> On Tue, Jan 14, 2014 at 09:41:33AM -0200, Henrique de Moraes Holschuh wrote:
>> I just got this assigned to amd64-microcode in Debian, but it is something
>> that needs to be worked around by the EFI/BIOS and/or the kernel.
>>
>> Since we all know
On Tue, Jan 14, 2014 at 09:41:33AM -0200, Henrique de Moraes Holschuh wrote:
> I just got this assigned to amd64-microcode in Debian, but it is something
> that needs to be worked around by the EFI/BIOS and/or the kernel.
>
> Since we all know just how well it pans out to depend on BIOS/EFI
I just got this assigned to amd64-microcode in Debian, but it is something
that needs to be worked around by the EFI/BIOS and/or the kernel.
Since we all know just how well it pans out to depend on BIOS/EFI updates
for *anything*, I'm raising the issue here. IMHO looks like it would be
I just got this assigned to amd64-microcode in Debian, but it is something
that needs to be worked around by the EFI/BIOS and/or the kernel.
Since we all know just how well it pans out to depend on BIOS/EFI updates
for *anything*, I'm raising the issue here. IMHO looks like it would be
On Tue, Jan 14, 2014 at 09:41:33AM -0200, Henrique de Moraes Holschuh wrote:
I just got this assigned to amd64-microcode in Debian, but it is something
that needs to be worked around by the EFI/BIOS and/or the kernel.
Since we all know just how well it pans out to depend on BIOS/EFI updates
On 01/14/2014 03:55 AM, Borislav Petkov wrote:
On Tue, Jan 14, 2014 at 09:41:33AM -0200, Henrique de Moraes Holschuh wrote:
I just got this assigned to amd64-microcode in Debian, but it is something
that needs to be worked around by the EFI/BIOS and/or the kernel.
Since we all know just how
On Tue, Jan 14, 2014 at 07:14:48AM -0800, H. Peter Anvin wrote:
Seriously, though, if this MSR can be set at runtime without problems
(which covers 98% of all workarounds, but not 100%) then it seems
like a no-brainer to just do it as long as the offending CPUs can be
identified by the kernel.
8 matches
Mail list logo