From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMaeF-0006wK-9A for qemu-devel@nongnu.org; Wed, 27 Aug 2014 06:40:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XMae7-0005hx-Qj for qemu-devel@nongnu.org; Wed, 27 Aug 2014 06:40:15 -0400 Message-ID: <53FDB587.1030505@suse.de> Date: Wed, 27 Aug 2014 12:40:07 +0200 From: Alexander Graf MIME-Version: 1.0 References: <20140825134353.2361.52046.stgit@aravindap> <20140825134554.2361.45051.stgit@aravindap> In-Reply-To: <20140825134554.2361.45051.stgit@aravindap> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 5/5] target-ppc: Handle cases when multi-processors get machine-check List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aravinda Prasad , aik@au1.ibm.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org Cc: benh@au1.ibm.com, paulus@samba.org On 25.08.14 15:45, Aravinda Prasad wrote: > It is possible for multi-processors to experience machine > check at or about the same time. As per PAPR, subsequent > processors serialize waiting for the first processor to > issue the ibm,nmi-interlock call. > > The second processor retries if the first processor which > received a machine check is still reading the error log > and is yet to issue ibm,nmi-interlock call. > > This patch implements this functionality. > > Signed-off-by: Aravinda Prasad This patch doesn't make any sense. Both threads will issue an HCALL which will get locked inside of QEMU, so we'll never see the case where both hypercalls get processed at the same time. Alex