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

Re: [Xen-devel] [patch 5/6] frontend device shutdown

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] [patch 5/6] frontend device shutdown
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 22 Aug 2006 09:40:19 +0100
Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: Tue, 22 Aug 2006 01:40:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1107F25.1331%Keir.Fraser@xxxxxxxxxxxx>
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: AcbFxS/ubkuWPDG4EduMfgAKle7CWAAAWk2E
Thread-topic: [Xen-devel] [patch 5/6] frontend device shutdown
User-agent: Microsoft-Entourage/11.2.5.060620
On 22/8/06 9:30 am, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> wrote:

> Two options:
>  1. Always enter Closed state, and then run a cleanup phase in the kexec
> code which iterates over xenstore device directories, switching
> Closed->Initialising.
>  2. Enter state Initialising if backend's 'hotplug_status' node indicates
> 'online'. Gate xenbus_probe_node() on kernel_status <= STATE_RUNNING (the
> shutdown code only ever gets run after kernel_status is bumped to one of the
> shutdown states, I believe).
> 
> I think (1) is architecturally cleaner, but I understand it may be a pain to
> implement in the constrained post-shutdown kexec environment. I don't think
> (2) is too bad, and is more along the lines of what you have already.

I had a chat with Ewan about this. We agree option (2) is sane and likely
much less work than option (1).

 -- Keir



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