From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=36776 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OJrci-00079T-LE for qemu-devel@nongnu.org; Wed, 02 Jun 2010 13:21:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OJrca-0003Iz-42 for qemu-devel@nongnu.org; Wed, 02 Jun 2010 13:20:59 -0400 Received: from are.twiddle.net ([75.149.56.221]:41631) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OJrcZ-0003Io-VC for qemu-devel@nongnu.org; Wed, 02 Jun 2010 13:20:52 -0400 Message-ID: <4C0692F2.9060203@twiddle.net> Date: Wed, 02 Jun 2010 10:20:50 -0700 From: Richard Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Unposted reserved_va patch List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org Re: 68a1c816868b3e35a1da698af412b29e61b1948a In general, I like the idea (especially since I've proposed it before. ;-) However: + if (have_guest_base) { + flags |= MAP_FIXED; + } I think this is broken. If the user specifies -G n -R m they're hoping or guessing that the range [n,n+m) is free. What they're not expecting is for the qemu application or any of the required shared libraries to get forcibly unmapped. I think instead you should simply adjust the error reporting after the mmap attempt without MAP_FIXED. r~