Il 13/12/2013 16:04, Jan Kiszka ha scritto: > Yes, kvm-kmod is starting to bitrot. I just noticed I messed up the last > stable release back in August, and no one seems to have noticed it. > There were no complains about the missing releases for 3.11 and 3.12, so > it the relevance must have dropped significantly. I think the relevance of releases is ~zero. kvm-kmod still remains extremely useful IMHO as a hacking tool. > kvm-kmod is still useful for hacking, so I'm considering to stop > providing releases (except for a final 3.10.21), just updates in git to > allow wrapping of latest kvm head on recent kernels. Yes, git can be good enough for distribution. > There are breakages > with kernels < 3.0 now, about which I personally do not care anymore, so > lifting the entrance level to 3.0 seems reasonable. Agreed on this as well. Personally I would be fine even with only 3-4 releases backwards compatibility (e.g. 3.8) right now. >> > For completeness, here is the patch I am using right now. > Is there anything in your patch that is still required with current > kvm-kmod next? Then I would be happy about a patch! Your next branch works for me. The only difference between my patch and your origin/next is that I'm copying %(linux)s/arch/%(arch)s/include/uapi/asm/msr-index.h' and you have + +#ifndef MSR_IA32_VMX_MISC_PREEMPTION_TIMER_SCALE +#define MSR_IA32_VMX_MISC_PREEMPTION_TIMER_SCALE 0x1F +#endif Everything else is roughly the same. Thanks for maintaining kvm-kmod! Paolo -- 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
