From: Struan Bartlett <struan@praguespringpeople.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qvm86, kqemu and video speed
Date: Mon, 11 Apr 2005 23:53:24 +0200 [thread overview]
Message-ID: <425AF1D4.30408@praguespringpeople.org> (raw)
In-Reply-To: <425A914C.9010608@mastros.biz>
James Mastros wrote:
> Struan Bartlett wrote:
>
>> The results seem to me to suggest that emulated performance is
>> weakest on video operations - which doesn't surprise me if it is
>> necessary for every pixel change to be emulated - and while this
>> won't be an issue for some Qemu users it will I expect be a major
>> issue for others.
>
>
> One thing that could be done as a fairly quick hack would be to call
> SDL's bitblit function for bitblits that are simple copies. These are
> rather common, and SDL already knows how to optimize them well --
> we're just missing a bit of glue. I got about halfway through doing
> this in a few hours of hacking, but realized that the video struct was
> completely undocumented, and I wasn't sure how to map from a pointer
> into the LFB back into xy coords.
I'm curious. Could you post your code somewhere I could look at it?
next prev parent reply other threads:[~2005-04-11 21:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 14:07 [Qemu-devel] qvm86, kqemu and video speed Struan Bartlett
2005-04-11 15:01 ` James Mastros
2005-04-11 15:17 ` Paul Brook
2005-04-11 15:35 ` Struan Bartlett
2005-04-11 21:51 ` Struan Bartlett
2005-04-15 8:54 ` Struan Bartlett
2005-04-12 3:13 ` Darryl Dixon
2005-04-11 21:53 ` Struan Bartlett [this message]
2005-04-12 16:38 ` Alex Beregszaszi
2005-04-12 19:30 ` Fabrice Bellard
2005-04-13 3:57 ` use.reply-to.address
2005-04-13 8:06 ` Struan Bartlett
2005-04-13 18:12 ` Hetz Ben Hamo
2005-04-13 19:24 ` Leonardo E. Reiter
2005-04-13 20:09 ` Leonardo E. Reiter
2005-04-14 9:42 ` Thomas Steffen
2005-04-18 7:32 ` Oliver Gerlich
2005-04-19 6:15 ` emuls
2005-04-13 21:12 ` Jim C. Brown
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=425AF1D4.30408@praguespringpeople.org \
--to=struan@praguespringpeople.org \
--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 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.