[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH RFC V11 15/18] kvm : Paravirtual ticketlocks support for linux guests running on KVM hypervisor
- To: Gleb Natapov <gleb@xxxxxxxxxx>
- From: Ingo Molnar <mingo@xxxxxxxxxx>
- Date: Mon, 5 Aug 2013 15:52:22 +0200
- Cc: jeremy@xxxxxxxx, x86@xxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx, peterz@xxxxxxxxxxxxx, drjones@xxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, andi@xxxxxxxxxxxxxx, hpa@xxxxxxxxx, stefano.stabellini@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>, agraf@xxxxxxx, mingo@xxxxxxxxxx, habanero@xxxxxxxxxxxxxxxxxx, ouyang@xxxxxxxxxxx, mtosatti@xxxxxxxxxx, avi.kivity@xxxxxxxxx, tglx@xxxxxxxxxxxxx, chegu_vinod@xxxxxx, gregkh@xxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, srivatsa.vaddagiri@xxxxxxxxx, attilio.rao@xxxxxxxxxx, pbonzini@xxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 05 Aug 2013 13:52:50 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
* Gleb Natapov <gleb@xxxxxxxxxx> wrote:
> 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).
Thanks,
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
