[Xen-devel] [PATCH] VT-d: get rid of hardcode in iommu_flush_cac

To:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] [PATCH] VT-d: get rid of hardcode in iommu_flush_cache_entry
From:	"Han, Weidong" <weidong.han@xxxxxxxxx>
Date:	Wed, 2 Dec 2009 13:35:36 +0800
Accept-language:	en-US
Acceptlanguage:	en-US
Cc:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date:	Tue, 01 Dec 2009 21:36:33 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcpzEUZ3bbQ9zHo+QbaLAuFZcR3Orw==
Thread-topic:	[Xen-devel] [PATCH] VT-d: get rid of hardcode in iommu_flush_cache_entry

Currently iommu_flush_cache_entry uses a fixed size 8 bytes to flush cache. But 
it also needs to flush caches with different sizes, e.g. struct root_entry is 
16 bytes. This patch fixes the hardcode by using a parameter "size" to flush 
caches with different sizes.

Signed-off-by: Weidong Han <weidong.han@xxxxxxxxx>

fix-hardcode.patch
Description: fix-hardcode.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [PATCH] VT-d: get rid of hardcode in iommu_flush_cache_entry