From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bconw-0003OC-Au for qemu-devel@nongnu.org; Thu, 25 Aug 2016 03:10:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bconr-00044O-A2 for qemu-devel@nongnu.org; Thu, 25 Aug 2016 03:10:23 -0400 Received: from szxga01-in.huawei.com ([58.251.152.64]:2571) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bconq-00043q-AN for qemu-devel@nongnu.org; Thu, 25 Aug 2016 03:10:19 -0400 Message-ID: <57BE99A7.2060005@huawei.com> Date: Thu, 25 Aug 2016 15:09:27 +0800 From: Shannon Zhao MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Why Qemu doesn't present L3 cache info for guest? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel , Paolo Bonzini , Eduardo Habkost Cc: longpeng , "Huangpeng (Peter)" , "Gonglei (Arei)" Hi guys, Looking at the codes, for pc-2.4 machine it enables host-cache-info for guest so guest can get the L3 cache info of host. But since QEMU has its own rule to generate ACPI ID, guest will not use the L3 cache correctly. I also notice that QEMU present L1 and L2 cache for guest via its own rule, why it not present L3 cache info which is consistent with the ACPI ID? Are there any downsides? Thanks, -- Shannon