From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Bruce Richardson <bruce.richardson@intel.com>,
john.mcnamara@intel.com, anatoly.burakov@intel.com,
ciara.power@intel.com
Cc: dev@dpdk.org
Subject: Intel Downfall mitigation
Date: Tue, 15 Aug 2023 11:20:50 +0200 [thread overview]
Message-ID: <2884378.BEx9A2HvPv@thomas> (raw)
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?
reply other threads:[~2023-08-15 9:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2884378.BEx9A2HvPv@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).