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 3/5] xen: Enforce introduce guest_handle_for_field
Date: Thu, 28 Jun 2012 17:26:24 +0100	[thread overview]
Message-ID: <1340900786-21802-4-git-send-email-jean.guyader@citrix.com> (raw)
In-Reply-To: <1340900786-21802-1-git-send-email-jean.guyader@citrix.com>

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


This helper turns a field of a GUEST_HANDLE in
a GUEST_HANDLE.

Signed-off-by: Jean Guyader <jean.guyader@citrix.com>
---
 xen/include/asm-x86/guest_access.h |    3 +++
 1 file changed, 3 insertions(+)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0003-xen-Enforce-introduce-guest_handle_for_field.patch --]
[-- Type: text/x-patch; name="0003-xen-Enforce-introduce-guest_handle_for_field.patch", Size: 547 bytes --]

diff --git a/xen/include/asm-x86/guest_access.h b/xen/include/asm-x86/guest_access.h
index 2b429c2..e3ac1d6 100644
--- a/xen/include/asm-x86/guest_access.h
+++ b/xen/include/asm-x86/guest_access.h
@@ -51,6 +51,9 @@
     (XEN_GUEST_HANDLE(type)) { _x };            \
 })
 
+#define guest_handle_for_field(hnd, type, fld)          \
+    ((XEN_GUEST_HANDLE(type)) { &(hnd).p->fld })
+
 #define guest_handle_from_ptr(ptr, type)        \
     ((XEN_GUEST_HANDLE(type)) { (type *)ptr })
 #define const_guest_handle_from_ptr(ptr, type)  \

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

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

  parent reply	other threads:[~2012-06-28 16:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 16:26 [PATCH 0/5] RFC: V4V (v2) Jean Guyader
2012-06-28 16:26 ` [PATCH 1/5] xen: add ssize_t Jean Guyader
2012-06-29  8:05   ` Jan Beulich
2012-06-29 10:09     ` Jean Guyader
2012-06-29 10:38       ` Jan Beulich
2012-06-28 16:26 ` [PATCH 2/5] v4v: Introduce VIRQ_V4V Jean Guyader
2012-06-29  8:07   ` Jan Beulich
2012-06-29 10:33     ` Jean Guyader
2012-06-28 16:26 ` Jean Guyader [this message]
2012-06-29  8:10   ` [PATCH 3/5] xen: Enforce introduce guest_handle_for_field Jan Beulich
2012-06-28 16:26 ` [PATCH 4/5] xen: Add V4V implementation Jean Guyader
2012-06-29  8:33   ` Jan Beulich
2012-06-29 10:03     ` Jean Guyader
2012-06-29 10:36       ` Jan Beulich
2012-07-18 20:09         ` Jean Guyader
2012-07-19  9:34           ` Andrew Cooper
2012-07-19  9:58             ` Jean Guyader
2012-07-19  9:54               ` Attilio Rao
2012-07-19 10:06                 ` Jean Guyader
2012-07-19 10:04                   ` Attilio Rao
2012-07-19 10:32                     ` Ian Campbell
2012-07-19 10:42               ` Andrew Cooper
2012-07-19 11:33                 ` Stefano Stabellini
2012-07-19 11:40                   ` Andrew Cooper
2012-07-19 11:58                 ` Jean Guyader
2012-07-23  8:18           ` Jan Beulich
2012-07-05 11:36   ` Tim Deegan
2012-06-28 16:26 ` [PATCH 5/5] v4v: Introduce basic access control to V4V Jean Guyader
2012-07-05 14:23   ` Tim Deegan

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=1340900786-21802-4-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).