linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@01.org
Subject: Re: [KVM] BUG: unable to handle kernel NULL pointer dereference at 00000000000002b0
Date: Thu, 27 Mar 2014 10:56:41 +0800	[thread overview]
Message-ID: <20140327025641.GA12099@localhost> (raw)
In-Reply-To: <5332F668.8080601@redhat.com>

On Wed, Mar 26, 2014 at 04:46:48PM +0100, Paolo Bonzini wrote:
> Il 26/03/2014 15:57, Fengguang Wu ha scritto:
> >>>> >
> >>>> >git://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
> >>>> >commit 93c4adc7afedf9b0ec190066d45b6d67db5270da ("KVM: x86: handle missing MPX in nested virtualization")
> >>>
> >>> Ouch.  Out of curiosity is this on Skylake prototypes, or is it also
> >>> visible on some released silicon?
> >Paolo, the problem shows up in a Sandybridge-EX and an Ivybridge-EX.
> 
> What does that mean in terms of commercial names?  I tested on Sandy
> Bridge Xeon E5.

Sorry I don't know the exact commercial names listed in

http://en.wikipedia.org/wiki/Sandy_Bridge
http://en.wikipedia.org/wiki/Ivy_Bridge_%28microarchitecture%29

Thanks,
Fengguang

  reply	other threads:[~2014-03-27  2:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 14:40 [KVM] BUG: unable to handle kernel NULL pointer dereference at 00000000000002b0 Fengguang Wu
2014-03-26 14:50 ` Paolo Bonzini
2014-03-26 14:57   ` Fengguang Wu
2014-03-26 15:46     ` Paolo Bonzini
2014-03-27  2:56       ` Fengguang Wu [this message]
2014-03-26 14:52 ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2014-04-14  7:49 Jet Chen
2014-04-28  9:33 ` Paolo Bonzini
2014-04-28  9:54   ` Jet Chen
2014-04-28 11:34     ` Paolo Bonzini
2014-04-28 13:52       ` Jet Chen

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=20140327025641.GA12099@localhost \
    --to=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=pbonzini@redhat.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).