From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41578) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTAwp-0008Mb-4m for qemu-devel@nongnu.org; Thu, 27 Mar 2014 10:06:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WTAwj-00063C-6V for qemu-devel@nongnu.org; Thu, 27 Mar 2014 10:06:23 -0400 Message-ID: <53343053.40200@redhat.com> Date: Thu, 27 Mar 2014 15:06:11 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1395886880-11021-1-git-send-email-aik@ozlabs.ru> <1395886880-11021-3-git-send-email-aik@ozlabs.ru> <53341281.8090907@redhat.com> <5334242E.1010806@ozlabs.ru> In-Reply-To: <5334242E.1010806@ozlabs.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/2] spapr: Define NMI interface List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexey Kardashevskiy , qemu-devel@nongnu.org Cc: qemu-ppc@nongnu.org, =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Il 27/03/2014 14:14, Alexey Kardashevskiy ha scritto: > 1) how many x86 CPUs/families are there to support? On ppc I'll add it for > POWER7/7+/8 families and I am ok. Just move the existing x86 code. It works on all CPUs from 486 on. > 2) what should "nmi" really do - deliver NMI to the current CPU (as s390 > does) or on all CPUs (as x86 does)? As you prefer. Current CPU, as s390 does, was in your patch here and it's fine. I don't know why x86 delivers it to all CPUs. Paolo