xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Lai <paul.c.lai@intel.com>
To: xen-devel@lists.xensource.com
Cc: ravi.sahita@intel.com, george.dunlap@citrix.com, jbeulich@suse.com
Subject: [PATCH Altp2m cleanup v5 0/3] Cleaning up altp2m code
Date: Tue, 13 Sep 2016 09:46:02 -0700	[thread overview]
Message-ID: <1473785165-11137-1-git-send-email-paul.c.lai@intel.com> (raw)

Altp2m cleanup work

The altp2m clean work is motivated by the following URLs:
   https://lists.xenproject.org/archives/html/xen-devel/2015-07/msg04323.html
   https://lists.xenproject.org/archives/html/xen-devel/2015-07/msg04454.html
   https://lists.xenproject.org/archives/html/xen-devel/2015-07/msg04530.html

Most of the work has been:
Lots of white space, indentation, and other coding style preference
corrections.
Lots of moving altp2m functions to the altp2m file.
Lots of moving ept functions to the ept file.
Lots of function return type corrections (and checking).
Better sanity checking of values before processing in do_altp2m_op().
Just using 'return' after a if() clause instead of using a goto
if the block is can be a one liner.

Most importantly here, we help submit Ravi Sahita's dynamically allocated
altp2m domain for struct p2m.  Also, Ravi introduces set_altp2m_active()
and altp2m_active() APIs for better readability and maintainability.

Along the way, some dependencies have broken and we've waited for them
to be fixed.  Most recently the gfn() which caused a hang of the whole system.
The gfn fixes are currently in staging. We've have verified against the
staging branch that this series of patches functions as expected.

Paul Lai (3):
  altp2m cleanup work.
  Move altp2m specific functions to altp2m files.
  Making altp2m domain dynamically allocated.

 xen/arch/x86/hvm/hvm.c            |  54 +++++++++----------
 xen/arch/x86/hvm/vmx/vmx.c        |   2 +-
 xen/arch/x86/mm/altp2m.c          |  57 ++++++++++++++++++++
 xen/arch/x86/mm/hap/hap.c         |  38 ++++----------
 xen/arch/x86/mm/mem_sharing.c     |   2 +-
 xen/arch/x86/mm/mm-locks.h        |   4 +-
 xen/arch/x86/mm/p2m-ept.c         |  39 ++++++++++++++
 xen/arch/x86/mm/p2m.c             | 106 +++++++++++++-------------------------
 xen/common/monitor.c              |   1 +
 xen/include/asm-x86/altp2m.h      |  11 +++-
 xen/include/asm-x86/domain.h      |   6 +--
 xen/include/asm-x86/hvm/hvm.h     |  22 ++++++--
 xen/include/asm-x86/hvm/vmx/vmx.h |   3 ++
 xen/include/asm-x86/p2m.h         |  18 ++++---
 14 files changed, 216 insertions(+), 147 deletions(-)

-- 
2.7.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2016-09-13 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 16:46 Paul Lai [this message]
2016-09-13 16:46 ` [PATCH Altp2m cleanup v5 1/3] altp2m cleanup work Paul Lai
2016-09-26 16:01   ` Jan Beulich
2016-09-26 17:25     ` Lai, Paul
2016-09-13 16:46 ` [PATCH Altp2m cleanup v5 2/3] Move altp2m specific functions to altp2m files Paul Lai
2016-09-13 16:46 ` [PATCH Altp2m cleanup v5 3/3] Making altp2m domain dynamically allocated Paul Lai

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=1473785165-11137-1-git-send-email-paul.c.lai@intel.com \
    --to=paul.c.lai@intel.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=ravi.sahita@intel.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).