From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: win-pv-devel@lists.xenproject.org, xen-devel@lists.xensource.com,
spice-devel@lists.freedesktop.org
Cc: Paul Durrant <paul.durrant@citrix.com>, pasik@iki.fi
Subject: Developers for virgl 3d windows guest support
Date: Tue, 26 Jan 2016 17:48:34 +0100 [thread overview]
Message-ID: <56A7A362.30309@m2r.biz> (raw)
I take a fast look to virgl 3d project even if I not tested it for now.
It seems interesting for adding 2d and 3d hw acceleration support to
virtual machines with a large hw (gpu) choice.
I take a look also to intel gvt-g but it has a very limited cpu support
choice.
I saw that windows guest support with direct3d drivers in virgl is
planned but I nothing was done for now.
I'm approaching a new project (based on xen) and I'm in planning phase now.
My goal would be to have virgl 3d windows guest support (drivers with
opengl and direct3d) and support of remote rendering with spice (we are
already using with qxl for now)
Are there any developers expert about these things that can advice me if
developing windows drivers (WDDM kernel driver + GL and D3D userspace
pieces) and any other needed pieces of code in virglrender, mesa, and
/or qemu is a good choice?
If yes, what we would like to know is approx time/effort to have the
above support upstream. Approximately how many persons and how many time
would require to complete the tasks? (my project is going to be financed
so we eventually have resource to schedule working time in the community)
Thanks for any reply and sorry for my bad english.
_______________________________________________
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
next reply other threads:[~2016-01-26 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 16:48 Fabio Fantoni [this message]
[not found] ` <56A7A362.30309-J6ELqAEQOBs@public.gmane.org>
2016-01-27 18:37 ` [Xen-devel] Developers for virgl 3d windows guest support Konrad Rzeszutek Wilk
2016-01-28 10:16 ` Fabio Fantoni
2016-01-28 11:32 ` Gerd Hoffmann
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=56A7A362.30309@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=pasik@iki.fi \
--cc=paul.durrant@citrix.com \
--cc=spice-devel@lists.freedesktop.org \
--cc=win-pv-devel@lists.xenproject.org \
--cc=xen-devel@lists.xensource.com \
/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.