[PATCH 0/5] xen: memory initialization/balloon fixes (#4)

[David Vrabel <david.vrabel@citrix.com>]

This set of patches fixes some bugs in the memory initialization under
Xen and in Xen's memory balloon driver.  They can make 100s of MB of
additional RAM available (depending on the system/configuration).

Patch 1 is a bug fix and sould be queued for 3.1 and possibly queued
for the 3.0 stable tree.

Patch 2 is a minor cleanup in the balloon driver. Please queue for
3.2.

Patches 3 & 4 increase the amount of low memory in 32 bit domains
started with < 1 GiB of RAM.  Please queue for 3.2

Patch 5 releases all pages in the initial allocation with PFNs that
lie within a 1-1 mapping.  This seems correct to me as I think that
once the 1-1 mapping is set the MFN of the original page is lost so
it's no longer accessible by the kernel (and it cannot be used by
another domain).

Changes since #3:

- Dropped the two patches that have already been applied.

- Fixed an endless loop on systems with non-page aligned RAM regions.

- Updated "xen: release all pages within 1-1 p2m mappings" to handle
  adjacent non-RAM regions better (particularly ones less than a page)
  and to round them so partial pages are included in the 1:1 p2m map
  (this should fix the dmidecode problem on systems with a DMI table
  on a non-page boundary).

David