From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM: Document KVM_NMI Date: Wed, 07 Dec 2011 12:21:30 +0200 Message-ID: <4EDF3E2A.3060208@redhat.com> References: <1323204643-17373-1-git-send-email-levinsasha928@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, Marcelo Tosatti , kvm@vger.kernel.org To: Sasha Levin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:52759 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754053Ab1LGKVd (ORCPT ); Wed, 7 Dec 2011 05:21:33 -0500 In-Reply-To: <1323204643-17373-1-git-send-email-levinsasha928@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/06/2011 10:50 PM, Sasha Levin wrote: > Cc: Avi Kivity > Cc: Marcelo Tosatti > Cc: kvm@vger.kernel.org Somehow, the changelog became the place where people manage their cc lists. > > +4.64 KVM_NMI > + > +Capability: basic > +Architectures: none > +Type: vcpu ioctl > +Parameters: none > +Returns: 0 on success, -1 on error > + > +Trigger an NMI on the specified VCPU. > + > +This can be used to cause a panic in the guest, which in turn would result > +in a backtrace/dump. > + I'm nitpicking, but this is too strongly worded. It's completely up to the guest how to interpret the NMI. It's also subtly broken with kernel irqchip - it injects an NMI unconditionally even though LINT1 can be configured to mask NMIs, or to do something other than queue an NMI (for example, queue a regular interrupt). Please note this. On second thoughts, I'll just document this instead of telling you what to write. -- error compiling committee.c: too many arguments to function