Bug#578005: Please consider backporting KVM_GET/SET_CLOCK to 2.6.32
maximilian attems wrote:
> tried 3cfc3092f40bc37c57ba556cfd8de4218f2135ab,
> ffde22ac53b6d6b1d7206f1172176a667eead778.
>
> none of them apply.
ffde22ac53b6d6b1d7206f1172176a667eead778 (Xen-HVM) applies with some
(manually checked, safe) fuzz/offset.
On top of that, afbcf7ab8d1bc8c2d04792f6d9e786e0adeb328d (kvmclock)
applies cleanly also with some minor fuzz.
Alternatively, I've attached a backported "kvmclock" patch that applies
without "Xen-HVM", in case you don't want that.
As for 3cfc3092f40bc37c57ba556cfd8de4218f2135ab (VCPU events), after
applying the previous two, it has one minor conflict that is easily
solvable with a one-liner. If it isn't obvious, I can attach a patch.
(all of the above are tested with a git checkout of 2.6.32, haven't
tried Debian's SVN although I don't expect it to be much different)
Regards,
Faidon
Reply to: