Yang, Xiaowei
2008-May-23 07:56 UTC
[Xen-devel] [PATCH] VT-d: remove Xen and tboot range from dom0''s VT-d table
This a step forward to fix the security hole introduced by dom0''s 1:1 mapping VT-d table: remove the critical code and data from it. The more flexible solution is to update dom0''s VT-d table on demand as what will be done for other PV domains. However, there could bring a performance issue even with software optimization. Iotlb flush of some hardware is time-consuming. Signed-off-by: Yang, Xiaowei <xiaowei.yang@intel.com> Thanks, Xiaowei _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Maybe Matching Threads
- [PATCH] VT-d: flush iotlb of selective iommu when a domain''s VT-d table is changed
- [PATCH] vt-d: fix wrong addr in IOTLB invalidation descriptor
- [PATCH][VT] Multithread IDE device model ( was: RE: [PATCH]Make IDE dma tranfer run in another thread inqemu)
- [PATCH] VT-d: IOTLB flush fixups
- [PATCH 0/5] VT-d support for PV guests