From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KczGm-0008Rd-1C for qemu-devel@nongnu.org; Tue, 09 Sep 2008 05:12:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KczGh-0008Lg-Sd for qemu-devel@nongnu.org; Tue, 09 Sep 2008 05:12:19 -0400 Received: from [199.232.76.173] (port=49075 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KczGh-0008LP-Jb for qemu-devel@nongnu.org; Tue, 09 Sep 2008 05:12:15 -0400 Received: from mx2.redhat.com ([66.187.237.31]:51630) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KczGh-0003JG-89 for qemu-devel@nongnu.org; Tue, 09 Sep 2008 05:12:15 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id m899Bc2d025179 for ; Tue, 9 Sep 2008 05:11:59 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m899BRUB003906 for ; Tue, 9 Sep 2008 05:11:27 -0400 Received: from zweiblum.travel.kraxel.org (vpn-4-93.str.redhat.com [10.32.4.93]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id m899BQmt026955 for ; Tue, 9 Sep 2008 05:11:26 -0400 Message-ID: <48C63DBD.8040605@redhat.com> Date: Tue, 09 Sep 2008 11:11:25 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] physical memory allocation? 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 Hi folks, I've looked at the physical guest memory allocation code (aka qemu_vmalloc). Reason is that I need some way to map guest memory pages to a second location in virtual memory. Thus I need a filehandle for the memory, so I can mmap() pages from it somewhere. I've seen there is a phys_ram_fd variable defined in exec.c. It isn't used anywhere though. kqemu seems to have very simliar needs, there is some code to back guest memory using a file in /dev/shm. How about doing that *unconditionally*, not just for kqemu? cheers, Gerd