From: Andreas Pflug <pgadmin@pse-consulting.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: 810964@bugs.debian.org, xen-devel@lists.xen.org
Subject: Re: [BUG] EDAC infomation partially missing
Date: Fri, 22 Jan 2016 12:33:53 +0100 [thread overview]
Message-ID: <56A213A1.8060206@pse-consulting.de> (raw)
In-Reply-To: <56A2154402000078000C9F74@prv-mh.provo.novell.com>
Am 22.01.16 um 11:40 schrieb Jan Beulich:
>>>> On 22.01.16 at 10:09, <pgadmin@pse-consulting.de> 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
next prev parent reply other threads:[~2016-01-22 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <569FA160.6070308@web.de>
2016-01-21 16:41 ` [BUG] EDAC infomation partially missing Jan Beulich
2016-01-22 9:09 ` Andreas Pflug
2016-01-22 10:40 ` Jan Beulich
2016-01-22 11:33 ` Andreas Pflug [this message]
[not found] <20170513223656.GA40303@scollay.m5p.com>
2017-05-15 8:02 ` Jan Beulich
2017-05-16 3:47 ` Elliott Mitchell
2017-05-16 9:54 ` Jan Beulich
2017-05-16 10:08 ` Andrew Cooper
2017-05-16 18:02 ` Elliott Mitchell
2017-05-13 22:36 Elliott Mitchell
-- strict thread matches above, loose matches on Subject: below --
2016-01-20 15:01 Andreas Pflug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A213A1.8060206@pse-consulting.de \
--to=pgadmin@pse-consulting.de \
--cc=810964@bugs.debian.org \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).