From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57536) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WugGr-0003iI-4n for qemu-devel@nongnu.org; Wed, 11 Jun 2014 07:00:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WugGj-0002An-DP for qemu-devel@nongnu.org; Wed, 11 Jun 2014 07:00:45 -0400 Message-ID: <1402484395.14780.48.camel@pasglop> From: Benjamin Herrenschmidt Date: Wed, 11 Jun 2014 20:59:55 +1000 In-Reply-To: <539833C4.5090101@redhat.com> References: <1401869330-32449-1-git-send-email-aik@ozlabs.ru> <1401869330-32449-2-git-send-email-aik@ozlabs.ru> <20140610093951.6dd64ea4@redhat.com> <20140610164107.249d8290.cornelia.huck@de.ibm.com> <20140610104847.1cb5a424@redhat.com> <53973277.4090500@redhat.com> <539749EB.2050608@suse.de> <1A9DA1AC-C696-452F-8D7E-68C49E339785@suse.de> <5397E230.8020605@redhat.com> <53980CCB.2040306@suse.de> <5398130D.8040706@redhat.com> <53981381.6060302@suse.de> <53981549.2090307@redhat.com> <53981691.9020407@suse.de> <539833C4.5090101@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v3 1/4] cpus: Define NMI callback List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Peter Maydell , Stefan Hajnoczi , QEMU Developers , Markus Armbruster , Alexander Graf , "qemu-ppc@nongnu.org" , Alex Bligh , Cornelia Huck , Luiz Capitulino , Andreas =?ISO-8859-1?Q?F=E4rber?= , Richard Henderson On Wed, 2014-06-11 at 12:47 +0200, Paolo Bonzini wrote: > Ok, I can buy removing the support for CPU != 0. But still, the > overengineering remains. > > If Alexey needs to trigger the NMI on all CPUs, simply moving the new > method from CPU to Machine, and blindly using first_cpu in s390 and x86 > makes the most sense. I can imagine a future where we would want to programatically trigger the sreset (the NMI is basically a soft reset for us) on a specific target CPU so it does make some sense to have a per CPU method and have the monitor "nmi" command call it on all of them. But it's not a huge deal if you decide to just make it as machine for now. This is more than just a "debug" feature however, it is generally used to trigger kdump on crashed partitions (this feature is called "dump" in pHyp). Cheers, Ben.