From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O1gHm-0007Qk-KN for qemu-devel@nongnu.org; Tue, 13 Apr 2010 09:36:14 -0400 Received: from [140.186.70.92] (port=60702 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O1gHg-0007Lp-29 for qemu-devel@nongnu.org; Tue, 13 Apr 2010 09:36:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O1gHd-0006qq-L0 for qemu-devel@nongnu.org; Tue, 13 Apr 2010 09:36:07 -0400 Received: from david.siemens.de ([192.35.17.14]:16004) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O1gHd-0006qQ-B1 for qemu-devel@nongnu.org; Tue, 13 Apr 2010 09:36:05 -0400 Message-ID: <4BC47340.3030407@siemens.com> Date: Tue, 13 Apr 2010 15:36:00 +0200 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Missing singlestep for already-translated code? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jun Koi Cc: qemu-devel@nongnu.org Jun Koi wrote: > Hi, > > I am looking into the singlestep command in monitor interface, and it > seems that we only take into account the singlestep flag when we are > translating code. > So for the already-translated code, we will miss singlestep? This feature is broken. For TCG, it should at least flush the translation buffer, and for KVM it has to enable single-stepping in the kernel. That's what happens automatically when you call cpu_single_step. I guess 'singlestep' wants to be somehow orthogonal to this. But this is the wrong approach. Does anyone actually used this feature or still does so? It looks fairly redundant to me, kind of a poor-man's gdb front-end as part of the monitor console. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux