On Wednesday 14 January 2009 04:02:29 Avi Kivity wrote: > Following is my alternative to irq routing. The differences compared to > Sheng's version are: > > - A single ioctl to replace the entire routing table, instead of add/remove > ioctls for individual routing entries. Routing changes are rare, and > we need to track the entire table in userspace anyway (for save/restore, > and for user irqchip). As a side effect changes are atomic. > - Interrupt numbers are allocated by userspace, instead of the kernel > - I implemented irqchip routings rather then MSIs, it should be easy to > add MSIs later on. > > Please review and comment.
Look nice to me now... Save/restore is a good reason to maintain a table in userspace. And looking forward to userspace patch. Put a table in kvm_context? -- regards Yang, Sheng > > Avi Kivity (1): > KVM: Userspace controlled irq routing > > arch/ia64/kvm/kvm-ia64.c | 5 ++ > arch/x86/kvm/x86.c | 6 ++ > include/linux/kvm.h | 33 +++++++++ > include/linux/kvm_host.h | 31 +++++++++ > virt/kvm/irq_comm.c | 168 > ++++++++++++++++++++++++++++++++++++++++++++- virt/kvm/kvm_main.c | > 25 +++++++ > 6 files changed, 264 insertions(+), 4 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
