aboutsummaryrefslogtreecommitdiffstats
path: root/xen/drivers/passthrough
diff options
context:
space:
mode:
authorAndrew Cooper <andrew.cooper3@citrix.com>2013-03-20 10:00:01 +0100
committerJan Beulich <jbeulich@suse.com>2013-03-20 10:00:01 +0100
commit0f7b6f91ac1bbfd33b23c291b14874b9561909d2 (patch)
treea7cac608cd1903985f338804241fca718935c9a3 /xen/drivers/passthrough
parent2d8a2823f3d6d2e5fba832e0afe1fab8fbcb3694 (diff)
downloadxen-0f7b6f91ac1bbfd33b23c291b14874b9561909d2.tar.gz
xen-0f7b6f91ac1bbfd33b23c291b14874b9561909d2.tar.bz2
xen-0f7b6f91ac1bbfd33b23c291b14874b9561909d2.zip
AMD/IOMMU: Process softirqs while building dom0 iommu mappings
Recent changes which have made their way into xen-4.2 stable have pushed the runtime of construct_dom0() over 5 seconds, which has caused regressions in XenServer testing because of our 5 second watchdog. The root cause is that amd_iommu_dom0_init() does not process softirqs and in particular the nmi_timer which causes the watchdog to decide that no useful progress is being made. This patch adds periodic calls to process_pending_softirqs() at the same interval as the Intel variant of this function. The server which was failing with the watchdog test now boots reliably with a timeout of 1 second. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Diffstat (limited to 'xen/drivers/passthrough')
-rw-r--r--xen/drivers/passthrough/amd/pci_amd_iommu.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/xen/drivers/passthrough/amd/pci_amd_iommu.c b/xen/drivers/passthrough/amd/pci_amd_iommu.c
index 2098e419a6..60696d74d8 100644
--- a/xen/drivers/passthrough/amd/pci_amd_iommu.c
+++ b/xen/drivers/passthrough/amd/pci_amd_iommu.c
@@ -317,6 +317,9 @@ static void __init amd_iommu_dom0_init(struct domain *d)
if ( mfn_valid(pfn) )
amd_iommu_map_page(d, pfn, pfn,
IOMMUF_readable|IOMMUF_writable);
+
+ if ( !(i & 0xfffff) )
+ process_pending_softirqs();
}
}