From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Hmcmx-0000Zi-Jq
	for qemu-devel@nongnu.org; Fri, 11 May 2007 17:36:35 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Hmcmt-0000ZW-4q
	for qemu-devel@nongnu.org; Fri, 11 May 2007 17:36:34 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Hmcms-0000ZT-Va
	for qemu-devel@nongnu.org; Fri, 11 May 2007 17:36:31 -0400
Received: from ik-out-1112.google.com ([66.249.90.178])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <shanesmith17@gmail.com>) id 1HmcfP-0002s9-RQ
	for qemu-devel@nongnu.org; Fri, 11 May 2007 17:28:48 -0400
Received: by ik-out-1112.google.com with SMTP id c28so783751ika
	for <qemu-devel@nongnu.org>; Fri, 11 May 2007 14:28:46 -0700 (PDT)
Message-ID: <ccc987170705111428t355d20aatd7f0fa4975208073@mail.gmail.com>
Date: Fri, 11 May 2007 14:28:45 -0700
From: "Shane Hummer-Smith" <shanesmith17@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_66655_7733717.1178918925513"
Subject: [Qemu-devel] <monitor.c>: mem_info and tlb_info
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

------=_Part_66655_7733717.1178918925513
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello there,

In the process of trying to understand the MMU and Paging in QEMU, I
stumbled upon the the following functions in monitor.c

- mem_info() and tlb_info()

Can somebody please tell me what's happenning within these functions -

I can see, though I'm not sure, that the physical memory is read for every
page directory (pgd?) and there is a condition check involving pde (page
directory entry?), some masks, and CR4, and stuff and more reads in an inner
loop. Even if I got this right, I have no clue what else is happenning in
there and _why?_. Can somebody please throw more light on what is happenning
within mem_info() and tlb_info() in monitor.c?


Thanks!
--S

------=_Part_66655_7733717.1178918925513
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello there,<br><br>In the process of trying to understand the MMU and Paging in QEMU, I stumbled upon the the following functions in monitor.c<br><br>- mem_info() and tlb_info()<br><br>Can somebody please tell me what&#39;s happenning within these functions - 
<br><br>I can see, though I&#39;m not sure, that the physical memory is read for every page directory (pgd?) and there is a condition check involving pde (page directory entry?), some masks, and CR4, and stuff and more reads in an inner loop. Even if I got this right, I have no clue what else is happenning in there and _why?_. Can somebody please throw more light on what is happenning within mem_info() and tlb_info() in 
monitor.c?<br><br><br>Thanks!<br>--S<br>

------=_Part_66655_7733717.1178918925513--