From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>,
"Michael S . Tsirkin" <mst@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Boris Petkov <bp@suse.de>,
Tony Luck <tony.luck@intel.com>,
Andi Kleen <andi.kleen@intel.com>,
rkrcmar@redhat.com, Ashok Raj <ashok.raj@intel.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/3] target-i386: add migration support for Intel LMCE
Date: Mon, 20 Jun 2016 08:58:29 +0200 [thread overview]
Message-ID: <b53dffce-7b05-3480-8749-460f80617476@redhat.com> (raw)
In-Reply-To: <20160620021136.mepymwylqvzsku55@hz-desktop>
On 20/06/2016 04:11, Haozhong Zhang wrote:
>>> > > Does that mean we can automatically enable LMCE for "-cpu host"?
>> >
>> > We can automatically enable LMCE for "-cpu host" if and only if
>> > the host kernel supports LMCE.
>> >
> According to our discussion for KVM Patch 3, we may have to disable it
> by default by -cpu host, so that pc-2.7 will not require new kernels
> unless LMCE is required explicitly by users.
-cpu host is a bit special, it requires the same processor and kernel on
both sides of a migration. So it can enable LMCE.
Paolo
next prev parent reply other threads:[~2016-06-20 6:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 6:06 [Qemu-devel] [PATCH v4 0/3] Add QEMU support for Intel local MCE Haozhong Zhang
2016-06-16 6:06 ` [Qemu-devel] [PATCH v4 1/3] target-i386: KVM: add basic Intel LMCE support Haozhong Zhang
2016-06-16 9:50 ` Paolo Bonzini
2016-06-16 10:16 ` Haozhong Zhang
2016-06-16 10:23 ` Paolo Bonzini
2016-06-16 10:34 ` Haozhong Zhang
2016-06-16 10:42 ` Paolo Bonzini
2016-06-16 18:05 ` Eduardo Habkost
2016-06-16 18:17 ` Paolo Bonzini
2016-06-16 19:37 ` Eduardo Habkost
2016-06-17 1:26 ` Haozhong Zhang
2016-06-17 16:20 ` Eduardo Habkost
2016-06-20 2:04 ` Haozhong Zhang
2016-06-16 6:06 ` [Qemu-devel] [PATCH v4 2/3] target-i386: add migration support for Intel LMCE Haozhong Zhang
2016-06-16 9:51 ` Paolo Bonzini
2016-06-16 10:29 ` Haozhong Zhang
2016-06-16 10:41 ` Paolo Bonzini
2016-06-16 10:55 ` Haozhong Zhang
2016-06-16 17:36 ` Eduardo Habkost
2016-06-16 17:40 ` Paolo Bonzini
2016-06-16 17:58 ` Eduardo Habkost
2016-06-17 2:01 ` Haozhong Zhang
2016-06-17 17:20 ` Eduardo Habkost
2016-06-17 17:26 ` Paolo Bonzini
2016-06-20 2:11 ` Haozhong Zhang
2016-06-20 6:58 ` Paolo Bonzini [this message]
2016-06-20 7:26 ` Haozhong Zhang
2016-06-16 19:53 ` Eduardo Habkost
2016-06-16 6:06 ` [Qemu-devel] [PATCH v4 3/3] i386: publish advised value of MSR_IA32_FEATURE_CONTROL via fw_cfg Haozhong Zhang
2016-06-16 9:52 ` Paolo Bonzini
2016-06-16 11:19 ` Haozhong Zhang
2016-06-17 17:31 ` Laszlo Ersek
2016-06-17 20:21 ` Raj, Ashok
2016-06-17 20:48 ` Laszlo Ersek
2016-06-17 20:55 ` Raj, Ashok
2016-06-17 21:30 ` Laszlo Ersek
2016-06-20 3:09 ` Haozhong Zhang
2016-06-20 6:56 ` Paolo Bonzini
2016-06-20 7:20 ` Haozhong Zhang
2016-06-22 10:18 ` Haozhong Zhang
2016-06-22 15:51 ` Laszlo Ersek
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=b53dffce-7b05-3480-8749-460f80617476@redhat.com \
--to=pbonzini@redhat.com \
--cc=andi.kleen@intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@suse.de \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=rth@twiddle.net \
--cc=tony.luck@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 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).