On 05/11/2020 15:56, Jan Beulich wrote: > Using max undermines the separation between default and max. For example, > turning off AVX512F on an MPX-capable system silently turns on MPX, > despite this not being part of the default policy anymore. Since the > information is used only for determining what to convert 'x' to (but not > to e.g. validate '1' settings), the effect of this change is identical > for guests with (suitable) "cpuid=" settings to that of the changes > separating default from max and then converting (e.g.) MPX from being > part of default to only being part of max for guests without (affected) > "cpuid=" settings. > > Signed-off-by: Jan Beulich <[email protected]>
This is a semantic change for how the xend string works. However, I do agree with your reasoning. I'm pretty sure it won't be safe to backport across my change to effectively eliminate the s/k options, but that's fine because it was the same time period where I introduces a distinction between max and default. Acked-by: Andrew Cooper <[email protected]>
