From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] xen: release all pages within 1-1 p2m mappings
Date: Thu, 29 Sep 2011 12:29:09 +0100 [thread overview]
Message-ID: <4E845685.9080701@citrix.com> (raw)
In-Reply-To: <1317294517-12614-1-git-send-email-david.vrabel@citrix.com>
Er. This was the wrong patch. I meant to repost "xen: allow extra
memory to be in multiple regions" to remove unnecessary test of
E820_UNUSABLE in xen_align_and_add_e820_region().
Sorry.
David
On 29/09/11 12:08, David Vrabel wrote:
> From: David Vrabel <david.vrabel@citrix.com>
>
> In xen_memory_setup() all reserved regions and gaps are set to an
> identity (1-1) p2m mapping. If an available page has a PFN within one
> of these 1-1 mappings it will become inaccessible (as it MFN is lost)
> so release them before setting up the mapping.
>
> [...]
next prev parent reply other threads:[~2011-09-29 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 16:46 [PATCH 0/5] xen: memory initialization/balloon fixes (#4) David Vrabel
2011-09-28 16:46 ` [PATCH 1/5] xen/balloon: account for pages released during memory setup David Vrabel
2011-09-28 16:46 ` [PATCH 2/5] xen/balloon: simplify test for the end of usable RAM David Vrabel
2011-09-28 16:46 ` [PATCH 3/5] xen: allow balloon driver to use more than one memory region David Vrabel
2011-09-28 16:46 ` [PATCH 4/5] xen: allow extra memory to be in multiple regions David Vrabel
2011-09-29 11:08 ` [PATCH] xen: release all pages within 1-1 p2m mappings David Vrabel
2011-09-29 11:29 ` David Vrabel [this message]
2011-09-29 11:26 ` [PATCH 1/2] xen: allow extra memory to be in multiple regions David Vrabel
2011-09-29 11:26 ` [PATCH 2/2] xen: release all pages within 1-1 p2m mappings David Vrabel
2011-09-28 16:46 ` [PATCH 5/5] " David Vrabel
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=4E845685.9080701@citrix.com \
--to=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).