From: Keir Fraser <keir@xensource.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com,
"Jürgen Groß " <juergen.gross@fujitsu-siemens.com>,
"Masaki Kanno" <kanno.masaki@jp.fujitsu.com>,
xen-ia64-devel@lists.xensource.com
Subject: Re: [Xen-ia64-devel] Re: [PATCH 0/5][IA64][HVM] Windows crashdump support
Date: Tue, 23 Jan 2007 14:01:26 +0000 [thread overview]
Message-ID: <C1DBC5B6.812D%keir@xensource.com> (raw)
In-Reply-To: <20070123135836.GA1639@totally.trollied.org.uk>
On 23/1/07 13:58, "John Levon" <levon@movementarian.org> wrote:
>> If that's the aim then perhaps the xm command should be given a better name.
>> 'xm os-init' is rather meaningless outside the context of physical INIT
>> buttons on ia64 systems -- not a very generic concept to export to a VM
>> management tool! Perhaps 'xm os-dump' with a guest-specific backend
>> implementation in xend (default to fail with an error message).
>
> I'd like to see a generic command that encompasses both os-init and
> sysrq. We support sysrq 'b' but feel a bit silly having that command
> name. Ideally we'd hide (but still support) 'xm sysrq' too.
Given that some of this is OS and/or arch specific, it may be hard to
concoct general names. At least the concept of a hardware 'dump switch' is
fairly well known, even if the implementation differs a bit across
architectures. I suppose we could provide better names for some of the more
useful Linux sysrq commands, provide a better / more general interface to
them (both at the xm level and the xenbus level) and encourage other PV
guests to support the new interface.
-- Keir
next prev parent reply other threads:[~2007-01-23 14:01 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 [this message]
2007-01-23 14:50 ` Re: [Xen-devel] " Masaki Kanno
2007-01-23 8:06 ` Keir Fraser
2007-01-23 8:25 ` Tristan Gingold
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=C1DBC5B6.812D%keir@xensource.com \
--to=keir@xensource.com \
--cc=juergen.gross@fujitsu-siemens.com \
--cc=kanno.masaki@jp.fujitsu.com \
--cc=levon@movementarian.org \
--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.