From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v2] KVM: x86: Inject pending interrupt even if pending nmi exist Date: Wed, 23 Mar 2016 22:11:00 +0100 Message-ID: <56F30664.8050006@redhat.com> References: <7CC7D3013F4B10479273CE019E6A8C7A3ED90C@BPXM15GP.gisp.nec.co.jp> <56F297A7.1030309@redhat.com> <20160323172159.GA22164@potion.brq.redhat.com> <56F2DEDD.5060600@redhat.com> <20160323190406.GB22164@potion.brq.redhat.com> <56F3040B.8070006@redhat.com> <56F3055C.8090004@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Yuki Shibuya , "kvm@vger.kernel.org" , Nobuo Yoshida To: Jan Kiszka , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= Return-path: Received: from mail-wm0-f66.google.com ([74.125.82.66]:34826 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751447AbcCWVLF (ORCPT ); Wed, 23 Mar 2016 17:11:05 -0400 Received: by mail-wm0-f66.google.com with SMTP id r129so1973925wmr.2 for ; Wed, 23 Mar 2016 14:11:03 -0700 (PDT) In-Reply-To: <56F3055C.8090004@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 23/03/2016 22:06, Jan Kiszka wrote: > > There is also at least one case where you could have one pending (but > > not injected) and one latched NMI at instruction boundary, and that is > > the special NMI shadow from the STI instruction. > > This sounds to me like we should try to address the issue Yuki is seeing > without playing with the nmi_pending counter. Yes, it would be nice if my suggestion worked. :) Paolo