qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: Qemu 2D performance plunges below acceptable levels
Date: Sat, 21 Feb 2009 07:02:42 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.64.0902210701170.2181@linmac.oyster.ru> (raw)
In-Reply-To: <499EE1FD.50704@eu.citrix.com>

On Fri, 20 Feb 2009, Stefano Stabellini wrote:

> Paul Brook wrote:
> 
> >>      SDL_BlitSurface(guest_screen, &rec, real_screen, &rec);
> >> -    SDL_UpdateRect(real_screen, x, y, w, h);
> >> +    SDL_UpdateRects(real_screen, 1, &rec);
> > 
> > Have you actually tried this? I'd be amazed and dismayed if it made any 
> > difference. I can believe that SDL_UpdateRects is better that *multiple* 
> > calls to SDL_UpdateRect. However I see absolutely no justification for this 
> > change.
> > 
> 
> Of course I didn't: I don't have any MacOSX available and this is the
> main reason I am asking other people to test this patch and doing it myself.
> 
> >>From the documentation I thought they were implemented differently
> somehow but now that you make me think about it I went through the
> actual code and SDL_UpdateRect is implemented using SDL_UpdateRects :(
> 
> Also I don't how to explain the fact that SDL_Flip is faster than
> SDL_UpdateRect on MacOSX according to malc: the same libsdl macosx faq I
>  linked before claims that SDL_DOUBLEBUF is not even supported on MacOsX.

Let me reiterate - SDL_UpdateRect was REMOVED from sdl_update, SDL_Flip 
was added to _sdl_refresh_. So, no, SDL_Flip is NOT faster than
SDL_UpdateRect.

-- 
mailto:av1474@comtv.ru

  parent reply	other threads:[~2009-02-21  4:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15 13:10 [Qemu-devel] Qemu 2D performance plunges below acceptable levels Alexey Eremenko
2009-02-15 17:11 ` [Qemu-devel] " Alexey Eremenko
2009-02-16 10:31   ` Stefano Stabellini
2009-02-16 11:47     ` Avi Kivity
2009-02-16 16:15       ` Stefano Stabellini
2009-02-16 16:36         ` Avi Kivity
2009-02-17 17:48         ` Avi Kivity
2009-02-17 19:00           ` Stefano Stabellini
2009-02-18  8:46             ` Alexey Eremenko
2009-02-18  9:33               ` malc
2009-02-18 10:48                 ` Stefano Stabellini
2009-02-18 11:17                   ` malc
2009-02-18 11:27                     ` Alexey Eremenko
2009-02-18 11:32                       ` malc
2009-02-18 12:12                     ` Stefano Stabellini
2009-02-18 18:51                       ` malc
2009-02-19 15:14                       ` malc
2009-02-20 16:37                         ` Stefano Stabellini
2009-02-20 16:52                           ` Paul Brook
2009-02-20 17:01                             ` Stefano Stabellini
2009-02-20 17:16                               ` Paul Brook
2009-02-21  4:02                               ` malc [this message]
2009-02-23  3:06                                 ` Stefano Stabellini
2009-02-23  6:43                                   ` malc
2009-02-20 17:17                             ` Laurent Desnogues
2009-02-18 10:43               ` Stefano Stabellini

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=Pine.LNX.4.64.0902210701170.2181@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --cc=paul@codesourcery.com \
    --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).