On 08/02/2010 08:49 AM, Ulrich Drepper wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/02/2010 05:51 AM, Andre Przywara wrote:
Do you have a use case for the cache size or is this just out of curiosity?
glibc uses the cache size information returned by cpuid to perform
optimizations. For instance, copy operations which would pollute too
much of the cache because they are large will use non-temporal
instructions. There are real performance benefits.
I imagine that there would be real performance problems from doing live
migration with -cpu host too if we don't guarantee these values remain
stable across migration...
Regards,
Anthony Liguori
Even the synthetic
CPU provided by qemu should have a more realistic value.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAkxWzPsACgkQ2ijCOnn/RHQ2JwCeJsgXHxkWG/PYS8JQRiGM1UFF
m78Ani9kmnKJyru/wh764NSgHSQx+WjU
=6qet
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
