From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33643) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vimry-00031O-U3 for qemu-devel@nongnu.org; Tue, 19 Nov 2013 10:05:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vimrq-0004og-5V for qemu-devel@nongnu.org; Tue, 19 Nov 2013 10:05:38 -0500 Received: from mx.ipv6.kamp.de ([2a02:248:0:51::16]:36062 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vimrp-0004oG-R0 for qemu-devel@nongnu.org; Tue, 19 Nov 2013 10:05:30 -0500 Message-ID: <528B7E39.6050905@kamp.de> Date: Tue, 19 Nov 2013 16:05:29 +0100 From: Peter Lieven MIME-Version: 1.0 References: <1379694292-1601-1-git-send-email-pbonzini@redhat.com> <1379694292-1601-12-git-send-email-pbonzini@redhat.com> <528A310A.60607@dlhnet.de> <528A3422.1030701@kamp.de> <528A3C4A.4090001@redhat.com> <528B3C86.3030309@kamp.de> <528B41A5.1080504@redhat.com> <528B53A6.3030204@kamp.de> <528B561C.9070200@redhat.com> <528B5A5B.1090705@kamp.de> <528B65E6.7040203@redhat.com> <528B7190.1060009@kamp.de> <528B7262.1010909@redhat.com> <528B7303.3070204@kamp.de> <528B738B.8080805@redhat.com> <528B79CA.7080109@kamp.de> <528B7C40.8050309@redhat.com> In-Reply-To: <528B7C40.8050309@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL 11/13] target-i386: forward CPUID cache leaves when -cpu host is used List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, Anthony Liguori , =?UTF-8?B?QmVub8OudCBDYW5ldA==?= On 19.11.2013 15:57, Paolo Bonzini wrote: > Il 19/11/2013 15:46, Peter Lieven ha scritto: >>> Just replace "if (cs->nr_cores > 1)" in the patch I posted, i.e. after >>> the switch. >> This seems to work. What is in bits 0..5 of eax? > It's the kind of cache. 0 means that there is no cache and the returned > data is not valid. In theory, Intel says you should only check whether > those bits are 0, and stop iterating when they are, but apparently > something is expecting eax=0. > >> What about the number of threads in count == 2? > That's a property of the L2 cache. It's not related to APIC IDs. okay, but the contents could be wrong if the physical system has threads while the emulated vserver has not. does this matter? > >> I would still like to have at least an option to disable the passthru >> without recompiling if other issues occur. > I think of "-cpu host" in general as a hit-or-miss option. I'm not sure > whether it makes sense to have such fine grain. As I explained, I have no trouble with -cpu host for ages when I ensure that I do not live migrate to a processor that misses a feature that was there when the vserver was created. With the caching option this could become a problem or do you think wrong assumption about the cache are just a performance penalty? Peter