From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tim Deegan <tim@xen.org>
Subject: [PATCH 0/5] x86/mm: out-of-memory errors in p2m ops
Date: Thu, 7 Mar 2013 14:52:58 +0000
Message-ID: <1362667983-24938-1-git-send-email-tim@xen.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

These patches begin to address error handling when the shadow/hap
pool can't allocate any more p2m pages.

Patch 1 is a bit of preliminary tidying.
Patch 2 prints a warning on error so it can be diagnosed.
Patches 3-5 add checks to direct callers of the p2m allocation functions.

With these patches applied, pool allocation errors will be
propagated as far as the set_p2m_entry() interface.
Unfortunately there are many callers of that that don't check the
return code -- PoD and mem_paging are the major cuplrits, but
there are other cases where the error is discarded further up the
stack (e.g. some callers of set_mmio_p2m_entry()).  Chasing those
up is work for another day.

Cheers,

Tim.