Hello,
I'm resending my last email since the first one didn't draw enough
attention despite the gravity of the situation and the issue has been
exacerbated by the recent kernel 4.20 changes which incur even a larger
performance loss - up to 50% according to the most recent Phoronix testing:
Hello,
I'm resending my last email since the first one didn't draw enough
attention despite the gravity of the situation and the issue has been
exacerbated by the recent kernel 4.20 changes which incur even a larger
performance loss - up to 50% according to the most recent Phoronix testing:
On 8/25/2018 4:28 PM, Artem S. Tashkinov wrote:
> On 08/25/2018 06:39 PM, Casey Schaufler wrote:
>> On 8/25/2018 3:42 AM, Artem S. Tashkinov wrote:
>>> Hello LKML,
>>>
>>> As time goes by more and more fixes of Intel/AMD/ARM CPUs vulnerabilities
>>> are added to the Linux kernel without a simple
On 8/25/2018 4:28 PM, Artem S. Tashkinov wrote:
> On 08/25/2018 06:39 PM, Casey Schaufler wrote:
>> On 8/25/2018 3:42 AM, Artem S. Tashkinov wrote:
>>> Hello LKML,
>>>
>>> As time goes by more and more fixes of Intel/AMD/ARM CPUs vulnerabilities
>>> are added to the Linux kernel without a simple
On 08/25/2018 06:39 PM, Casey Schaufler wrote:
On 8/25/2018 3:42 AM, Artem S. Tashkinov wrote:
Hello LKML,
As time goes by more and more fixes of Intel/AMD/ARM CPUs vulnerabilities are
added to the Linux kernel without a simple way to disable them all in one fell
swoop.
Many of the
On 08/25/2018 06:39 PM, Casey Schaufler wrote:
On 8/25/2018 3:42 AM, Artem S. Tashkinov wrote:
Hello LKML,
As time goes by more and more fixes of Intel/AMD/ARM CPUs vulnerabilities are
added to the Linux kernel without a simple way to disable them all in one fell
swoop.
Many of the
On 8/25/2018 3:42 AM, Artem S. Tashkinov wrote:
> Hello LKML,
>
> As time goes by more and more fixes of Intel/AMD/ARM CPUs vulnerabilities are
> added to the Linux kernel without a simple way to disable them all in one
> fell swoop.
Many of the mitigations are unrelated to each other. There is
On 8/25/2018 3:42 AM, Artem S. Tashkinov wrote:
> Hello LKML,
>
> As time goes by more and more fixes of Intel/AMD/ARM CPUs vulnerabilities are
> added to the Linux kernel without a simple way to disable them all in one
> fell swoop.
Many of the mitigations are unrelated to each other. There is
Hello LKML,
As time goes by more and more fixes of Intel/AMD/ARM CPUs
vulnerabilities are added to the Linux kernel without a simple way to
disable them all in one fell swoop.
Disabling is a good option for strictly confined environments where no
3d party untrusted code is ever to be run,
Hello LKML,
As time goes by more and more fixes of Intel/AMD/ARM CPUs
vulnerabilities are added to the Linux kernel without a simple way to
disable them all in one fell swoop.
Disabling is a good option for strictly confined environments where no
3d party untrusted code is ever to be run,
Hello LKML,
As time goes by more and more fixes of Intel/AMD/ARM CPUs
vulnerabilities are added to the Linux kernel without a simple way to
disable them all in one fell swoop.
Disabling is a good option for strictly confined environments where no
3d party untrusted code is ever to be run,
Hello LKML,
As time goes by more and more fixes of Intel/AMD/ARM CPUs
vulnerabilities are added to the Linux kernel without a simple way to
disable them all in one fell swoop.
Disabling is a good option for strictly confined environments where no
3d party untrusted code is ever to be run,
12 matches
Mail list logo
