[Xen-devel][PATCH] Fix the boot failure of xenU after destroying

To:	"Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel][PATCH] Fix the boot failure of xenU after destroying a HVM guest
From:	"Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>
Date:	Thu, 26 Jun 2008 14:12:00 +0800
Cc:	jbeulich@xxxxxxxxxx
Delivery-date:	Wed, 25 Jun 2008 23:12:35 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcjXU4t4qffyMQQSR5e4ylNJCskyHQ==
Thread-topic:	[Xen-devel][PATCH] Fix the boot failure of xenU after destroying a HVM guest

Fix the boot failure of xenU after destroying a HVM guest.
- Both page_info and shadow_page_info are stored in frame_table. 
At first, all spin locks in frame table are initialized as
SPIN_LOCK_UNLOCKED. 
If one frame is used as shadow_page_info, we still should initialize the
spin lock to be SPIN_LOCK_UNLOCKED when freeing that page.

Signed-off-by: Dongxiao Xu <dongxiao.xu@xxxxxxxxx>

Best Regards,
-- Dongxiao

init_spinlock.patch
Description: init_spinlock.patch

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel][PATCH] Fix the boot failure of xenU after destroying a HVM g