From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38631) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAhJU-0006hz-TI for qemu-devel@nongnu.org; Thu, 02 Jul 2015 12:26:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZAhJP-0006Tx-Ks for qemu-devel@nongnu.org; Thu, 02 Jul 2015 12:26:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58023) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAhJP-0006To-GP for qemu-devel@nongnu.org; Thu, 02 Jul 2015 12:26:07 -0400 References: <1435853275-5440-1-git-send-email-den@openvz.org> <1435853275-5440-12-git-send-email-den@openvz.org> <5595645A.6070402@suse.de> From: Paolo Bonzini Message-ID: <5595661A.1050303@redhat.com> Date: Thu, 2 Jul 2015 18:26:02 +0200 MIME-Version: 1.0 In-Reply-To: <5595645A.6070402@suse.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 11/12] qemu: add crash_occurred flag into CPUState List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Andreas_F=c3=a4rber?= , "Denis V. Lunev" Cc: Andrey Smetanin , qemu-devel@nongnu.org, kvm@vger.kernel.org On 02/07/2015 18:18, Andreas F=C3=A4rber wrote: >> > + uint32_t crash_occurred; >> > volatile sig_atomic_t exit_request; >> > uint32_t interrupt_request; >> > int singlestep_enabled; > If you add this field to CPUState, you'll also need to reset it in > qom/cpu.c. Or is it intentionally persistent? And since you are at it, you can make it a bool. Paolo