From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HzYJI-00076U-7r for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:27:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HzYJG-00076G-U5 for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:27:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HzYJG-00076D-Oy for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:27:22 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HzYJG-0008Dj-87 for qemu-devel@nongnu.org; Sat, 16 Jun 2007 09:27:22 -0400 From: Paul Brook Subject: Re: [Qemu-devel] TB Chaining NOT Reset on TLB Flush?? Date: Sat, 16 Jun 2007 14:27:05 +0100 References: <20070616132206.GA7968@163.com> In-Reply-To: <20070616132206.GA7968@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706161427.06630.paul@codesourcery.com> 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, amateur > 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?? The internals documentation is out of date. TBs are only chained directly when both source and destination are on the same page. Paul