From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Pflug Subject: Re: [BUG] EDAC infomation partially missing Date: Fri, 22 Jan 2016 12:33:53 +0100 Message-ID: <56A213A1.8060206@pse-consulting.de> References: <569FA160.6070308@web.de> <56A1184902000078000C9B3D@prv-mh.provo.novell.com> <56A1F1B0.9030508@pse-consulting.de> <56A2154402000078000C9F74@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <56A2154402000078000C9F74@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: 810964@bugs.debian.org, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Am 22.01.16 um 11:40 schrieb Jan Beulich: >>>> On 22.01.16 at 10:09, wrote: >> When booting with Xen 4.4.1: >> >> AMD64 EDAC driver v3.4.0 >> EDAC amd64: DRAM ECC enabled. >> EDAC amd64: NB MCE bank disabled, set MSR 0x0000017b[4] on node 0 to enable. > I wonder how valid his message is. We actually write this MSR with > all ones during boot. > > However, considering involved functions like > nb_mce_bank_enabled_on_node() or node_to_amd_nb() taking > node IDs as inputs, and considering that PV guests (including > Dom0) don't have a topology matching that of the host, I doubt > very much that this driver is even remotely prepared to run > under Xen. It working on Xen 4.1.x would then be by pure > accident. The dmesg is identical with or without Xen4.1, so I'd guess it does work if flags are detected correctly. Regards Andreas