From: Dushyant Behl <myselfdushyantbehl@gmail.com>
To: Xen Devel <xen-devel@lists.xen.org>
Cc: David Scott <dave.scott@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Andres Lagar Cavilla <andres.lagarcavilla@gmail.com>,
Dushyant Behl <myselfdushyantbehl@gmail.com>
Subject: Re: Refactoring mempaging code from xenpaging to libxc and few updates
Date: Wed, 13 Aug 2014 21:58:37 +0530 [thread overview]
Message-ID: <CAHF350LJOsz73kWMmtGUajegps-76mWMb+agPtwGynp-71wAVg@mail.gmail.com> (raw)
In-Reply-To: <1407444012-31830-1-git-send-email-myselfdushyantbehl@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1495 bytes --]
Hi Everyone,
I am extremely sorry that I didn't notice these patches had most of the
code which did exactly what xc_mem_event_enable (added by XSA-99) did.
I request you to kindly ignore this patch series, I have prepared a new
patch series which takes some necessary bits and pieces from this patch
series and adds them to xc_mem_event_enable.
I'll be sending the new patch series, Please have a look at those.
I am really sorry for the inconvenience.
Thanks and Regards,
Dushyant Behl
On Fri, Aug 8, 2014 at 2:10 AM, Dushyant Behl <myselfdushyantbehl@gmail.com>
wrote:
> The following patches refactor memepaging code from xenpaging to libxc -
>
> [PATCH v3 1/3] tools/libxc: refactored mempaging code from xenpaging
> This patch adds two routines xc_mem_paging_ring_setup and
> xc_mem_paging_ring_teardown to libxc at the path
> tools/libxc/xc_mem_paging_setup.c, which is a new file.
>
> [PATCH v3 2/3] tools/libxc/xc_mem_paging_setup.c: replacing deprecated
> functions
> Replaces calls to deprecated function xc_map_foreign_batch with calls to
> xc_map_foreign_bulk.
>
> [PATCH v3 3/3] tools/libxc/xc_mem_paging_setup.c: FIX- Race condition
> Fix for a known race condition bug in mempaging ring setup code, this race
> condition is actually simmilar to that concerned by XSA-99. This patch
> tries to
> take care of all the points mentioned in XSA-99, along with clearing the
> ringpage
> to remove any bogus input.
>
> Signed-off-by: Dushyant Behl <myselfdushyantbehl@gmail.com>
>
[-- Attachment #1.2: Type: text/html, Size: 2031 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-08-13 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 20:40 Refactoring mempaging code from xenpaging to libxc and few updates Dushyant Behl
2014-08-07 20:40 ` [PATCH v3 1/3] tools/libxc: refactored mempaging code from xenpaging to libxc Dushyant Behl
2014-08-07 20:40 ` [PATCH v3 2/3] tools/libxc/xc_mem_paging_setup.c: replacing deprecated function calls Dushyant Behl
2014-08-07 20:40 ` [PATCH v3 3/3] tools/libxc/xc_mem_paging_setup.c: FIX- Race condition between initializing shared ring and mempaging Dushyant Behl
2014-08-08 2:37 ` Andres Lagar Cavilla
2014-08-13 16:28 ` Dushyant Behl [this message]
2014-08-13 20:54 ` Refactoring mempaging code from xenpaging to libxc and few updates 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=CAHF350LJOsz73kWMmtGUajegps-76mWMb+agPtwGynp-71wAVg@mail.gmail.com \
--to=myselfdushyantbehl@gmail.com \
--cc=andres.lagarcavilla@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=dave.scott@eu.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).