From: Dennis Schridde <dennis.schridde-axtXthT+lymYbFdUjOg7S7NAH6kLmebB@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Bind amdgpu to SR-IOV virtual function
Date: Thu, 25 Aug 2016 17:00:41 +0200 [thread overview]
Message-ID: <2568946.uSqerHif76@c07060> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1345 bytes --]
Hello!
I investigating the virtualisation abilities of current AMD FirePro hardware;
specifically how to securely pass a share of a GPU to one application (a Rkt/
Docker container). I already read vfio.txt and pci-iov-howto.txt, but they do
not answer my questions. I was unable to find documentation on the process
online, either.
1. How do I create VFs from a AMD FirePro PF? I saw an example using VMWare
ESXi tools, where it is possible to specify RAM size and time-share, but I
have not seen how that translates to modifying /sys/bus/pci/..., which is the
method recommended for SR-IOV devices in pci-iov-howto.txt.
2. After having created VFs, is it possible to bind these to the host's amdgpu
driver, so that I get multiple /dev/dri/card* device nodes?
3. Will passing these /dev/dri/card* device nodes into a Rkt/Docker container
be enough for the AMD Radeon Pro OpenGL runtime to be able to use that card?
Best regards,
Dennis Schridde
--
Heidelberg University Computing Centre
Service division: Future IT - Research & Education
Tel. +49 6221 54-4519, Fax +49 6221 54-5581
dennis.schridde-axtXthT+lymYbFdUjOg7S7NAH6kLmebB@public.gmane.org
http://www.urz.uni-heidelberg.de/
Ruprecht-Karls-Universität Heidelberg
Universitätsrechenzentrum
Im Neuenheimer Feld 293, 69120 Heidelberg, Germany
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 681 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2016-08-25 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:00 Dennis Schridde [this message]
2016-08-25 15:44 ` Bind amdgpu to SR-IOV virtual function Alex Deucher
[not found] ` <CADnq5_PFpcM78ZtcfmDMdXboriz7MeLq7Ob+ZFWSOyVcNvoevQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-08-25 15:51 ` Dennis Schridde
2016-08-25 15:55 ` Alex Deucher
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=2568946.uSqerHif76@c07060 \
--to=dennis.schridde-axtxtht+lymybfdujog7s7nah6klmebb@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.