xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: MCE in pv-domU
Date: Wed, 7 Jun 2017 16:23:20 +0200	[thread overview]
Message-ID: <678ec56b-208e-96ef-6d07-cadb7590c117@suse.com> (raw)
In-Reply-To: <5938258A02000078001606F3@suse.com>

On 07/06/17 16:10, Jan Beulich wrote:
>>>> On 07.06.17 at 16:00, <jgross@suse.com> wrote:
>> Just saw the message:
>>
>> [    0.005227] mce: CPU supports 2 MCE banks
>>
>> in the boot log of a pv domU (Linux 4.11). I really have problems to see
>> the value of MCE handling being active in this case. Shouldn't we switch
>> it off?
> 
> What's wrong with letting a guest decide on its own what to do
> if a memory page assigned to it went bad? From host perspective
> the only "recovery" would be to kill the guest. The guest kernel,
> otoh, may be able to confine damage to just the killing of a single
> process (or if the page is not in use, no damage would result at
> all).

So the MCE related resources are fully virtualized for the guest?


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-06-07 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 14:00 MCE in pv-domU Juergen Gross
2017-06-07 14:10 ` Jan Beulich
     [not found] ` <5938258A02000078001606F3@suse.com>
2017-06-07 14:23   ` Juergen Gross [this message]
2017-06-07 14:31     ` Jan Beulich
2017-06-07 15:51       ` Andrew Cooper

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=678ec56b-208e-96ef-6d07-cadb7590c117@suse.com \
    --to=jgross@suse.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=xen-devel@lists.xenproject.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).