All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Shanab <jshanab@earthlink.net>
To: xen-devel@lists.xensource.com
Subject: Grad project transition to masters thesis idea
Date: Sat, 02 Sep 2006 16:50:12 -0700	[thread overview]
Message-ID: <44FA18B4.5090402@earthlink.net> (raw)

I am starting a Grad class on graphics and planning on turning it into
my masters thesis.  I would like to write a openGL split graphics driver
for zen to allow sharing of accelerated graphics. (without copying large
amounts of data around)

Kind of xgl+xen in domain zero with each pane a seperate domain. I
envision a rotate left right between desktop and a rotate up down
between domains. Not really a cube anymore, but you get the point.   I
have been reading documents on xgl,compviz,xgtk,xegl and xen but I am
not sure if this is possible yet.

What I am thinking is that each opengl context will be "registered" with
the hypervisor and a virtual openGL driver provided in each domain will
serve out xgl for an x server to use. A domain switch is just a eye
point change or opengl context change, what is in the card stays there
between switches.

But... Am i correct in assuming that the driver in domain zero will have
to be made xen aware so that it can determine which domain interupts 
from code accesing the card belong to? What I am afraid is that since
the card has a GPU it is like a dual processor system and that there
might not be enough  access to the GPU, that it may need it's own
hypervisor . I don't really know how the GPU's work. Is the code running
in the main CPU or in the GPU, where is that line?

Suggestions, comments?

             reply	other threads:[~2006-09-02 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-02 23:50 Jeff Shanab [this message]
2006-09-03  3:12 ` Grad project transition to masters thesis idea Niraj Tolia
2006-10-20  1:20 ` Mark Williamson

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=44FA18B4.5090402@earthlink.net \
    --to=jshanab@earthlink.net \
    --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.