From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51321)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andrey@xdel.ru>) id 1Yd0pD-00028s-HR
	for qemu-devel@nongnu.org; Tue, 31 Mar 2015 14:23:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andrey@xdel.ru>) id 1Yd0pC-0004G7-Gg
	for qemu-devel@nongnu.org; Tue, 31 Mar 2015 14:23:43 -0400
Received: from mail-la0-x22c.google.com ([2a00:1450:4010:c03::22c]:35830)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andrey@xdel.ru>) id 1Yd0pC-0004Fq-4F
	for qemu-devel@nongnu.org; Tue, 31 Mar 2015 14:23:42 -0400
Received: by lahf3 with SMTP id f3so18856232lah.2
	for <qemu-devel@nongnu.org>; Tue, 31 Mar 2015 11:23:41 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <jpgbnj911s9.fsf@redhat.com>
References: <CABYiri_D-Y8uxW30ddwomnbotCFFWLEKU7rona761W5yo66-zQ@mail.gmail.com>
	<20150326174056.GC13271@potion.brq.redhat.com>
	<CABYiri-TZp51en0cdE9k=iq3dr-eVM=+Z2vx89R81V97CgUp2Q@mail.gmail.com>
	<20150326204053.GC27093@potion.brq.redhat.com>
	<jpgoanfo4iu.fsf@redhat.com>
	<CABYiri95_Ykg-fub0UvcHqHDKQ7Ufu4n05FhVqE8RwzjeqeATA@mail.gmail.com>
	<20150330185634.GE13271@potion.brq.redhat.com>
	<CABYiri9KOP5zjJVAzC70C=eruUwriHpu0YL_HUeUmbvB7ZSA_w@mail.gmail.com>
	<20150331134512.GG13271@potion.brq.redhat.com>
	<CABYiri8fK3zta+m0eVpStn9vRmU5-doDim9JG2sr1uGFhMkWfg@mail.gmail.com>
	<20150331164539.GD14262@potion.brq.redhat.com>
	<CABYiri8XjGNsoumb=d0EffpO3GRL8NT83kadSQyQYCdC3svb7Q@mail.gmail.com>
	<jpga8ytrqpi.fsf@redhat.com> <jpgbnj911s9.fsf@redhat.com>
From: Andrey Korolyov <andrey@xdel.ru>
Date: Tue, 31 Mar 2015 21:23:20 +0300
Message-ID: <CABYiri8N48vc71sdnwyTeChUPgG=iHnU4MnV_4-9DPkPxP_Xbg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] E5-2620v2 - emulation stop error
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Bandan Das <bsd@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>, =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= <rkrcmar@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>, Kevin O'Connor <kevin@koconnor.net>, Gerd Hoffmann <kraxel@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>

On Tue, Mar 31, 2015 at 9:04 PM, Bandan Das <bsd@redhat.com> wrote:
> Bandan Das <bsd@redhat.com> writes:
>
>> Andrey Korolyov <andrey@xdel.ru> writes:
>> ...
>>> http://xdel.ru/downloads/kvm-e5v2-issue/another-tracepoint-fail-with-apicv.dat.gz
>>>
>>> Something a bit more interesting, but the mess is happening just
>>> *after* NMI firing.
>>
>> What happens if NMI is turned off on the host ?
>
> Sorry, I meant the watchdog..


Thanks, everything goes well (as it probably should go there):
http://xdel.ru/downloads/kvm-e5v2-issue/apicv-enabled-nmi-disabled.dat.gz