From: Lionel Ulmer <lionel.ulmer@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OpenGL idea...
Date: Sat, 11 Oct 2003 09:02:35 +0200 [thread overview]
Message-ID: <20031011090235.A31919@bbland> (raw)
In-Reply-To: <Pine.GSO.3.96.1031010234106.5534A-100000@beach.silcom.com>; from cpage@silcom.com on Fri, Oct 10, 2003 at 11:43:05PM -0700
> Would it be possible to create a thunk "library" that is linked to
> the application in place of the x86 library? If so then one could be made
> to handle the OpenGL calls and pass them onto the native DLL. This would
> in theory enable accelerated OpenGL... unless there's something else I'm
> missing...
This could work (ie to basically have most GL calls be like syscalls). The
problems are :
1) you need to do parameter conversions for all API calls. Which are pretty
easy for most of the core APIs, but will be a pain for textures, vertex
buffers.
2) OpenGL, for thread safety, relies on the way the underlying system does
threading. For example, I know that the NVIDIA drivers, when NPTL is
built in, use some special storage in the TLS space for their datas.
Now, if QEMU emulates 'target' threading all in the same 'native' thread
(ie you do not have one target thread == one native thread), this won't
work as all GL calls will be on the same thread (note that
multi-threaded GL apps are pretty rare out there :-) ).
3) if X is emulated and GL is native, how are you going to get all GLX
calls working ?
These are the problems I see... Maybe they have easy solution though, I did
not think too much about this :-)
Lionel
--
Lionel Ulmer - http://www.bbrox.org/
prev parent reply other threads:[~2003-10-11 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 6:43 [Qemu-devel] OpenGL idea Chad Page
2003-10-11 7:02 ` Lionel Ulmer [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=20031011090235.A31919@bbland \
--to=lionel.ulmer@free.fr \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).