From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HzYCl-0005RE-5k for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:20:39 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HzYCi-0005R2-Pl for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:20:37 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HzYCi-0005Qz-II for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:20:36 -0400 Received: from py-out-1112.google.com ([64.233.166.178]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HzYCi-000796-9n for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:20:36 -0400 Received: by py-out-1112.google.com with SMTP id y77so2296797pyg for ; Sat, 16 Jun 2007 06:20:35 -0700 (PDT) Date: Sat, 16 Jun 2007 21:22:06 +0800 From: amateur Message-ID: <20070616132206.GA7968@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] TB Chaining NOT Reset on TLB Flush?? Reply-To: amateur , 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 Hi guys, I read from the Qemu internal documentation this: ``When MMU mappings change, only the chaining of the basic blocks is reset (i.e. a basic block can no longer jump directly to another one).'' But when I read the code, I find that tlb_flush() doesn't reset the chaining between TBs. Is that the intended behaviour?? Won't that cause problems on guest context switch?? -- If two people love each other, there can be no happy end to it. -- Ernest Hemingway