diff options
author | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | 2011-02-16 13:43:04 -0500 |
---|---|---|
committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | 2011-02-18 09:26:37 -0500 |
commit | 55cb8cd45e0600df1473489518d7f12ce1bbe973 (patch) | |
tree | 10e0d7301cca3b6511018703a4c1cb7f4645cb36 /drivers | |
parent | 1d4610527bc71d3f9eea520fc51a02d54f79dcd0 (diff) | |
download | kernel_samsung_tuna-55cb8cd45e0600df1473489518d7f12ce1bbe973.zip kernel_samsung_tuna-55cb8cd45e0600df1473489518d7f12ce1bbe973.tar.gz kernel_samsung_tuna-55cb8cd45e0600df1473489518d7f12ce1bbe973.tar.bz2 |
pci/xen: Use xen_allocate_pirq_msi instead of xen_allocate_pirq
xen_allocate_pirq -> xen_map_pirq_gsi -> PHYSDEVOP_alloc_irq_vector IFF
xen_initial_domain() in addition to the kernel side book-keeping side of
things (set chip and handler, update irq_info etc) whereas
xen_allocate_pirq_msi just does the kernel book keeping.
Also xen_allocate_pirq allocates an IRQ in the 1-1 GSI space whereas
xen_allocate_pirq_msi allocates a dynamic one in the >GSI IRQ space.
All of this is uneccessary as this code path is only executed
when we run as a domU PV guest with an MSI/MSI-X PCI card passed in.
Hence we can jump straight to allocating an dynamic IRQ (and
binding it to the proper PIRQ) and skip the rest.
In short: this change is a cosmetic one.
Reviewed-by: Ian Campbell <Ian.Campbell@citrix.com>
Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions