From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: bharat gohil <ghl.bhrt@gmail.com>, jike.song@intel.com
Cc: xen-devel@lists.xenproject.org
Subject: Re: XenGT GPU virtualization
Date: Tue, 31 Jan 2017 16:29:47 -0500 [thread overview]
Message-ID: <20170131212947.GE20233@char.us.ORACLE.com> (raw)
In-Reply-To: <CABdg74f2deeTw26gJ6aLNBH2XMRJ3L0Rrg78oLRn93+VhHdSEw@mail.gmail.com>
On Wed, Jan 18, 2017 at 06:51:02PM +0530, bharat gohil wrote:
> Hello
Hey!
CC-ing one of the XenGT folks who I hope can help you.
>
> 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?
>
> --
> Regards,
> Bharat Gohil
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-31 21:29 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 [this message]
2017-02-20 15:16 ` anshul makkar
2017-02-20 15:31 ` Paul Durrant
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=20170131212947.GE20233@char.us.ORACLE.com \
--to=konrad.wilk@oracle.com \
--cc=ghl.bhrt@gmail.com \
--cc=jike.song@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.