[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 4/4] AMD IOMMU: untie remap and vector maps
On Tue, Mar 26, 2013 at 9:05 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote: > With the specific IRTEs used for an interrupt no longer depending on > the vector, there's no need to tie the remap sharing model to the > vector sharing one. > > Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Unfortunately I'm having a bit of trouble "paging in" the technical details of why this change was necessary. I thought that the limitation had to do with the remapping table itself. Are you saying that if interrupt X maps to pcpu 0 vector 5, and interrupt Y maps to pcpu 2 vector 5, that even if X and Y are in the same table, they will still go to the right place? Could you give me a brief explanation of why that is? (I don't know what IRTE is, and Google is not helpful.) -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |