All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: KVM <kvm@vger.kernel.org>,
	"Marcelo Tosatti" <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Huang Ying" <ying.huang@intel.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [PATCH] target-i386: Do not set MCG_SER_P by default
Date: Mon, 23 Nov 2015 15:47:44 +0100	[thread overview]
Message-ID: <56532710.8030607@redhat.com> (raw)
In-Reply-To: <20151123132237.GM23717@thinpad.lan.raisama.net>



On 23/11/2015 14:22, Eduardo Habkost wrote:
> > Software Error Recovery, i.e. SER, is purely an Intel feature and it
> > shouldn't be set by default. Enable it only on Intel.
> 
> What happens when SER is enabled on an AMD CPU? If it really
> should't be enabled, why is KVM returning it on
> KVM_X86_GET_MCE_CAP_SUPPORTED?

Indeed... is it a problem if our frankenstein AMD CPU can recover from
memory errors?

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: KVM <kvm@vger.kernel.org>,
	"Marcelo Tosatti" <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Huang Ying" <ying.huang@intel.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] target-i386: Do not set MCG_SER_P by default
Date: Mon, 23 Nov 2015 15:47:44 +0100	[thread overview]
Message-ID: <56532710.8030607@redhat.com> (raw)
In-Reply-To: <20151123132237.GM23717@thinpad.lan.raisama.net>



On 23/11/2015 14:22, Eduardo Habkost wrote:
> > Software Error Recovery, i.e. SER, is purely an Intel feature and it
> > shouldn't be set by default. Enable it only on Intel.
> 
> What happens when SER is enabled on an AMD CPU? If it really
> should't be enabled, why is KVM returning it on
> KVM_X86_GET_MCE_CAP_SUPPORTED?

Indeed... is it a problem if our frankenstein AMD CPU can recover from
memory errors?

Paolo

  reply	other threads:[~2015-11-23 14:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 23:01 [PATCH] target-i386: Do not set MCG_SER_P by default Borislav Petkov
2015-11-20 23:11 ` Andreas Färber
2015-11-20 23:11   ` [Qemu-devel] " Andreas Färber
2015-11-21  1:09   ` Borislav Petkov
2015-11-21  1:09     ` [Qemu-devel] " Borislav Petkov
2015-11-23 13:22     ` Eduardo Habkost
2015-11-23 13:22       ` [Qemu-devel] " Eduardo Habkost
2015-11-23 14:47       ` Paolo Bonzini [this message]
2015-11-23 14:47         ` Paolo Bonzini
2015-11-23 15:03         ` Borislav Petkov
2015-11-23 15:03           ` [Qemu-devel] " Borislav Petkov
2015-11-23 15:11       ` MCG_CAP ABI breakage (was Re: [Qemu-devel] [PATCH] target-i386: Do not set MCG_SER_P by default) Eduardo Habkost
2015-11-23 15:11         ` [Qemu-devel] MCG_CAP ABI breakage (was " Eduardo Habkost
2015-11-23 16:43         ` MCG_CAP ABI breakage (was Re: [Qemu-devel] " Borislav Petkov
2015-11-23 16:43           ` [Qemu-devel] MCG_CAP ABI breakage (was " Borislav Petkov
2015-11-23 19:42           ` MCG_CAP ABI breakage (was Re: [Qemu-devel] " Eduardo Habkost
2015-11-23 19:42             ` [Qemu-devel] MCG_CAP ABI breakage (was " Eduardo Habkost
2015-11-23 20:46             ` MCG_CAP ABI breakage (was Re: [Qemu-devel] " Borislav Petkov
2015-11-23 20:46               ` [Qemu-devel] MCG_CAP ABI breakage (was " Borislav Petkov
2015-11-24 16:36           ` MCG_CAP ABI breakage (was Re: [Qemu-devel] " Eduardo Habkost
2015-11-24 16:36             ` [Qemu-devel] MCG_CAP ABI breakage (was " Eduardo Habkost
2015-11-24 18:44             ` MCG_CAP ABI breakage (was Re: [Qemu-devel] " Borislav Petkov
2015-11-24 18:44               ` [Qemu-devel] MCG_CAP ABI breakage (was " Borislav Petkov

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=56532710.8030607@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=bp@alien8.de \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=ying.huang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.