From: Keir Fraser <keir@xensource.com>
To: "Li, Xin B" <xin.b.li@intel.com>,
"Zhai, Edwin" <edwin.zhai@intel.com>,
Keir Fraser <keir@xensource.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH][HVM] remove qemu shadow_vram patch forperformance
Date: Tue, 20 Mar 2007 09:45:28 +0000 [thread overview]
Message-ID: <C2255DB8.BD88%keir@xensource.com> (raw)
In-Reply-To: <B30DA1341B0CFA4893EF8A36B40B5C5DE9DD8A@pdsmsx411.ccr.corp.intel.com>
On 20/3/07 09:36, "Li, Xin B" <xin.b.li@intel.com> wrote:
> The major problem this patch is trying to fix is the performance drop
> when multiple HVM guests are running, and I think we need a better
> solution for this.
>From my own reading of the code I would have thought that by removing that
SSE memcmp we'd be replacing periodic SSE block memcmp with periodic
pixel-by-pixel comparison (which is what I think we end up doing if we get
past the SSE memcmp?). I'm thinking particularly of the VNC side of things
rather than SDL here, by the way: you guys use SDL most of the time, right?
-- Keir
next prev parent reply other threads:[~2007-03-20 9:45 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 [this message]
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
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=C2255DB8.BD88%keir@xensource.com \
--to=keir@xensource.com \
--cc=edwin.zhai@intel.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xin.b.li@intel.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.