* Intel Downfall mitigation
@ 2023-08-15 9:20 Thomas Monjalon
0 siblings, 0 replies; only message in thread
From: Thomas Monjalon @ 2023-08-15 9:20 UTC (permalink / raw)
To: Konstantin Ananyev, Bruce Richardson, john.mcnamara,
anatoly.burakov, ciara.power
Cc: dev
Hello all,
Regarding the vulnerability recently discovered on Intel AVX CPU:
https://downfall.page/
Some microcode fixes are published by Intel.
Should we mitigate the vulnerability in DPDK as well?
In general, AVX512 is disabled by default in DPDK.
Other AVX sizes are enabled if possible.
The memcpy 512 is enabled at compilation only with RTE_MEMCPY_AVX512.
For now, there is no switch for other memcpy paths.
There is a method to disable most SIMD code at runtime.
From the application before EAL init:
rte_vect_set_max_simd_bitwidth(RTE_VECT_SIMD_DISABLED)
or from user input:
--force-max-simd-bitwidth=64
As far as I know it will disable any SIMD code (including AVX)
in most code paths except for rte_memcpy().
Opinions, comments?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-08-15 9:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-15 9:20 Intel Downfall mitigation Thomas Monjalon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).