xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH 0/5] x86: guest resource mepping
Date: Wed, 2 Aug 2017 10:59:44 +0100	[thread overview]
Message-ID: <20170802095949.40677-1-paul.durrant@citrix.com> (raw)

This series introduces support for direct mapping of guest resources.
Mapping is currently limited to grant tables but support for other resources
will be added by subsequent patches.

Paul Durrant (5):
  arch/[x86|arm]: remove code duplication
  x86/mm: allow a privileged PV domain to map guest mfns
  x86/mm: add HYPERVISOR_memory_op to acquire guest resources
  tools/libxenforeignmemory: add support for resource mapping
  tools/libxenctrl: use new xenforeignmemory API to seed grant table

 tools/include/xen-sys/Linux/privcmd.h              |  11 ++
 tools/libs/foreignmemory/core.c                    |  42 ++++++
 .../libs/foreignmemory/include/xenforeignmemory.h  |  39 ++++++
 tools/libs/foreignmemory/libxenforeignmemory.map   |   5 +
 tools/libs/foreignmemory/linux.c                   |  45 +++++++
 tools/libs/foreignmemory/private.h                 |  30 +++++
 tools/libxc/include/xc_dom.h                       |   8 +-
 tools/libxc/xc_dom_boot.c                          | 102 +++++++++++---
 tools/libxc/xc_sr_restore_x86_hvm.c                |  10 +-
 tools/libxc/xc_sr_restore_x86_pv.c                 |   2 +-
 tools/libxl/libxl_dom.c                            |   1 -
 tools/python/xen/lowlevel/xc/xc.c                  |   6 +-
 xen/arch/arm/mm.c                                  |  29 +---
 xen/arch/x86/mm.c                                  | 150 +++++++++++++++++----
 xen/arch/x86/mm/p2m.c                              |   3 +-
 xen/common/grant_table.c                           |  33 +++++
 xen/include/asm-x86/p2m.h                          |   3 +
 xen/include/public/memory.h                        |  38 +++++-
 xen/include/xen/grant_table.h                      |   3 +
 19 files changed, 467 insertions(+), 93 deletions(-)

-- 
2.11.0


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

             reply	other threads:[~2017-08-02  9:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  9:59 Paul Durrant [this message]
2017-08-02  9:59 ` [PATCH 1/5] [x86|arm]: remove code duplication Paul Durrant
2017-08-02  9:59 ` [PATCH 2/5] x86/mm: allow a privileged PV domain to map guest mfns Paul Durrant
2017-08-02  9:59 ` [PATCH 3/5] x86/mm: add HYPERVISOR_memory_op to acquire guest resources Paul Durrant
2017-08-02  9:59 ` [PATCH 4/5] tools/libxenforeignmemory: add support for resource mapping Paul Durrant
2017-08-04 12:15   ` Wei Liu
2017-08-07 12:41     ` Paul Durrant
2017-08-02  9:59 ` [PATCH 5/5] tools/libxenctrl: use new xenforeignmemory API to seed grant table Paul Durrant
2017-08-04 12:26   ` Wei Liu
2017-08-04 13:02     ` Marek Marczykowski-Górecki
2017-08-04 13:21       ` Wei Liu
2017-08-04 13:39         ` Juergen Gross
2017-08-07 12:36       ` Paul Durrant
2017-08-07 12:35     ` Paul Durrant

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=20170802095949.40677-1-paul.durrant@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=xen-devel@lists.xenproject.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).