RE: [ANNOUNCE] iommu-2.6.git tree

[Luck, Tony]

> The x86 maintainers are not responsible for IA64 patches AFAIK. The KVM
> work will be merged by Avi.
       ^^^^^^^

FYI: This part appears to have already happened:

$ git log v2.6.27.. | grep KVM.*ia64
      KVM: ia64: Add intel iommu support for guests.
      KVM: ia64: add directed mmio range support for kvm guests
      KVM: ia64: Make pmt table be able to hold physical mmio entries.
    KVM: ia64: Add intel iommu support for guests.
    KVM: ia64: add directed mmio range support for kvm guests
    KVM: ia64: Make pmt table be able to hold physical mmio entries.
    KVM: ia64: add support for Tukwila processors
    KVM: ia64: Implement a uniform vps interface
    KVM: ia64: Implement kvm_arch_vcpu_ioctl_{set,get}_mpstate
    KVM: ia64: Enable virtio driver for ia64 in Kconfig
    KVM: ia64: add a dummy irq ack notification

I have some extra ia64 bits queued in my tree (that are in today's
linux-next tree tagged "next-20081020").  These parts build OK by
themselves, but CONFIG_DMAR can't be turned on until the pieces that
David has in his tree are merged too (e.g. the parts that make
the driver work for systems where PAGESIZE may be something other
than 4K).

-Tony
--
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/