On Tue, May 18, 2010 at 9:43 PM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > I'll rerun with profiling tomorrow to see if calloc() makes a > difference for general qemu_mallocz() usage.
The results are unchanged for direct calloc() instead of malloc+memset. The memset() symbol is still at the top of the profile because glibc is using it internally for calloc(). In theory calloc() allows libc to do optimizations so I think changing qemu_mallocz() to use calloc() is reasonable. Stefan