Re: [PATCH 0/5] x86: KVM vdso and clock improvements

From: Andy Lutomirski
Date: Thu Dec 10 2015 - 22:22:30 EST

Next message: Andy Lutomirski: "[PATCH 3/6] x86/vdso: Track each mm's loaded vdso image as well as its base"
Previous message: Andy Lutomirski: "[PATCH 6/6] x86/vdso: Disallow vvar access to vclock IO for never-used vclocks"
In reply to: Paolo Bonzini: "Re: [tip:x86/asm] x86/kvm: On KVM re-enable (e.g. after suspend), update clocks"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Dec 10, 2015 at 7:20 PM, Andy Lutomirski <luto@xxxxxxxxxx> wrote:
> NB: patch 1 doesn't really belong here, but it makes this a lot

Ugh, please disregard the resend. I typoed my git send-email command slightly.

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Andy Lutomirski: "[PATCH 3/6] x86/vdso: Track each mm's loaded vdso image as well as its base"
Previous message: Andy Lutomirski: "[PATCH 6/6] x86/vdso: Disallow vvar access to vclock IO for never-used vclocks"
In reply to: Paolo Bonzini: "Re: [tip:x86/asm] x86/kvm: On KVM re-enable (e.g. after suspend), update clocks"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]