diff options
| author | Yijing Wang <wangyijing@huawei.com> | 2014-09-17 13:32:19 +0400 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2014-09-25 21:11:47 +0400 |
| commit | 5fc24d8cb9d43e0db335137051092da03a6845dc (patch) | |
| tree | c476b207814a1409d74fffe7b0837ef372dc7f9a /firmware/vicam | |
| parent | fb3e306515ba6a012364b698b8ca71c337424ed3 (diff) | |
| download | linux-5fc24d8cb9d43e0db335137051092da03a6845dc.tar.xz | |
iommu/irq_remapping: Fix the regression of hpet irq remapping
Commit 71054d8841b4 ("x86, hpet: Introduce x86_msi_ops.setup_hpet_msi")
introduced x86_msi_ops.setup_hpet_msi to setup hpet MSI irq
when irq remapping enabled. This caused a regression of
hpet MSI irq remapping.
Original code flow before commit 71054d8841b4:
hpet_setup_msi_irq()
arch_setup_hpet_msi()
setup_hpet_msi_remapped()
remap_ops->setup_hpet_msi()
alloc_irte()
msi_compose_msg()
hpet_msi_write()
...
Current code flow after commit 71054d8841b4:
hpet_setup_msi_irq()
x86_msi.setup_hpet_msi()
setup_hpet_msi_remapped()
intel_setup_hpet_msi()
alloc_irte()
Currently, we only call alloc_irte() for hpet MSI, but
do not composed and wrote its msg...
Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'firmware/vicam')
0 files changed, 0 insertions, 0 deletions