All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Keir Fraser <keir@xensource.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com, "Zhai,
	Edwin" <edwin.zhai@intel.com>
Subject: Re: [PATCH][HVM] remove qemu shadow_vram patch for performance
Date: Wed, 21 Mar 2007 16:09:25 -0500	[thread overview]
Message-ID: <46019F05.6050000@us.ibm.com> (raw)
In-Reply-To: <C21ED565.B88C%keir@xensource.com>

Keir Fraser wrote:
> 
> 
> On 15/3/07 03:30, "Zhai, Edwin" <edwin.zhai@intel.com> wrote:
> 
>> remove qemu shadow_vram patch and force a whole screen update each time for
>> performance.
>>
>> W/O this patch, there is huge performance drop in HVM domain when adding other
>> guest(windows or linux with xwindow).
>>
>> shadow_vram_revert.patch - revert the shadow_vram patch
>> shadow_vram_force_update.patch - explictly redraw screen each time
> 
> How can updating the whole screen 30 times a second be faster than the
> memcmp() that we do currently?

It really depends.  The VNC display already has a minimization mechanism 
so doign the memcmp() in the vga driver doesn't help at all.

For SDL, when using X, it's going to be doing an XShmImage so the 
difference is only in the size of update (no data is transferred to the 
X server).  If the X server is double buffering the framebuffer (which I 
have to assume it's doing), then you're just paying the cost of a 
memcpy() in the X server that you would normally pay in qemu-dm.

However, if you're forwarding SDL over X, or for some reason your X 
server isn't using XShmImage, this patch will slow things down considerably.

Perhaps this should be made a configuration option?

Regards,

Anthony Liguori

>  -- Keir

      parent reply	other threads:[~2007-03-21 21:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15  3:30 [PATCH][HVM] remove qemu shadow_vram patch for performance Zhai, Edwin
2007-03-15 10:50 ` Keir Fraser
2007-03-16  3:04   ` Zhai, Edwin
2007-03-20  8:38     ` [PATCH][HVM] remove qemu shadow_vram patch forperformance Li, Xin B
2007-03-20  8:47       ` Keir Fraser
2007-03-20  9:36         ` Li, Xin B
2007-03-20  9:45           ` Keir Fraser
2007-03-20  9:48             ` Li, Xin B
2007-03-21  2:38             ` Zhai, Edwin
2007-03-21 20:50             ` [PATCH][HVM] remove qemu shadow_vram patchforperformance Dong, Eddie
2007-03-22 23:40         ` [PATCH][HVM] remove qemu shadow_vram patch forperformance Christian Limpach
2007-03-23  0:38           ` [PATCH][HVM] remove qemu shadow_vram patchforperformance Dong, Eddie
2007-03-21 21:09   ` [PATCH][HVM] remove qemu shadow_vram patch for performance Anthony Liguori
2007-03-21 21:09   ` Anthony Liguori [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=46019F05.6050000@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=edwin.zhai@intel.com \
    --cc=keir@xensource.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.