From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jrwbt-0006o8-DS for qemu-devel@nongnu.org; Fri, 02 May 2008 10:51:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jrwbo-0006gy-Rv for qemu-devel@nongnu.org; Fri, 02 May 2008 10:51:39 -0400 Received: from [199.232.76.173] (port=36313 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jrwbn-0006gp-Vs for qemu-devel@nongnu.org; Fri, 02 May 2008 10:51:36 -0400 Received: from tim.rpsys.net ([194.106.48.114]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jrwbm-0000lf-HV for qemu-devel@nongnu.org; Fri, 02 May 2008 10:51:35 -0400 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id m42EpTN6025257 for ; Fri, 2 May 2008 15:51:29 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25188-02 for ; Fri, 2 May 2008 15:51:24 +0100 (BST) Received: from [192.168.1.3] (dax.rpnet.com [192.168.1.3]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id m42EpKdK025251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 2 May 2008 15:51:20 +0100 Subject: Re: [Qemu-devel] Qemu and mmap_min_addr From: Richard Purdie In-Reply-To: <481874A7.7000704@hut.fi> References: <48185B4D.4060903@hut.fi> <200804301331.32869.paul@codesourcery.com> <481874A7.7000704@hut.fi> Content-Type: text/plain Date: Fri, 02 May 2008 15:51:19 +0100 Message-Id: <1209739879.5184.16.camel@dax.rpnet.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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 On Wed, 2008-04-30 at 16:31 +0300, Jussi Hakala wrote: > Paul Brook wrote: > > You have to use a nonzero GUEST_BASE to offset the guest VM. However this > > hasn't been tested in a while, and has probably bitrotted. > > For preliminary testing, setting GUEST_BASE to 65536 seemed to work. > I'll investigate further and report back to you :) I was also looking at this problem and setting GUEST_BASE seemed to fix my test cases although I've not tried it in a wider environment. I was wondering if mismatching the host and guest memory layouts like that incurred a performance penalty though? Regards, Richard