[Xen-devel] [PATCH] linux, S3: dom0 doesn't need save ioapic sta

To:	'xen-devel' <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] [PATCH] linux, S3: dom0 doesn't need save ioapic state
From:	"Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date:	Tue, 18 Nov 2008 20:51:13 +0800
Accept-language:	en-US
Acceptlanguage:	en-US
Delivery-date:	Tue, 18 Nov 2008 04:52:04 -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:	AclJfFbMzUxJTp+0S2+iOY8JxYJ64Q==
Thread-topic:	[PATCH] linux, S3: dom0 doesn't need save ioapic state

Dom0 doesn't need to save/restore ioapic state across S3
suspend/resume, as Xen already does it. The more important
is to avoid warnings on some platforms which may have
uninitialized RTEs to be weird value (like smi mode) but
masked. When dom0 saves those entries and then write back
later, it's easy to trigger Xen's sanity check from
ioapic_guest_write.

Signed-off-by Kevin Tian <kevin.tian@xxxxxxxxx>

Thanks,
Kevin

disable_ioapic_suspend.patch
Description: disable_ioapic_suspend.patch

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [PATCH] linux, S3: dom0 doesn't need save ioapic state