xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Aravindh Puthiyaparambil <aravindp@cisco.com>
To: xen-devel@lists.xenproject.org
Cc: Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Jan Beulich <jbeulich@suse.com>
Subject: [PATCH RFC 0/2] Make mem_access APIs and hypercalls generic
Date: Tue,  8 Apr 2014 22:50:05 -0700	[thread overview]
Message-ID: <1397022607-1704-1-git-send-email-aravindp@cisco.com> (raw)

This is a precusor patch to the one that enables mem_access for PV domains.

The mem_access APIs, hypercalls and structures all have HVM specific naming. As 
a first step to making this work for PV domains, this patch renames them in a more 
generic fashion. 

Signed-off-by: Aravindh Puthiyaparambil <aravindp@cisco.com>
Cc: Keir Fraser <keir@xen.org>
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>

---

The main reason for the RFC is that I am not sure if I am doing the hypercall 
preemption continuation correctly. Please take a look and let me know how I 
should proceed. 
          
Thanks,
Aravindh

  x86/mem_access: Make the mem_access ops generic
  tools/libxc: Make the mem_access APIs generic

 tools/libxc/xc_mem_access.c      | 57 ++++++++++++++++++++++++++++---
 tools/libxc/xc_misc.c            | 60 +++++----------------------------
 tools/libxc/xenctrl.h            | 18 ++++++++++
 xen/arch/x86/hvm/hvm.c           | 73 ++--------------------------------------
 xen/arch/x86/mm/mem_access.c     | 68 +++++++++++++++++++++++++++++++++++--
 xen/arch/x86/mm/mem_event.c      |  3 --
 xen/arch/x86/mm/p2m.c            | 34 +++++++++----------
 xen/arch/x86/x86_64/compat/mm.c  |  7 +++-
 xen/arch/x86/x86_64/mm.c         |  7 +++-
 xen/include/asm-x86/mem_access.h |  2 +-
 xen/include/asm-x86/p2m.h        |  6 ++--
 xen/include/public/hvm/hvm_op.h  | 50 +++++++++++++--------------
 xen/include/public/memory.h      | 53 +++++++++++++++++++++++++++--
 13 files changed, 251 insertions(+), 187 deletions(-)

-- 
1.8.3.2

             reply	other threads:[~2014-04-09  5:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09  5:50 Aravindh Puthiyaparambil [this message]
2014-04-09  5:50 ` [PATCH RFC 1/2] x86/mem_access: Make the mem_access ops generic Aravindh Puthiyaparambil
2014-04-09  8:53   ` Jan Beulich
2014-04-10  0:39     ` Aravindh Puthiyaparambil (aravindp)
2014-04-10  6:17       ` Jan Beulich
2014-04-09  5:50 ` [PATCH RFC 2/2] tools/libxc: Make the mem_access APIs generic Aravindh Puthiyaparambil
2014-04-09  8:23   ` Ian Campbell
2014-04-09  8:58     ` Jan Beulich
2014-04-09  9:06       ` Ian Campbell
2014-04-10  0:43         ` Aravindh Puthiyaparambil (aravindp)
2014-04-10  0:43     ` Aravindh Puthiyaparambil (aravindp)

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=1397022607-1704-1-git-send-email-aravindp@cisco.com \
    --to=aravindp@cisco.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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).