mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 02:01:24 +01:00
Quan Xu
dca07f3002
The parameter 'iommu_dev_iotlb_timeout' specifies the timeout of device IOTLB invalidation in milliseconds. By default, the timeout is 1000 milliseconds, which can be boot-time changed. We also confirmed with VT-d hardware team that 1 milliseconds is large enough for VT-d IOMMU internal invalidation. the existing panic() is eliminated and we bubble up the timeout of device IOTLB invalidation for further processing, as the PCI-e Address Translation Services (ATS) mandates a timeout of 60 seconds for device IOTLB invalidation. Obviously we can't spin for 60 seconds or otherwise Xen hypervisor hangs. Signed-off-by: Quan Xu <quan.xu@intel.com> Acked-by: Kevin Tian <kevin.tian@intel.com> Reviewed-by: Jan Beulich <jbeulich@suse.com>
xen-bugtool =========== The xen-bugtool command line application will collate the Xen dmesg output, details of the hardware configuration of your machine, information about the build of Xen that you are using, plus, if you allow it, various logs. The information collated can either be posted to a Xen Bugzilla bug (this bug must already exist in the system, and you must be a registered user there), or it can be saved as a .tar.bz2 for sending or archiving. The collated logs may contain private information, and if you are at all worried about that, you should not use this tool, or you should explicitly exclude those logs from the archive. xen-bugtool is wholly interactive, so simply run it, and answer the questions.