From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH] tweak memory error correction field in the SMBIOS data Date: Wed, 25 Nov 2009 16:18:20 +0100 Message-ID: <4B0D4ABC.20104@redhat.com> References: <1259086479-12444-1-git-send-email-pbonzini@redhat.com> <4B0CF889.7000404@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Jiang, Yunhong" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 11/25/2009 04:00 PM, Jiang, Yunhong wrote: > So with your patch, even if host has no ECC support, you will still > tell guest that the memory has ECC? Yes, but I don't think it's of great importance. I'm just pleasing a test with the simplest possible 1-line fix. Do you know of anything that actually cares (i.e. not just "shows it to the user") about that particular DMI field, and does something different if it reads "ECC"? For that matter, hvmloader is already saying that the host is running at some number of megahertz, which does not make sense for virtualization because the host may be loaded and slow down the guest. Paolo