From: Tristan Gingold <tgingold@free.fr>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com
Subject: Re: Re: [Xen-devel] [PATCH 0/5][IA64][HVM] Windows crashdump support
Date: Tue, 23 Jan 2007 09:25:50 +0100 [thread overview]
Message-ID: <20070123082550.GA2551@saphi> (raw)
In-Reply-To: <C1DB727F.7A77%Keir.Fraser@cl.cam.ac.uk>
On Tue, Jan 23, 2007 at 08:06:23AM +0000, Keir Fraser wrote:
> On 23/1/07 2:40 am, "Masaki Kanno" <kanno.masaki@jp.fujitsu.com> 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.
next prev parent reply other threads:[~2007-01-23 8:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 2:40 [PATCH 0/5][IA64][HVM] Windows crashdump support Masaki Kanno
2007-01-23 2:40 ` [PATCH 1/5][IA64][HVM] Windows crashdump support: Xen common side Masaki Kanno
2007-01-23 2:40 ` [PATCH 2/5][IA64][HVM] Windows crashdump support: Xen arch_ia64 side Masaki Kanno
2007-01-23 2:41 ` [PATCH 3/5][IA64][HVM] Windows crashdump support: Linux " Masaki Kanno
2007-01-23 2:41 ` [PATCH 4/5][IA64][HVM] Windows crashdump support: Tools common side Masaki Kanno
2007-01-23 2:41 ` [PATCH 5/5][IA64][HVM] Windows crashdump support: Tools arch_ia64 side Masaki Kanno
2007-01-23 7:18 ` [Xen-devel] [PATCH 0/5][IA64][HVM] Windows crashdump support Keir Fraser
2007-01-23 7:47 ` Jürgen Groß
2007-01-23 8:00 ` Keir Fraser
2007-01-23 13:58 ` [Xen-ia64-devel] " John Levon
2007-01-23 14:01 ` Keir Fraser
2007-01-23 14:50 ` Re: [Xen-devel] " Masaki Kanno
2007-01-23 8:06 ` Keir Fraser
2007-01-23 8:25 ` Tristan Gingold [this message]
2007-01-23 16:19 ` Re: [Xen-devel] [PATCH 0/5][IA64][HVM] Windowscrashdump support Masaki Kanno
2007-01-23 16:32 ` [Xen-ia64-devel] " Tristan Gingold
2007-01-23 16:36 ` Keir Fraser
2007-01-24 5:04 ` Tristan Gingold
2007-01-24 5:27 ` Re: [Xen-devel] " Masaki Kanno
2007-01-24 7:41 ` [Xen-ia64-devel] " Tristan Gingold
2007-01-24 9:12 ` Re: [Xen-devel] " Masaki Kanno
2007-01-23 8:37 ` [PATCH 0/5][IA64][HVM] Windows crashdump support Masaki Kanno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070123082550.GA2551@saphi \
--to=tgingold@free.fr \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.