qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Extremely slow graphic updates
Date: Wed, 21 Jan 2009 20:06:38 +0000	[thread overview]
Message-ID: <4977804E.70705@eu.citrix.com> (raw)
In-Reply-To: <20090121152259.GG29175@csclub.uwaterloo.ca>

Lennart Sorensen wrote:

> I just tried running with '-serial /dev/null -parallel /dev/null' and
> the slow down problem disappeared.  I am suspicious of this part of the
> 6336 commit:
> 
> @@ -1360,12 +1352,137 @@ void qemu_console_copy(QEMUConsole *console, int src_x, int src_y,
>                  int dst_x, int dst_y, int w, int h)
>  {
>      if (active_console == console) {
> -        if (console->ds->dpy_copy)
> -            console->ds->dpy_copy(console->ds,
> -                            src_x, src_y, dst_x, dst_y, w, h);
> -        else {
> -            /* TODO */
> -            console->ds->dpy_update(console->ds, dst_x, dst_y, w, h);
> -        }
> +            dpy_copy(console->ds, src_x, src_y, dst_x, dst_y, w, h);
>      }
>  }
> 
> To me this looks like what used to do a copy if the console was active,
> and an update if it was not, has turned into a copy at all times.  This
> sounds like potentially doing expensive work on inactive consoles.  This
> is what made me think of trying to disable the parallel and serial
> consoles.
> 
> I made this little patch for console.c:
> 
> --- qemu-0.9.1.14778c2064166a8d1d07b22f0af9eee4fa490e60/console.c       2009-01-21 09:26:06.000000000 -0500
> +++ qemu-0.9.1.14778c2064166a8d1d07b22f0af9eee4fa490e60.new/console.c   2009-01-21 10:12:29.000000000 -0500
> @@ -1433,7 +1433,11 @@
>                         int dst_x, int dst_y, int w, int h)
>  {
>      if (is_graphic_console()) {
> -        dpy_copy(ds, src_x, src_y, dst_x, dst_y, w, h);
> +        if(active_console->ds == ds) {
> +            dpy_copy(ds, src_x, src_y, dst_x, dst_y, w, h);
> +        } else {
> +            dpy_update(ds, dst_x, dst_y, w, h);
> +        }
>      }
>  }
> 
> And then it is back to proper speed for me across ssh.  Does it make sense?
> 


I am afraid your patch shouldn't make a difference because sdl doesn't
have a dpy_copy function so with sdl dpy_update is always called.
Besides none calls qemu_console_copy but graphic cards so passing
'-serial /dev/null -parallel /dev/null' shouldn't change anything in
this regard.

In any case I tried passing '-serial /dev/null -parallel /dev/null' as
arguments but (locally) I do not see any benefits (I tested with the
debian ppc installation cd).
Could you please tell me if you see the slowdown on a local X server also?
The sdl blitting functions are optimized to be run locally, it is
possible that they do not have good performances on a remote X server.
Fortunately we provide a much better interface to connect to qemu
remotely (vnc), that now should be even faster than before.

  reply	other threads:[~2009-01-21 20:11 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 16:26 [Qemu-devel] qemu-system-ppc seems slow today Lennart Sorensen
2009-01-19 17:09 ` Aurelien Jarno
2009-01-19 17:49   ` Lennart Sorensen
2009-01-19 18:07     ` Lennart Sorensen
2009-01-19 18:39       ` Aurelien Jarno
2009-01-19 19:42         ` Lennart Sorensen
2009-01-20  0:53           ` Lennart Sorensen
2009-01-20  1:01             ` François Revol
2009-01-20  1:33             ` [Qemu-devel] Extremely slow graphic updates (was: qemu-system-ppc seems slow today) Paul Brook
2009-01-20  1:54               ` [Qemu-devel] Re: Extremely slow graphic updates Anthony Liguori
2009-01-20 11:22               ` Stefano Stabellini
2009-01-20 11:28                 ` Stefano Stabellini
2009-01-20 14:46                   ` Lennart Sorensen
2009-01-20 14:45                 ` Lennart Sorensen
2009-01-20 15:21                   ` Stefano Stabellini
2009-01-20 16:55                     ` Lennart Sorensen
2009-01-20 17:09                       ` Samuel Thibault
2009-01-20 18:15                         ` Lennart Sorensen
2009-01-20 18:16                           ` Stefano Stabellini
2009-01-20 18:25                             ` Lennart Sorensen
2009-01-20 19:35                               ` Lennart Sorensen
2009-01-20 19:46                                 ` Jamie Lokier
2009-01-20 20:02                                   ` Lennart Sorensen
2009-01-20 20:12                                     ` Jamie Lokier
2009-01-20 20:17                                       ` Lennart Sorensen
2009-01-20 19:38                               ` Stefano Stabellini
2009-01-20 20:05                                 ` Lennart Sorensen
2009-01-20 20:30                             ` Avi Kivity
2009-01-20 18:59                           ` Samuel Thibault
2009-01-20 17:21                       ` Stefano Stabellini
2009-01-20 17:35                         ` Stefano Stabellini
2009-01-20 18:11                 ` Paul Brook
2009-01-20 18:48                   ` Re : " Sylvain Petreolle
2009-01-20 21:29                   ` Stefan Weil
2009-01-21  1:50                   ` Paul Brook
2009-01-21 15:23                     ` Lennart Sorensen
2009-01-21 20:06                       ` Stefano Stabellini [this message]
2009-01-21 21:29                         ` Lennart Sorensen
2009-01-21 21:49                           ` Lennart Sorensen
2009-01-21 21:52                             ` Stefano Stabellini
2009-01-22  0:20                             ` Paul Brook
2009-01-22 13:19                               ` Lennart Sorensen

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=4977804E.70705@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    --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).