xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jean Guyader <jean.guyader@citrix.com>
To: xen-devel@lists.xen.org
Cc: Jean Guyader <jean.guyader@citrix.com>
Subject: [PATCH 0/5] RFC: V4V (v3)
Date: Fri, 3 Aug 2012 20:50:49 +0100	[thread overview]
Message-ID: <1344023454-31425-1-git-send-email-jean.guyader@citrix.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]

v3 changes:
        - Switch to event channel
                - Allocated a unbound event channel
                  per domain.
                - Add a new v4v call to share the
                  event channel port.
        - Public headers with actual type definition
        - Align all the v4v type to 64 bits
        - Modify v4v MAGIC numbers because we won't
          but backward compatible anymore
        - Merge insert and insertv
        - Merge send and sendv
        - Turn all the lock prerequisite from comment
          to ASSERT()
        - Make use or write_atomic instead of volatile pointers
        - Merge v4v_memcpy_to_guest_ring and
          v4v_memcpy_to_guest_ring_from_guest
                - Introduce copy_from_guest_maybe that can take
                  a void * and a handle as src address.
        - TODO:
                - Add libv4v userspace code

v2 changes:
        - Cleanup plugin header
        - Include basic access control
        - Use guest_handle_for_field


Jan Beulich (1):
  xen: Introduce guest_handle_for_field

Jean Guyader (4):
  xen: add ssize_t
  xen: virq, remove VIRQ_XC_RESERVED
  xen: events, exposes evtchn_alloc_unbound_domain
  xen: Add V4V implementation

 xen/arch/x86/hvm/hvm.c             |    9 +-
 xen/arch/x86/x86_32/entry.S        |    2 +
 xen/arch/x86/x86_64/compat/entry.S |    2 +
 xen/arch/x86/x86_64/entry.S        |    2 +
 xen/common/Makefile                |    1 +
 xen/common/domain.c                |   13 +-
 xen/common/event_channel.c         |   33 +-
 xen/common/v4v.c                   | 1895 ++++++++++++++++++++++++++++++++++++
 xen/include/asm-arm/types.h        |    1 +
 xen/include/asm-x86/guest_access.h |    3 +
 xen/include/asm-x86/types.h        |    6 +
 xen/include/public/v4v.h           |  291 ++++++
 xen/include/public/xen.h           |    3 +-
 xen/include/xen/event.h            |    2 +
 xen/include/xen/sched.h            |    4 +
 xen/include/xen/v4v.h              |  134 +++
 xen/include/xen/v4v_utils.h        |  276 ++++++
 17 files changed, 2665 insertions(+), 12 deletions(-)
 create mode 100644 xen/common/v4v.c
 create mode 100644 xen/include/public/v4v.h
 create mode 100644 xen/include/xen/v4v.h
 create mode 100644 xen/include/xen/v4v_utils.h

-- 
1.7.9.5


[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

             reply	other threads:[~2012-08-03 19:50 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 19:50 Jean Guyader [this message]
2012-08-03 19:50 ` [PATCH 1/5] xen: add ssize_t Jean Guyader
2012-08-06  8:08   ` Jan Beulich
2012-08-06 14:47     ` Jean Guyader
2012-08-09  9:51       ` Tim Deegan
2012-08-09 10:19         ` Jean Guyader
2012-08-09 10:39           ` Jan Beulich
2012-08-09 10:48             ` Jean Guyader
2012-08-09 13:02               ` Jan Beulich
2012-08-09 10:59           ` Tim Deegan
2012-08-09 11:08             ` Jean Guyader
2012-08-03 19:50 ` [PATCH 2/5] xen: Introduce guest_handle_for_field Jean Guyader
2012-08-03 19:50 ` [PATCH 3/5] xen: virq, remove VIRQ_XC_RESERVED Jean Guyader
2012-08-06  8:10   ` Jan Beulich
2012-08-06 14:46     ` Jean Guyader
2012-08-06 14:49       ` Andrew Cooper
2012-08-06 14:56       ` Ian Campbell
2012-08-06 15:01         ` Jean Guyader
2012-08-06 15:13           ` Ian Campbell
2012-08-06 15:46             ` Jan Beulich
2012-08-03 19:50 ` [PATCH 4/5] xen: events, exposes evtchn_alloc_unbound_domain Jean Guyader
2012-08-06  8:19   ` Jan Beulich
2012-08-09 10:06   ` Tim Deegan
2012-08-09 10:23     ` Ian Campbell
2012-08-09 10:35       ` Tim Deegan
2012-08-09 10:40         ` Jean Guyader
2012-08-09 23:25           ` Jean Guyader
2012-08-10  7:35             ` Jan Beulich
2012-08-10  7:51               ` Jean Guyader
2012-08-10  7:57                 ` Jan Beulich
2012-08-23 12:03                   ` Jean Guyader
2012-08-03 19:50 ` [PATCH 5/5] xen: Add V4V implementation Jean Guyader
2012-08-06  8:45   ` Jan Beulich
2012-08-23 11:57     ` Jean Guyader
2012-08-24 20:06       ` Jan Beulich
2012-09-01 20:58         ` Jean Guyader
2012-09-01 20:56     ` Jean Guyader
2013-06-11 17:10       ` [PATCH 5/5] xen: Add V4V implementation - padding question Ross Philipson
2013-06-11 17:25         ` Tim Deegan
2013-06-11 17:40           ` Ross Philipson
2013-06-11 17:54             ` Ross Philipson
2013-06-11 18:04               ` Tim Deegan
2013-06-12  7:45                 ` Jan Beulich
2013-06-13 17:21                 ` Stefano Stabellini
2012-08-09 10:38   ` [PATCH 5/5] xen: Add V4V implementation Tim Deegan
2012-08-10 16:51     ` Jean Guyader
2012-08-13  9:38       ` Tim Deegan
2012-08-13 12:43         ` Jean Guyader
2012-08-16 12:32           ` Tim Deegan
2012-08-04 13:24 ` [PATCH 0/5] RFC: V4V (v3) Jean Guyader

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=1344023454-31425-1-git-send-email-jean.guyader@citrix.com \
    --to=jean.guyader@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).