lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 16 May 2019 10:54:43 +0300
From:   Liran Alon <>
To:     "wencongyang (A)" <>
        Huangzhichao <>,
        guijianfeng <>,
        gaowanlong <>,
        "Chentao (Boby)" <>,
        "Liujinsong (Paul)" <>
Subject: Re: Question about MDS mitigation

Indeed those CPU resources are shared between sibling hyperthreads on same CPU core.
There is currently no mechanism merged upstream to completely mitigate SMT-enabled scenarios.
Note that this is also true for L1TF.

There are several proposal to address this but they are still in early research mode.
For example, see this KVM address space isolation patch series developed by myself and Alexandre:
(Which should be integrated with a mechanism which kick sibling hyperthreads when switching from KVM isolated address space to full kernel address space)
This partially mimics Microsoft work regarding HyperClear which you can read more about it here:


> On 16 May 2019, at 5:42, wencongyang (A) <> wrote:
> Hi all
> Fill buffers, load ports are shared between threads on the same physical core.
> We need to run more than one vm on the same physical core.
> Is there any complete mitigation for environments utilizing SMT?

Powered by blists - more mailing lists