From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: Re: [PATCH 1/3] s390/kvm: Set CPU in stopped state on initial cpu reset Date: Mon, 11 Jun 2012 18:46:43 +0200 Message-ID: <4FD620F3.4050405@suse.de> References: <1339423619-42299-1-git-send-email-cornelia.huck@de.ibm.com> <1339423619-42299-2-git-send-email-cornelia.huck@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Marcelo Tosatti , Christian Borntraeger , Carsten Otte , Heiko Carstens , Martin Schwidefsky , KVM , linux-s390 To: Cornelia Huck Return-path: Received: from cantor2.suse.de ([195.135.220.15]:40981 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754779Ab2FKQqr (ORCPT ); Mon, 11 Jun 2012 12:46:47 -0400 In-Reply-To: <1339423619-42299-2-git-send-email-cornelia.huck@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/11/2012 04:06 PM, Cornelia Huck wrote: > From: Christian Borntraeger > > The initial cpu reset sets the cpu in the stopped state. > Several places check for the cpu state (e.g. sigp set prefix) and > not setting the STOPPED state triggered errors with newer guest > kernels after reboot. > > Signed-off-by: Christian Borntraeger > Signed-off-by: Cornelia Huck Is this only broken as of now or has this been broken before? So do we need to send this to -stable for anyone? And what happens on RESET? Alex