From: Wei Liu <wei.liu2@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] tools/libxenforeignmemory: add a call to restrict the handle
Date: Fri, 24 Mar 2017 11:40:14 +0000 [thread overview]
Message-ID: <20170324114014.uc2w2p2f2fytftvi@citrix.com> (raw)
In-Reply-To: <1490181925-8026-1-git-send-email-paul.durrant@citrix.com>
On Wed, Mar 22, 2017 at 11:25:25AM +0000, Paul Durrant wrote:
> Commit 8ef5f344d061 "tools/libxendevicemodel: add a call to restrict the
> handle" added a function to the devicemodel interface to restrict
> operations through the API to a specific domain, where a capable under-
> lying privcmd driver exists.
>
> This patch adds similar functionality to the xenforeignmemory API. This
> will be necessary (as much as xendevicemodel restriction) for limiting
> the scope of device models to specific domains.
>
> NOTE: My patch to the linux kernel [1] added the appropriate checks to
> the foreign memory ioctls.
>
> [1] https://git.kernel.org/cgit/linux/kernel/git/ostr/linux.git/commit/?id=4610d240
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-24 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 11:25 [PATCH] tools/libxenforeignmemory: add a call to restrict the handle Paul Durrant
2017-03-24 11:40 ` Wei Liu [this message]
2017-03-24 20:10 ` Andrew Cooper
2017-03-24 20:24 ` Paul Durrant
2017-03-27 8:06 ` Paul Durrant
2017-03-27 8:16 ` Andrew Cooper
2017-03-27 8:20 ` Paul Durrant
2017-03-27 18:03 ` Julien Grall
2017-03-27 22:54 ` Andrew Cooper
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=20170324114014.uc2w2p2f2fytftvi@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=paul.durrant@citrix.com \
--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).