From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52331) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YBL5Q-0003uI-Nr for qemu-devel@nongnu.org; Wed, 14 Jan 2015 05:22:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YBL5H-0006te-Lx for qemu-devel@nongnu.org; Wed, 14 Jan 2015 05:22:04 -0500 Received: from mail-we0-x22c.google.com ([2a00:1450:400c:c03::22c]:57577) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YBL5H-0006tU-FG for qemu-devel@nongnu.org; Wed, 14 Jan 2015 05:21:55 -0500 Received: by mail-we0-f172.google.com with SMTP id k11so7860111wes.3 for ; Wed, 14 Jan 2015 02:21:55 -0800 (PST) Sender: Paolo Bonzini Message-ID: <54B6433E.3030702@redhat.com> Date: Wed, 14 Jan 2015 11:21:50 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <20150112115944.3504.66763.stgit@PASHA-ISP> <20150112120032.3504.11086.stgit@PASHA-ISP> <54B3BF3B.7020403@redhat.com> <001301d02e64$f192c740$d4b855c0$@Dovgaluk@ispras.ru> <54B3C404.4050603@redhat.com> <3141.42739302969$1421226482@news.gmane.org> <54B63B8E.5010708@redhat.com> <48665.1020743468$1421230035@news.gmane.org> In-Reply-To: <48665.1020743468$1421230035@news.gmane.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v7 08/21] replay: interrupts and exceptions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pavel Dovgaluk , qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, peter.crosthwaite@xilinx.com, mark.burton@greensocs.com, real@ispras.ru, batuzovk@ispras.ru, maria.klimushenkova@ispras.ru, alex.bennee@linaro.org, afaerber@suse.de, fred.konrad@greensocs.com On 14/01/2015 11:06, Pavel Dovgaluk wrote: >> > I think it is okay. INIT executes cpu_loop_exit() on x86 because >> > processors other than the boot processor are halted after they receive INIT. > Then I cannot put everything in one if-else chain because it will change the behavior of the code. > After processing RESET branch we can also process hardware interrupts (in unmodified code). Then if it's simpler you can add cpu_loop_exit(). It's not required, but it's also definitely not a fast path. Paolo