On Wed, Feb 1, 2023 at 5:29 AM Emanuele Giuseppe Esposito <eesposit@xxxxxxxxxx> wrote: > > As the title suggest, if the host cpu supports flush_l1d flag and > QEMU/userspace wants to boot a VM with the same flag (or emulate same > host features), KVM should be able to do so. > > Patch 3 is the main fix, because if flush_l1d is not advertised by > KVM, a linux VM will erroneously mark > /sys/devices/system/cpu/vulnerabilities/mmio_stale_data > as vulnerable, even though it isn't since the host has the feature > and takes care of this. Not sure what would happen in the nested case though. > > Patch 1 and 2 are just taken and refactored from Jim Mattison's serie that it > seems was lost a while ago: > https://patchwork.kernel.org/project/kvm/patch/20180814173049.21756-1-jmattson@xxxxxxxxxx/ > > I thought it was worth re-posting them. What has changed since the patches were originally posted, and Konrad dissed them?
