> > On Mon, Aug 05, 2013 at 11:46:03AM +0200, Ingo Molnar wrote: > > > Acked-by: Ingo Molnar <mingo@xxxxxxxxxx> > > > > > > I guess you'd want to carry this in the KVM tree or so - maybe in a > > > separate branch because it changes Xen as well? > > > > It changes KVM host and guest side, XEN and common x86 spinlock code. I > > think it would be best to merge common x86 spinlock bits and guest side > > KVM/XEN bits through tip tree and host KVM part will go through KVM > > tree. If this is OK with you, Ingo, and XEN folks Raghavendra can send > > two separate patch series one for the tip and one for KVM host side. > > Sure, that's fine - if the initial series works fine in isolation as well > (i.e. won't break anything). It would be a big problem if it didn't! Raghavendra, please send the two separate series as Gleb explained above. Thanks, 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
