From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tristan Gingold Subject: Re: [Xen-ia64-devel] Re: [PATCH 0/5][IA64][HVM] Windowscrashdump support Date: Wed, 24 Jan 2007 06:04:19 +0100 Message-ID: <20070124050419.GA2511@saphi> References: <20070123163253.GA4559@saphi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Tristan Gingold , xen-devel@lists.xensource.com, Masaki Kanno , xen-ia64-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Jan 23, 2007 at 04:36:57PM +0000, Keir Fraser wrote: > On 23/1/07 16:32, "Tristan Gingold" wrote: > > >> Maybe os-init is not the best command name as you say. If you have idea > >> of command name, could you send it? > > something like > > xm trigger init|reset|nmi > > This could be acceptable, mapping to a domctl command with type enumeration > argument. Specifying vcpu would indeed make sense. It's not clear that such > a flexible interface would really be needed (maybe xm os-dump would > suffice, mapping to the usual 'hardware dump switch' method for the > particular architecture?) but it's better than 'xm os-init' which I > definitely dislike, and maybe the extra flexibility could turn out to be > useful. For sure this is an export-only command. I don't really like the xm os-dump name, because the action of init/nmi is up to the domain. It may or not dump. Tristan.