Messages in this thread |  | | From | Benjamin Lamowski <> | Subject | Re: [PATCH 1/1] x86/split_lock: check split lock feature on initialization | Date | Mon, 6 Apr 2020 10:23:16 +0200 |
| |
[...] > Calling split_lock_verify_msr() with X86_FEATURE_SPLIT_LOCK_DETECT=0 is > intentional, the idea is to ensure SLD is disabled on all CPUs, e.g. in the > unlikely scenario that BIOS enabled SLD.
I was aware of the intention, but I still don't understand under which scenario this could be set by the BIOS although the earlier feature detection has failed, i.e. shouldn't the feature have been detected in all cases where SLD can actually be disabled? If so, checking for availability first instead of catching a #GP(0) if it is not implemented seems to be the cleaner solution.
> The first rdmsrl_safe() should short circuit split_lock_verify_msr() if > the RDMSR faults, i.e. it might fault, but it shouldn't WARN. Are you > seeing issues or was this found via code inspection?
We stumbled across this issue because the x86 version of our VMM is not yet ready for production and when accessing unimplemented MSRs would simply return 0 and issue a warning. This is of course a deviation from rdmsr as defined in the SDM and the pieces are ours to keep, it will be changed to generate a #GP(0) once the last missing MSRs are emulated properly.
-- Benjamin Lamowski - +49.351.41883235 Operating Systems Engineer - https://www.kernkonzept.com
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth
|  |