Re: [PATCH v4] KVM: Introduce direct MSI message injection for in-kernel irqchips

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/04/2012 01:48 PM, Jan Kiszka wrote:
> > 
> > I'm not so sure anymore.  Sorry about the U turn, but remind me why?  In
> > the long term it will be slower.
>
> Likely not measurably slower. If you look at a message through the arch
> glasses, you can usually spot the destination directly, specifically if
> a message targets a single processor - no need for hashing and table
> lookups in the common case.

Not on x86.  The APIC ID is guest-provided.  In x2apic mode it can be
quite large.

> In contrast, the maintenance costs for the current explicit route based
> model are significant as we see now.
>

You mean in amount of code in userspace?  That doesn't get solved since
we need to keep compatibility.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

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


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux