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 3 of 7] Make suspend return 1 when a domain is re

To: Brendan Cully <brendan@xxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 3 of 7] Make suspend return 1 when a domain is resumed
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 19 Jan 2007 17:09:23 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 Jan 2007 09:09:03 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070119163651.GA11597@xxxxxxxxxxxxxxxxx>
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: Acc77JC9z4WaRKffEduuowAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH 3 of 7] Make suspend return 1 when a domain is resumed
User-agent: Microsoft-Entourage/11.2.5.060620
On 19/1/07 16:36, "Brendan Cully" <brendan@xxxxxxxxx> wrote:

> sorry, that was a bad comment. I'd been using "resume" to mean
> suspend-cancel and "reconnect" to mean run in a new domain. This patch
> is the backwards compatible version (it sets EAX to 1 in xc_linux_save
> rather than xc_linux_restore).

Oh, I see. Makes sense.

> I poked around the elfnote route for advertising kernel features to
> xend, and I have a feeling someone else should be designing the API
> for that - I only want very little out of it and would probably be
> shortsighted. For instance, it wasn't clear to me whether it'd be
> better to have an xc function that returns almost raw elfnotes (an
> array of (type, length, contents)) or only parsed, named elfnotes, or
> only features.

The xenctrl function that pulls out the elfnote info is going to need to
know about specific elfnotes, the type of contents, and have a sensible
strategy for stringifying them. I suggest (type, contents) pairs where type
is the elfnote type name, and contents is content-specific string. There are
lots of elfnotes so you only need worry about the elfnote you care about
(your new one) -- all I want is a framework where we can extract more
elfnotes as and when we need to.

 -- Keir


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