From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tristan Gingold Subject: Re: Re: [Xen-devel] [PATCH 0/5][IA64][HVM] Windows crashdump support Date: Tue, 23 Jan 2007 09:25:50 +0100 Message-ID: <20070123082550.GA2551@saphi> References: <61C73E97DDED6Akanno.masaki@jp.fujitsu.com> 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-ia64-devel-bounces@lists.xensource.com Errors-To: xen-ia64-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Jan 23, 2007 at 08:06:23AM +0000, Keir Fraser wrote: > On 23/1/07 2:40 am, "Masaki Kanno" wrote: > > > In the ia64 machine, there is an INIT switch. By pushing the > > INIT switch, an INIT interruption is generated. The INIT > > interruption triggers off when the Windows collects the > > crashdump. (I attach a screenshot of the Windows crashdump.) > > Does ia64 Windows generate a dump if you send it an NMI? That would be a > more generic mechanism that would allow x86 HVM to share the same domctl or > hvm_op. Otherwise we need a send_init hypercall for ia64 and a send_nmi > hypercall for x86, or we need a more vague generic name like > "trigger_dump_switch" (which actually is rather attractive now I think about > it). I support the feature too. I think being able to post an NMI/INIT is a good feature. It allows you to test the feature if your bare hardware don't have it. Maybe os-init is not the best name. Maybe the balance between code in hypervisor (very small) and code in xm (larger) is not very good, but difficule to improve ! Tristan.