xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dushyant Behl <myselfdushyantbehl@gmail.com>
To: xen-devel@lists.xen.org
Cc: David Scott <dave.scott@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Andres Lagar Cavilla <andres.lagarcavilla@gmail.com>,
	Dushyant Behl <myselfdushyantbehl@gmail.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH v0 0/3] Modifications to mem_event_enable API and addition of teardown routine.
Date: Thu, 14 Aug 2014 02:21:37 +0530	[thread overview]
Message-ID: <1407963100-18796-1-git-send-email-myselfdushyantbehl@gmail.com> (raw)

This patch series is the corrected version of the following patch series,
http://lists.xenproject.org/archives/html/xen-devel/2014-08/msg00847.html
http://lists.xenproject.org/archives/html/xen-devel/2014-08/msg00848.html
http://lists.xenproject.org/archives/html/xen-devel/2014-08/msg00846.html
http://lists.xenproject.org/archives/html/xen-devel/2014-08/msg00849.html

The previous patch series had some code which was actually present in the tree
after addition of XSA-99. Please ignore the older patch series and have a look
at this patch series.

[PATCH v0 1/3] mem_access: modifications to mem_event enable API.
This patch modifies the xc_mem_event_enable API by -
 1. adding shared ring init.
 2. clearing ring page.
 3. replacing calls to deprecated API's.
 4. updating the xc_mem_event_enable API to have simmilar signature with other
    mem_event API's (This was my personal choice and is certainly debatable).

[PATCH v0 2/3] mem_event: Added new helper API to teardown mem event and unmap ring_page.
This patch adds a new xc_mem_event_teardown API to teardown the mem event setup
for the PAGING, ACCESS and SHARING HVM params.

[PATCH v0 3/3] xenpaging: updated code to use safer mem_event API's for setup and teardown.
This patch simply updates the code to use the newly created API's.

Signed-off-by: Dushyant Behl <myselfdushyantbehl@gmail.com>

             reply	other threads:[~2014-08-13 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 20:51 Dushyant Behl [this message]
2014-08-13 20:51 ` [PATCH v0 1/3] mem_access: modifications to mem_event enable API Dushyant Behl
     [not found]   ` <CAGU+auvmQOWp8VH5bt+yh55iyJxLOV6Hd8ZfvAsdyuOOZ3fBNQ@mail.gmail.com>
2014-08-22 22:05     ` Aravindh Puthiyaparambil (aravindp)
2014-08-25  0:16       ` Dushyant Behl
2014-08-25 17:48         ` Aravindh Puthiyaparambil (aravindp)
2014-08-26 17:50       ` Ian Campbell
2014-08-13 20:51 ` [PATCH v0 2/3] mem_event: Added new helper API to teardown mem event setup and unmap ring_page Dushyant Behl
     [not found]   ` <CAGU+auudSP7mXfGzMzhDm4WkwS7icGy_rFCAWHhN85xe_pF=Og@mail.gmail.com>
2014-08-22 22:24     ` Aravindh Puthiyaparambil (aravindp)
2014-08-13 20:51 ` [PATCH v0 3/3] xenpaging: updated code to use safer mem_event API's for setup and teardown Dushyant Behl

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=1407963100-18796-1-git-send-email-myselfdushyantbehl@gmail.com \
    --to=myselfdushyantbehl@gmail.com \
    --cc=andres.lagarcavilla@gmail.com \
    --cc=dave.scott@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.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).