From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41090) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlYt2-0000tn-AZ for qemu-devel@nongnu.org; Wed, 27 Nov 2013 01:46:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VlYsw-0004XY-Be for qemu-devel@nongnu.org; Wed, 27 Nov 2013 01:46:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:31067) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlYsw-0004XR-3H for qemu-devel@nongnu.org; Wed, 27 Nov 2013 01:46:06 -0500 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id rAR6k58T030677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 27 Nov 2013 01:46:05 -0500 Message-ID: <1385534761.13867.9.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Wed, 27 Nov 2013 07:46:01 +0100 In-Reply-To: <52951398.3010206@redhat.com> References: <1385482583-23122-1-git-send-email-kraxel@redhat.com> <52951398.3010206@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] piix: fix 32bit pci hole List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: qemu-devel@nongnu.org > > + i440fx->pci_info.w32.begin = ram_size; > But this patch also obliterates the high bound, 0xe0000000, which can > lead to: > - w32.end - w32.begin <= 512M, or > - a special case of the former, w32.end < w32.begin. ram_size is not the total amount of memory, it is low memory only. There is another parameter to i440fx_init (above_4g_mem_size) which holds the amount of memory which is going to be mapped above 4G. Maximum possible value of ram_size is 0xe0000000. For completeness: On q35 the maximum amount of low mem is 0xb0000000. > w32.end is set to IO_APIC_DEFAULT_ADDRESS==0xfec00000. (Which is BTW > fine for OVMF too.) What will happen in a 6G guest, for example? ram_size = 0xe0000000 above_4g_mem_size = 0xa0000000 cheers, Gerd