All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: capturing windows crash dumps
Date: Wed, 19 Aug 2009 11:38:39 +0100	[thread overview]
Message-ID: <4A8BD62F.20902@citrix.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0177CCC1@trantor>

James Harper wrote:
> 
> The more I look into it the less fond I get of this idea... I already
> use the serial line for other things.
> 
> What about an event channel and a page of memory that could be retrieved
> via the existing hvm_get_param mechanism for HVM domains and part of the
> start_info page for PV domains? (just like store_mfn and store_evtchn
> etc).
> 

What about a 2nd serial line?

-- 
===============================
Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom

TEL: x35957 (+44 1223 225957)
===============================

  reply	other threads:[~2009-08-19 10:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  6:47 capturing windows crash dumps James Harper
2009-08-18  7:54 ` Keir Fraser
2009-08-18 10:42   ` James Harper
2009-08-18 12:10     ` Keir Fraser
2009-08-18 12:16       ` James Harper
2009-08-18 13:47         ` Stefano Stabellini
2009-08-18 23:53           ` James Harper
2009-08-19 10:28       ` James Harper
2009-08-19 10:38         ` Paul Durrant [this message]
2009-08-19 13:34           ` Stefano Stabellini
2009-08-19 13:35         ` Konrad Rzeszutek Wilk
2009-08-19 13:47           ` Paul Durrant
2009-08-20  9:56             ` James Harper
2009-08-20 10:22               ` Keir Fraser

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=4A8BD62F.20902@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-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.