On 04/15/2010 09:37 PM, Glauber Costa wrote:
Avi pointed out a while ago that those MSRs falls into the pentium PMU range. So the idea here is to add new ones, and after a while, deprecate the old ones. Signed-off-by: Glauber Costa<glommer@xxxxxxxxxx> --- arch/x86/include/asm/kvm_para.h | 8 ++++++-- arch/x86/kvm/x86.c | 7 ++++++- 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/arch/x86/include/asm/kvm_para.h b/arch/x86/include/asm/kvm_para.h index ffae142..0cffb96 100644 --- a/arch/x86/include/asm/kvm_para.h +++ b/arch/x86/include/asm/kvm_para.h @@ -17,8 +17,12 @@ #define KVM_FEATURE_NOP_IO_DELAY 1 #define KVM_FEATURE_MMU_OP 2 -#define MSR_KVM_WALL_CLOCK 0x11 -#define MSR_KVM_SYSTEM_TIME 0x12 +#define MSR_KVM_WALL_CLOCK_OLD 0x11 +#define MSR_KVM_SYSTEM_TIME_OLD 0x12 + +/* Custom MSRs falls in the range 0x4b564d00-0x4b564dff */ +#define MSR_KVM_WALL_CLOCK 0x4b564d00 +#define MSR_KVM_SYSTEM_TIME 0x4b564d01
This is exposed to userspace. Userspace that is compiled with the new headers, but runs on an old kernel, will break.
So you need to keep the old names, and define a new KVM_FEATURE for the new names.
-- Do not meddle in the internals of kernels, for they are subtle and quick to panic. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
