From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HkCJt-00058c-2V for qemu-devel@nongnu.org; Sat, 05 May 2007 00:56:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HkCJr-00058Q-64 for qemu-devel@nongnu.org; Sat, 05 May 2007 00:56:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HkCJr-00058N-1y for qemu-devel@nongnu.org; Sat, 05 May 2007 00:56:31 -0400 Received: from adsum.doit.wisc.edu ([144.92.197.210]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.60) (envelope-from ) id 1HkCD8-0000qH-LU for qemu-devel@nongnu.org; Sat, 05 May 2007 00:49:34 -0400 Received: from avs-daemon.smtpauth1.wiscmail.wisc.edu by smtpauth1.wiscmail.wisc.edu (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JHJ00A03XEJV900@smtpauth1.wiscmail.wisc.edu> for qemu-devel@nongnu.org; Fri, 04 May 2007 23:49:31 -0500 (CDT) Received: from [192.168.15.3] (eh-104-106-92.resnet.wisc.edu [146.151.106.92]) by smtpauth1.wiscmail.wisc.edu (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JHJ007EOXEHHW20@smtpauth1.wiscmail.wisc.edu> for qemu-devel@nongnu.org; Fri, 04 May 2007 23:49:29 -0500 (CDT) Date: Fri, 04 May 2007 23:52:08 -0500 From: Nuri Eady In-reply-to: Message-id: <463C0D78.8080303@wisc.edu> MIME-version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: 7BIT References: Subject: [Qemu-devel] Detecting a kernel stack change Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I'd like to detect when the kernel stack changes and it seems to me that might be possible by looking at when the tss structure is accessed and the esp element is changed. Linux uses a command something like the following to update the esp in the tss during a task switch... init_tss[smp_processor_id( )].esp0 = next->thread.esp0; Is it possible to detect when this happens in qemu? Maybe in the protected_interrupt helper function? Thanks, Nuri