Re: [RFC PATCH 0/4] ARM: KVM: Enable the ioeventfd capability of KVM on ARM

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

 



On 03/31/2014 05:53 PM, Peter Maydell wrote:
On 31 March 2014 16:49, Alexander Graf <agraf@xxxxxxx> wrote:
On 03/31/2014 03:53 PM, Peter Maydell wrote:
On 31 March 2014 14:44, Alexander Graf <agraf@xxxxxxx> wrote:
IRQ Routing is really just a map from a flat number space that KVM uses
internally to specific interrupt controller pins. So if you see a "GSI"
that
really just means "global interrupt index number".
Er, but we already have a global interrupt index number
for ARM, it's the value you pass to KVM_IRQ_LINE. What
extra does IRQ routing bring to the party?
It allows you to have multiple distributors :). And MSI target IDs that you
can use for irqfd.
What's a distributor in this context? Why would an MSI
target ID need to be any different from the ID format
we're currently using?

Because it may contain more information than the number space allows to cover (target address, data payload).


Alex

_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm




[Index of Archives]     [Linux KVM]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux