| commit | f8e378f27f2a8b99bf9be0a9168ba0ea19eeb740 | |
| author | Avi Kivity <avi@redhat.com> | |
| Mon, 20 Jun 2011 08:12:47 +0000 (20 11:12 +0300) | ||
| committer | Anthony Liguori <aliguori@us.ibm.com> | |
| Wed, 22 Jun 2011 12:18:38 +0000 (22 07:18 -0500) | ||
| tree | bdc5f4192241afbcc17f931557529d6e18e17a77 | treesnapshot (tar.gz zip) |
| parent | 9319a6d3a6af9ae85556261e4a759eaddb49d734 | commitdiff |
Optimize screendump
When running kvm-autotest, fputc() is often the second highest (sometimes #1)
function showing up in a profile. This is due to fputc() locking the file
for every byte written.
Optimize by buffering a line's worth of pixels and writing that out in a
single call.
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
When running kvm-autotest, fputc() is often the second highest (sometimes #1)
function showing up in a profile. This is due to fputc() locking the file
for every byte written.
Optimize by buffering a line's worth of pixels and writing that out in a
single call.
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
| hw/vga.c | diffblobblamehistory |