public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Boris Petkov <bp@suse.de>
Cc: Haozhong Zhang <haozhong.zhang@intel.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	kvm@vger.kernel.org, Tony Luck <tony.luck@intel.com>,
	Andi Kleen <andi.kleen@intel.com>,
	Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH v3 1/2] target-i386: KVM: add basic Intel LMCE support
Date: Sat, 4 Jun 2016 18:03:17 -0300	[thread overview]
Message-ID: <20160604210317.GA17952@thinpad.lan.raisama.net> (raw)
In-Reply-To: <f2419649-16c0-4fc6-ba16-e38b72ef8c5f@email.android.com>

On Sat, Jun 04, 2016 at 12:34:39PM +0200, Boris Petkov wrote:
> Haozhong Zhang <haozhong.zhang@intel.com> wrote:
> 
> >This patch adds the support to inject SRAR and SRAO as LMCE, i.e. they
> >will be injected to only one VCPU rather than broadcast to all
> >VCPUs. As KVM reports LMCE support on Intel platforms, this features is
> >only available on Intel platforms.
> >
> >Signed-off-by: Ashok Raj <ashok.raj@intel.com>
> >Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> >---
> >Cc: Paolo Bonzini <pbonzini@redhat.com>
> >Cc: Richard Henderson <rth@twiddle.net>
> >Cc: Eduardo Habkost <ehabkost@redhat.com>
> >Cc: Marcelo Tosatti <mtosatti@redhat.com>
> >Cc: Boris Petkov <bp@suse.de>
> >Cc: kvm@vger.kernel.org
> >Cc: Tony Luck <tony.luck@intel.com>
> >Cc: Andi Kleen <andi.kleen@intel.com>
> >---
> > target-i386/cpu.c | 26 ++++++++++++++++++++++++++
> > target-i386/cpu.h | 13 ++++++++++++-
> > target-i386/kvm.c | 35 +++++++++++++++++++++++++++++++----
> > 3 files changed, 69 insertions(+), 5 deletions(-)
> 
> ...
> 
> >@@ -1173,6 +1182,8 @@ struct X86CPU {
> >      */
> >     bool enable_pmu;
> > 
> >+    bool enable_lmce;
> 
> That struct would go fat pretty fast if it grows a bool per CPU
> feature. Perhaps a more clever, a-bit-per-featurebit scheme
> would be in order.

We already have X86CPU.features, but it's specific for feature
flags appearing on CPUID. We can eventually extend
FeatureWord/FeatureWordInfo/x86_cpu_get_supported_feature_word()
to represent features that don't appear directly on CPUID.

-- 
Eduardo

  reply	other threads:[~2016-06-06 11:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03  6:09 [PATCH v3 0/2] Add QEMU support for Intel local MCE Haozhong Zhang
2016-06-03  6:09 ` [PATCH v3 1/2] target-i386: KVM: add basic Intel LMCE support Haozhong Zhang
2016-06-03 15:57   ` Radim Krčmář
2016-06-05 15:32     ` Haozhong Zhang
2016-06-08 11:32     ` Paolo Bonzini
2016-06-13  7:55       ` Haozhong Zhang
2016-06-13  8:33         ` Paolo Bonzini
2016-06-13 10:01           ` Haozhong Zhang
2016-06-13 10:07             ` Paolo Bonzini
2016-06-13 10:09               ` Haozhong Zhang
2016-06-04 10:15   ` Boris Petkov
2016-06-05 15:35     ` Haozhong Zhang
2016-06-04 10:34   ` Boris Petkov
2016-06-04 21:03     ` Eduardo Habkost [this message]
2016-06-07  9:41       ` Haozhong Zhang
2016-06-07 11:47         ` Haozhong Zhang
2016-06-05 15:41     ` Haozhong Zhang
2016-06-08 11:34       ` Paolo Bonzini
2016-06-09  6:52         ` Haozhong Zhang
2016-06-07 20:10   ` Eduardo Habkost
2016-06-08  1:43     ` Haozhong Zhang
2016-06-03  6:09 ` [PATCH v3 2/2] target-i386: add migration support for Intel LMCE Haozhong Zhang
2016-06-07 20:18   ` Eduardo Habkost
2016-06-08  1:56     ` Haozhong Zhang
2016-06-08 11:36   ` Paolo Bonzini
2016-06-09  7:16     ` Haozhong Zhang
2016-06-09  8:23       ` Paolo Bonzini
2016-06-03  6:38 ` [PATCH v3 0/2] Add QEMU support for Intel local MCE Haozhong Zhang

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=20160604210317.GA17952@thinpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=andi.kleen@intel.com \
    --cc=ashok.raj@intel.com \
    --cc=bp@suse.de \
    --cc=haozhong.zhang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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