From: Paul Durrant <Paul.Durrant@citrix.com>
To: Anshul Makkar <anshul.makkar@citrix.com>,
bharat gohil <ghl.bhrt@gmail.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: XenGT GPU virtualization
Date: Mon, 20 Feb 2017 15:31:36 +0000 [thread overview]
Message-ID: <f696fcdd0e4f414d85c8ece721708dd7@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <cbfec348-9172-112f-a4dd-c540047e3afc@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1195 bytes --]
No, that’s not correct. The GPU commands are whitelisted and only the commands that can be audited are handled.
Paul
From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of anshul makkar
Sent: 20 February 2017 15:16
To: bharat gohil <ghl.bhrt@gmail.com>; xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] XenGT GPU virtualization
On 18/01/17 13:21, bharat gohil wrote:
Hello
I am new to GPU and GPU virtualization and found that xen support intel GPU virtualization using XenGT.
I want to know,
1) What are the critical GPU command pass from xen to Dom0?
2) How the Dom0 mediator or xen validate the GPU command which is passed from domU GPU driver?
3) If one of the domU guest send bad(malicious) command to GPU which led GPU to bad state. Can Dom0 mediator or xen prevents this kind of scenario?
As far as I know, there is know mediation to check for the commands. Xen does audit the target address space, but not GPU commands.
--
Regards,
Bharat Gohil
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org<mailto:Xen-devel@lists.xen.org>
https://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 45846 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-20 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 13:21 XenGT GPU virtualization bharat gohil
2017-01-31 21:29 ` Konrad Rzeszutek Wilk
2017-02-20 15:16 ` anshul makkar
2017-02-20 15:31 ` Paul Durrant [this message]
2017-02-23 12:29 ` bharat gohil
2017-02-23 12:36 ` Paul Durrant
2017-02-24 1:24 ` Haozhong Zhang
2017-02-24 1:42 ` Haozhong Zhang
2017-02-24 2:25 ` [iGVT-g] " Wang, Hongbo
2017-02-24 6:58 ` bharat gohil
2017-02-28 15:07 ` Konrad Rzeszutek Wilk
2017-03-01 14:36 ` Zhiyuan Lv
2017-03-01 19:50 ` Konrad Rzeszutek Wilk
2017-02-24 1:23 ` Haozhong Zhang
2017-02-24 1:38 ` Haozhong Zhang
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=f696fcdd0e4f414d85c8ece721708dd7@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=ghl.bhrt@gmail.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).