From: Mark Williamson <mark.williamson@cl.cam.ac.uk>
To: xen-devel@lists.xensource.com
Cc: Jeff Shanab <jshanab@earthlink.net>, Jacob Gorm Hansen <jacobg@diku.dk>
Subject: Re: Grad project transition to masters thesis idea
Date: Fri, 20 Oct 2006 02:20:21 +0100 [thread overview]
Message-ID: <200610200220.21926.mark.williamson@cl.cam.ac.uk> (raw)
In-Reply-To: <44FA18B4.5090402@earthlink.net>
> 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)
Well, that'd be cool :-)
> 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.
Kind of a hypercube then :-D That'd be really cool.
> 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.
Jacob has done a bit of work on this in the form of Blink and also a previous
project that source isn't available. He might be able to suggest some
reading...
> 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?
You'd have to figure out some way of handling the multiplexing in domain 0.
This doesn't necessarily have to modify the device driver, but *something*
there needs to handle domains competing for resources, prevent them from
abusing the screen (although preventing abuse might be more optional in a
workstation setting).
> 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?
Another thing you might find interesting is that MS (and, I think, maybe
NVidea) are looking at virtualisation-aware graphics hardware, but I'm not
sure if there are any details available on this.
HTH,
Mark
--
Dave: Just a question. What use is a unicyle with no seat? And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!
prev parent reply other threads:[~2006-10-20 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 23:50 Grad project transition to masters thesis idea Jeff Shanab
2006-09-03 3:12 ` Niraj Tolia
2006-10-20 1:20 ` Mark Williamson [this message]
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=200610200220.21926.mark.williamson@cl.cam.ac.uk \
--to=mark.williamson@cl.cam.ac.uk \
--cc=jacobg@diku.dk \
--cc=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.