From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: KVM Processor cache size Date: Mon, 02 Aug 2010 17:23:21 -0500 Message-ID: <4C574559.40509@codemonkey.ws> References: <4C56BF6F.9040402@amd.com> <4C56CCFB.204@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Andre Przywara , Ricardo Martins , "kvm@vger.kernel.org" To: Ulrich Drepper Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:47688 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751102Ab0HBWXZ (ORCPT ); Mon, 2 Aug 2010 18:23:25 -0400 Received: by iwn7 with SMTP id 7so4468298iwn.19 for ; Mon, 02 Aug 2010 15:23:25 -0700 (PDT) In-Reply-To: <4C56CCFB.204@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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: > =20 >> Do you have a use case for the cache size or is this just out of cur= iosity? >> =20 > 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= =20 migration with -cpu host too if we don't guarantee these values remain=20 stable across migration... Regards, Anthony Liguori > Even the synthetic > CPU provided by qemu should have a more realistic value. > > - --=20 > =E2=9E=A7 Ulrich Drepper =E2=9E=A7 Red Hat, Inc. =E2=9E=A7 444 Castro= St =E2=9E=A7 Mountain View, CA =E2=9D=96 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iEYEARECAAYFAkxWzPsACgkQ2ijCOnn/RHQ2JwCeJsgXHxkWG/PYS8JQRiGM1UFF > m78Ani9kmnKJyru/wh764NSgHSQx+WjU > =3D6qet > -----END PGP SIGNATURE----- > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > =20