From: Paul Durrant <paul.durrant@citrix.com>
To: Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
James Harper <james.harper@bendigoit.com.au>,
Keir Fraser <Keir.Fraser@eu.citrix.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: "Iomem mapping not permitted" during windows crash dump under GPLPV
Date: Tue, 2 Feb 2010 16:54:11 +0000 [thread overview]
Message-ID: <4B6858B3.2000808@citrix.com> (raw)
In-Reply-To: <20100202135820.GA7099@whitby.uk.xensource.com>
Tim Deegan wrote:
>
> What's the problem with just ignoring the errors when a frontend page
> doesn't exist, though?
>
I think the only problem is the noise really. I guess it would be nice
if we can spot an attempt to grant map a ballooned out page and maybe
not emit the warning messages in that case.
Paul
--
===============================
Paul Durrant, Software Engineer
Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom
===============================
next prev parent reply other threads:[~2010-02-02 16:54 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
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 [this message]
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=4B6858B3.2000808@citrix.com \
--to=paul.durrant@citrix.com \
--cc=JBeulich@novell.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=Tim.Deegan@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.