From: Tim Deegan <Tim.Deegan@citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 00 of 13] [RFC] p2m cleanups
Date: Fri, 13 May 2011 17:28:42 +0100 [thread overview]
Message-ID: <patchbomb.1305304122@whitby.uk.xensource.com> (raw)
This series is the current state of my p2m cleanups; it passes
basic smoke-tests but needs more serious testing before it's
ready to go in. I'm posting it as an RFC for now so anyone who's
interested in it can see the way things are going and maybe even
give feedback before I get too far down this particular rabbit-hole.
So far, it:
- fixes a lot of locking bugs
- tidies up the p2m interface, mostly to stop the callers needing to know
about internal p2m cruft.
- collects all the x86/mm locks together, defining and enforcing a
locking order.
Next stages:
- Fix the ugly "need_lock" semi-recursive locking.
- Fix the idiom where many callers of gfn_to_mfn_* immediately
have to page in or unshare the result by moving that logic
into p2m code and requesting it with a flag.
- Disentangle the page allocators from hap and shadow, and put them
under their own lock, which will allow me to undo some of the
contortions the log-dirty code goes to when allocating memory.
- Sort out the interactions between nested HAP and memory
sharing/paging.
After all that (phew!) I should be in a position to look at
integrating the p2m code and the core typecounting code better,
to avoid the TOCTOU races that have been pointed out in the
memory sharing code.
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
next reply other threads:[~2011-05-13 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 16:28 Tim Deegan [this message]
2011-05-13 16:28 ` [PATCH 01 of 13] x86/mm/p2m: Mark internal functions static Tim Deegan
2011-05-13 16:28 ` [PATCH 02 of 13] x86/mm/p2m: little fixes and tidying up Tim Deegan
2011-05-13 16:28 ` [PATCH 03 of 13] x86/mm/p2m: hide the current-domain fast-path inside the p2m-pt code Tim Deegan
2011-05-13 16:28 ` [PATCH 04 of 13] x86/mm/p2m: merge gfn_to_mfn_unshare with other gfn_to_mfn paths Tim Deegan
2011-05-13 16:28 ` [PATCH 05 of 13] x86/mm/p2m: Make p2m interfaces take struct domain arguments Tim Deegan
2011-05-13 16:28 ` [PATCH 06 of 13] x86/mm/p2m: paging_p2m_ga_to_gfn() doesn't need so many arguments Tim Deegan
2011-05-13 16:28 ` [PATCH 07 of 13] x86/mm: Fix memory-sharing code's locking discipline Tim Deegan
2011-05-13 16:28 ` [PATCH 08 of 13] x86/mm/p2m: Remove recursive-locking code from set_shared_p2m_entry() Tim Deegan
2011-05-13 16:28 ` [PATCH 09 of 13] x86/mm/p2m: Fix locking discipline around p2m updates Tim Deegan
2011-05-13 16:28 ` [PATCH 10 of 13] x86/mm/p2m: Fix locking discipline around p2m lookups Tim Deegan
2011-05-13 16:28 ` [PATCH 11 of 13] x86/mm/p2m: Move p2m code in HVMOP_[gs]et_mem_access into p2m.c Tim Deegan
2011-05-13 16:28 ` [PATCH 12 of 13] x86/mm/p2m: Fix locking discipline around log-dirty teardown Tim Deegan
2011-05-13 16:28 ` [PATCH 13 of 13] x86/mm: dedup the various copies of the shadow lock functions Tim Deegan
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=patchbomb.1305304122@whitby.uk.xensource.com \
--to=tim.deegan@citrix.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).