From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46556) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeO8H-00031e-9y for qemu-devel@nongnu.org; Tue, 12 Jun 2012 06:15:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SeO8B-0000DM-7K for qemu-devel@nongnu.org; Tue, 12 Jun 2012 06:15:28 -0400 Received: from e06smtp14.uk.ibm.com ([195.75.94.110]:33869) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeO8A-0000Cp-VX for qemu-devel@nongnu.org; Tue, 12 Jun 2012 06:15:23 -0400 Received: from /spool/local by e06smtp14.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 12 Jun 2012 11:15:20 +0100 Received: from d06av06.portsmouth.uk.ibm.com (d06av06.portsmouth.uk.ibm.com [9.149.37.217]) by d06nrmr1307.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q5CAFIdd2597010 for ; Tue, 12 Jun 2012 11:15:18 +0100 Received: from d06av06.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av06.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q5CAFIkj023700 for ; Tue, 12 Jun 2012 04:15:18 -0600 Message-ID: <4FD716B6.4030309@de.ibm.com> Date: Tue, 12 Jun 2012 12:15:18 +0200 From: Christian Borntraeger MIME-Version: 1.0 References: <1338984323-21914-1-git-send-email-jfrei@de.ibm.com> <1338984323-21914-5-git-send-email-jfrei@de.ibm.com> <4FD70F0A.8050609@suse.de> In-Reply-To: <4FD70F0A.8050609@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 4/8] s390: stop target cpu on sigp initial reset List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Jens Freimann , Cornelia Huck , Jens Freimann , Heinz Graalfs , qemu-devel On 12/06/12 11:42, Alexander Graf wrote: > Jens Freimann wrote: >> From: Christian Borntraeger >> >> We must not run the target cpu after an initial reset. This makes >> system_reset more reliable for smp guests. >> > > Why? After an initial reset, the cpu is in a state (PSW=0) that causes program check loops if the cpu thread starts before the cpu is properly set up, iow we might burn cpu and have the cpu in a state that it is not supposed to be. Christian