WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] SHUTDOWN_suspend

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] SHUTDOWN_suspend
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 17 Jan 2008 17:04:42 +0000
Delivery-date: Thu, 17 Jan 2008 09:04:42 -0800
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
Could someone explain to me the mechanisms by which the
SHUTDOWN_suspend sub-command of SCHEDOP_shutdown is handled?
I am namely having a hard time finding where the non-zero return code
unmodified_drivers/linux-2.6/platform-pci/machine_reboot.c:bp_suspend()
checks for gets injected.

Besides that it puzzles me that this is being used differently by the
pv-on-hvm drivers and the ones on a pv kernel: the latter pass an extra
argument, the consumer of which I again cannot seem to be able to find.
I'm specifically interested if it is valid to replace the pv drivers' use
(through HYPERVISOR_shutdown()) with a call to HYPERVISOR_suspend(),
and whether in that case passing just any value for the 'srec' parameter
is possible.

Thanks, Jan



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

<Prev in Thread] Current Thread [Next in Thread>