On 20/07/19 00:05, Eduardo Habkost wrote: >> Actually KVM does not mark it as supported: >> >> const u32 kvm_cpuid_7_0_ebx_x86_features = >> F(FSGSBASE) | F(BMI1) | F(HLE) | F(AVX2) | F(SMEP) | >> F(BMI2) | F(ERMS) | f_invpcid | F(RTM) | f_mpx | F(RDSEED) | >> F(ADX) | F(SMAP) | F(AVX512IFMA) | F(AVX512F) | F(AVX512PF) | >> F(AVX512ER) | F(AVX512CD) | F(CLFLUSHOPT) | F(CLWB) | >> F(AVX512DQ) | >> F(SHA_NI) | F(AVX512BW) | F(AVX512VL) | f_intel_pt; > We can still add the feature name if we also set it on > .unmigratable_features, but I don't see why it would be useful. > Is anybody working to support exposing RDT-M to guests?
I don't think so. Paolo
