On 31 March 2014 17:12, Alexander Graf <agraf@xxxxxxx> wrote: > 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: >>>> 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). I'm finding this conversation confusing because I think you're assuming more knowledge about MSI and irqfds than I have. What I was hoping to provoke with my initial question was a more detailed explanation of what the API does, when it gets used and what information gets passed around where. thanks -- PMM _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
