From: Tim Deegan <tim@xen.org>
To: xen-devel@lists.xen.org
Subject: [PATCH 0/5] x86/mm: out-of-memory errors in p2m ops
Date: Thu, 7 Mar 2013 14:52:58 +0000 [thread overview]
Message-ID: <1362667983-24938-1-git-send-email-tim@xen.org> (raw)
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.
next reply other threads:[~2013-03-07 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 14:52 Tim Deegan [this message]
2013-03-07 14:52 ` [PATCH 1/5] x86/mm: use bool_t for flags in shadow-pagetable structs Tim Deegan
2013-03-07 14:53 ` [PATCH 2/5] x86/mm: warn if we ever run out of shadow/hap pool for p2m/lgd ops Tim Deegan
2013-03-07 15:22 ` Andrew Cooper
2013-03-07 15:34 ` Jan Beulich
2013-03-07 14:53 ` [PATCH 3/5] x86/ept: check for errors in a few callers of ept_set_entry Tim Deegan
2013-03-07 14:53 ` [PATCH 4/5] x86/mem_sharing: check for errors in p2m->set_entry() Tim Deegan
2013-03-07 15:07 ` Andres Lagar-Cavilla
2013-03-07 16:10 ` Tim Deegan
2013-03-07 16:49 ` Andres Lagar-Cavilla
2013-03-07 14:53 ` [PATCH 5/5] x86/mem_access: " Tim Deegan
2013-03-07 21:50 ` Aravindh Puthiyaparambil
2013-03-07 15:38 ` [PATCH 0/5] x86/mm: out-of-memory errors in p2m ops Jan Beulich
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=1362667983-24938-1-git-send-email-tim@xen.org \
--to=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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.