xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tamas K Lengyel <tklengyel@sec.in.tum.de>
To: xen-devel@lists.xen.org
Cc: tim@xen.org, dgdegra@tycho.nsa.gov,
	stefano.stabellini@citrix.com, ian.campbell@citrix.com,
	Tamas K Lengyel <tklengyel@sec.in.tum.de>
Subject: [PATCH for-4.5 v12 0/3] Refactoring for future mem_event and mem_access support on ARM
Date: Mon, 29 Sep 2014 17:55:10 +0200	[thread overview]
Message-ID: <1412006113-31551-1-git-send-email-tklengyel@sec.in.tum.de> (raw)

These patches are the refactoring and minor patches that will be required
for future mem_access support on ARM that could be merged now.

This PATCH series is also available at:
https://github.com/tklengyel/xen/tree/arm_memaccess_12-for-4.5

Julien Grall (1):
  xen/arm: Implement domain_get_maximum_gpfn

Tamas K Lengyel (2):
  xen/xsm: Wrap mem_access blocks into HAS_MEM_ACCESS ifdefs
  xen/arm: Add p2m_set_permission and p2m_shatter_page helpers.

 xen/arch/arm/mm.c       |   2 +-
 xen/arch/arm/p2m.c      | 137 +++++++++++++++++++++++++++++++++---------------
 xen/include/xsm/dummy.h |  26 ++++-----
 xen/include/xsm/xsm.h   |  29 +++++-----
 xen/xsm/dummy.c         |   7 ++-
 xen/xsm/flask/hooks.c   |  33 +++++++-----
 6 files changed, 151 insertions(+), 83 deletions(-)

-- 
2.1.0

             reply	other threads:[~2014-09-29 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 15:55 Tamas K Lengyel [this message]
2014-09-29 15:55 ` [PATCH for-4.5 v12 1/3] xen/xsm: Wrap mem_access blocks into HAS_MEM_ACCESS ifdefs Tamas K Lengyel
2014-09-29 15:55 ` [PATCH for-4.5 v12 2/3] xen/arm: Implement domain_get_maximum_gpfn Tamas K Lengyel
2014-09-29 15:55 ` [PATCH for-4.5 v12 3/3] xen/arm: Add p2m_set_permission and p2m_shatter_page helpers Tamas K Lengyel
2014-10-01 10:59 ` [PATCH for-4.5 v12 0/3] Refactoring for future mem_event and mem_access support on ARM Ian Campbell
2014-10-02 15:50   ` Konrad Rzeszutek Wilk
2014-10-06 13:50     ` Ian Campbell

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=1412006113-31551-1-git-send-email-tklengyel@sec.in.tum.de \
    --to=tklengyel@sec.in.tum.de \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=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 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).