xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH 0/2] xen/mem Common cleanup
Date: Wed, 3 Jun 2015 12:43:21 +0100	[thread overview]
Message-ID: <1433331803-1783-1-git-send-email-andrew.cooper3@citrix.com> (raw)

Following c/s e758ed14 which describes the current terms used in Xens memory
management, introduce some infrastructure so that new code can be written
correctly.

This is the start of a long potential cleanup.

Andrew Cooper (2):
  xen/mem: Expose typesafe mfns/gfns/pfns to common code
  xen/vmap: Convert vmap() to using mfn_t

 xen/arch/arm/mm.c              |    8 ++++---
 xen/arch/x86/domain_page.c     |    3 ++-
 xen/arch/x86/mm.c              |    6 +++---
 xen/arch/x86/mm/shadow/multi.c |    6 +++---
 xen/common/vmap.c              |   14 ++++++------
 xen/drivers/acpi/osl.c         |    5 +++--
 xen/include/asm-arm/mm.h       |    2 --
 xen/include/asm-x86/guest_pt.h |    9 --------
 xen/include/asm-x86/mm.h       |   37 --------------------------------
 xen/include/asm-x86/paging.h   |    1 -
 xen/include/xen/mm.h           |   28 ++++++++++++++++++++++++
 xen/include/xen/typesafe.h     |   46 ++++++++++++++++++++++++++++++++++++++++
 xen/include/xen/vmap.h         |    6 +++---
 13 files changed, 100 insertions(+), 71 deletions(-)
 create mode 100644 xen/include/xen/typesafe.h

-- 
1.7.10.4

             reply	other threads:[~2015-06-03 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 11:43 Andrew Cooper [this message]
2015-06-03 11:43 ` [PATCH 1/2] xen/mem: Expose typesafe mfns/gfns/pfns to common code Andrew Cooper
2015-06-03 11:43 ` [PATCH 2/2] xen/vmap: Convert vmap() to using mfn_t Andrew Cooper
2015-06-04 14:00 ` [PATCH 0/2] xen/mem Common cleanup 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=1433331803-1783-1-git-send-email-andrew.cooper3@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --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 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).