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: "Iomem mapping not permitted" during windows crash dump under GPLPV
Date: Tue, 2 Feb 2010 11:02:58 +0000	[thread overview]
Message-ID: <4B680662.1060201@citrix.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01898F42@trantor>

James Harper wrote:
>> Keir Fraser wrote:
>>> On 30/01/2010 08:30, "James Harper" <james.harper@bendigoit.com.au>
> wrote:
>>>> So there is definitely nothing I could tell Xen to do with a DomU
> PFN
>>>> that would remove the p2m mapping?
>>> If you balloon out a page, that would do it.
>>>
>> Yes, it certainly would and I've seen it many times. I'm fairly sure
>> that by just ignoring the failed block writes coming back from
>> blkback/tap and carrying on you still end up with a usable MEMORY.DMP
>> after reboot.
>>
> 
> Yes, that works. I still eye the error messages with contempt though :)
> 

If you wanted to be clean, I guess you could check the data buffer addr 
passed to you by Windows against a map of ballooned out pages and 
substitute a dummy buffer in this case... but then you have the 
'interesting' problem of making the dump driver aware of that map.

   Paul

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

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

  reply	other threads:[~2010-02-02 11:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30  5:26 "Iomem mapping not permitted" during windows crash dump under GPLPV James Harper
2010-01-30  8:23 ` Keir Fraser
2010-01-30  8:30   ` James Harper
2010-01-30  9:33     ` Keir Fraser
2010-02-02 10:24       ` Paul Durrant
2010-02-02 10:47         ` James Harper
2010-02-02 11:02           ` Paul Durrant [this message]
2010-02-02 11:07             ` James Harper
2010-02-02 11:27               ` Jan Beulich
2010-02-02 13:30                 ` Keir Fraser
2010-02-02 13:58                   ` Tim Deegan
2010-02-02 16:54                     ` Paul Durrant
2010-02-02 17:15                       ` Tim Deegan
2010-02-02 18:08                         ` Paul Durrant
2010-02-02 22:01                     ` "Iomem mapping not permitted" during windows crashdump " James Harper
2010-02-02 14:26                   ` "Iomem mapping not permitted" during windows crash dump " Jan Beulich
2010-02-02 14:33                     ` Keir Fraser
2010-02-02 20:32                     ` Steven Smith
2010-02-02 21:57                       ` James Harper
2010-02-02 11:34               ` Paul Durrant
2010-02-02 11:41                 ` James Harper

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=4B680662.1060201@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.