Zhang, Xiantao wrote: > Han, Weidong wrote: >> Avi Kivity wrote: >>> Zhang, Xiantao wrote: >>>> Hi, Avi >>>> I have rebased the patchset according to your comments, it can >>>> be applied to current tip of kvm.git. Please review again and apply >>>> if no other concerns. Thanks! Xiantao >>>> [PATCH 1/8] kvm/vt-d: Moving vtd.c from arch/x86/kvm/ to virt/kvm/ >>>> [PATCH 2/8] kvm: Moving device_assignment logic to kvm_main.c >>>> [PATCH 3/8] kvm: Changing is_mmio_pfn to kvm_is_mmio_pfn, and make >>>> it common [PATCH 4/8] kvm: Split arch/x86/kvm/irq.c to two parts. >>>> [PATCH 5/8] kvm: Moving irqchip_in_kernel from ioapic.h to irq.h >>>> [PATCH 6/8] kvm/ia64: Make pmt table be able to hold physical mmio >>>> entries. [PATCH 7/8] kvm/ia64: Add directed mmio range support for >>>> kvm guests. [PATCH 8/8] kvm/ia64: Add intel iommu support for >>>> guests >>>> >>> >>> Applied all, thanks. >>> >>> Since it's relatively simple, and since follow-on vt-d fixes will >>> depend on it, I will likely push it for 2.6.28. >>> >> >> It's good to merge these patches. But meanwhile, we need to rebase >> other VT-d patches -:( > > Aha, every coin always has two sides. But anyway it should be easy > to rebase them, because the common parts split from x86 side have no > logic changes, and just did code move. :) Thanks! Xiantao > Yes, it's easy to rebase. And this makes VT-d code arch-independent. We will rebase after Avi merged these patches in. Regards, Weidong >>> >>> -- >>> Do not meddle in the internals of kernels, for they are subtle and >>> quick to panic. -- To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
