From: Paolo Bonzini <pbonzini@redhat.com>
To: lkp@lists.01.org
Subject: Re: [KVM] BUG: unable to handle kernel NULL pointer dereference at 00000000000002b0
Date: Wed, 26 Mar 2014 16:46:48 +0100 [thread overview]
Message-ID: <5332F668.8080601@redhat.com> (raw)
In-Reply-To: <20140326145701.GA27938@localhost>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
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.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fengguang Wu <fengguang.wu@intel.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: Wed, 26 Mar 2014 16:46:48 +0100 [thread overview]
Message-ID: <5332F668.8080601@redhat.com> (raw)
In-Reply-To: <20140326145701.GA27938@localhost>
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.
Paolo
next prev parent reply other threads:[~2014-03-26 15:46 UTC|newest]
Thread overview: 22+ 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:40 ` Fengguang Wu
2014-03-26 14:50 ` Paolo Bonzini
2014-03-26 14:50 ` Paolo Bonzini
2014-03-26 14:57 ` Fengguang Wu
2014-03-26 14:57 ` Fengguang Wu
2014-03-26 15:46 ` Paolo Bonzini [this message]
2014-03-26 15:46 ` Paolo Bonzini
2014-03-27 2:56 ` Fengguang Wu
2014-03-27 2:56 ` Fengguang Wu
2014-03-26 14:52 ` Paolo Bonzini
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-14 7:49 ` Jet Chen
2014-04-28 9:33 ` Paolo Bonzini
2014-04-28 9:33 ` Paolo Bonzini
2014-04-28 9:54 ` Jet Chen
2014-04-28 9:54 ` Jet Chen
2014-04-28 11:34 ` Paolo Bonzini
2014-04-28 11:34 ` Paolo Bonzini
2014-04-28 13:52 ` Jet Chen
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=5332F668.8080601@redhat.com \
--to=pbonzini@redhat.com \
--cc=lkp@lists.01.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 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.