Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751974Ab2KHEGY (ORCPT ); Wed, 7 Nov 2012 23:06:24 -0500 Received: from mail-bk0-f46.google.com ([209.85.214.46]:37187 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751113Ab2KHEGW (ORCPT ); Wed, 7 Nov 2012 23:06:22 -0500 MIME-Version: 1.0 In-Reply-To: <20121108014043.GA22057@phenom.dumpdata.com> References: <1349827115-16600-1-git-send-email-yinghai@kernel.org> <20121030134442.GB27463@phenom.dumpdata.com> <20121107161144.GA18353@phenom.dumpdata.com> <20121108014043.GA22057@phenom.dumpdata.com> Date: Wed, 7 Nov 2012 20:06:21 -0800 X-Google-Sender-Auth: WakN9o_NGgZQ9z7W34ujlv47klQ Message-ID: Subject: Re: [PATCH -v3 0/7] x86: Use BRK to pre mapping page table to make xen happy From: Yinghai Lu To: Konrad Rzeszutek Wilk Cc: "H. Peter Anvin" , Stefano Stabellini , Andrew Morton , Jacob Shin , Ingo Molnar , Thomas Gleixner , Tejun Heo , "linux-kernel@vger.kernel.org" Content-Type: multipart/mixed; boundary=0015174c11c63240cb04cdf3f52c Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3392 Lines: 70 --0015174c11c63240cb04cdf3f52c Content-Type: text/plain; charset=ISO-8859-1 On Wed, Nov 7, 2012 at 5:40 PM, Konrad Rzeszutek Wilk wrote: > > I ran in a problem with launching an 8GB guest. When launching a 4GB it worked > fine, but with 8GB I get: > > .000000] init_memory_mapping: [mem 0x1f4000000-0x1f47fffff] > [ 0.000000] [mem 0x1f4000000-0x1f47fffff] page 4k > [ 0.000000] memblock_reserve: [0x000001f311c000-0x000001f311d000] alloc_low_pages+0x103/0x130 > [ 0.000000] memblock_reserve: [0x000001f311b000-0x000001f311c000] alloc_low_pages+0x103/0x130 > [ 0.000000] memblock_reserve: [0x000001f311a000-0x000001f311b000] alloc_low_pages+0x103/0x130 > [ 0.000000] memblock_reserve: [0x000001f3119000-0x000001f311a000] alloc_low_pages+0x103/0x130 > [ 0.000000] Kernel panic - not syncing: initrd too large to handle, disabling initrd (348401664 needed, 524288 available) > [ 0.000000] > [ 0.000000] Pid: 0, comm: swapper Not tainted 3.7.0-rc4upstream-00042-g1b66ccf #1 > [ 0.000000] Call Trace: > [ 0.000000] [] panic+0xbf/0x1df > [ 0.000000] [] setup_arch+0x728/0xb29 > [ 0.000000] [] ? printk+0x48/0x4a > [ 0.000000] [] start_kernel+0x90/0x39e > [ 0.000000] [] x86_64_start_reservations+0x131/0x136 > [ 0.000000] [] xen_start_kernel+0x546/0x548 > xen memmap [ 0.000000] Xen: [mem 0x0000000000000000-0x000000000009ffff] usable [ 0.000000] Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved [ 0.000000] Xen: [mem 0x0000000000100000-0x00000001f47fffff] usable there is no hole under 4G, trigger the bug about max_low_pfn_mapped updating in add_pfn_range_mapped(). please check attached patch, that should fix the problem. then I will fold it into corresponding commit that instroduce add_pfn_range_mapped(). Thanks Yinghai --0015174c11c63240cb04cdf3f52c Content-Type: application/octet-stream; name="fix_max_low_pfn_mapped.patch" Content-Disposition: attachment; filename="fix_max_low_pfn_mapped.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h99ctm6n1 LS0tCiBhcmNoL3g4Ni9tbS9pbml0LmMgfCAgICA1ICsrKy0tCiAxIGZpbGUgY2hhbmdlZCwgMyBp bnNlcnRpb25zKCspLCAyIGRlbGV0aW9ucygtKQoKSW5kZXg6IGxpbnV4LTIuNi9hcmNoL3g4Ni9t bS9pbml0LmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PQotLS0gbGludXgtMi42Lm9yaWcvYXJjaC94ODYvbW0vaW5pdC5j CisrKyBsaW51eC0yLjYvYXJjaC94ODYvbW0vaW5pdC5jCkBAIC0zMDUsOCArMzA1LDkgQEAgc3Rh dGljIHZvaWQgYWRkX3Bmbl9yYW5nZV9tYXBwZWQodW5zaWduZQogCiAJbWF4X3Bmbl9tYXBwZWQg PSBtYXgobWF4X3Bmbl9tYXBwZWQsIGVuZF9wZm4pOwogCi0JaWYgKGVuZF9wZm4gPD0gKDFVTCA8 PCAoMzIgLSBQQUdFX1NISUZUKSkpCi0JCW1heF9sb3dfcGZuX21hcHBlZCA9IG1heChtYXhfbG93 X3Bmbl9tYXBwZWQsIGVuZF9wZm4pOworCWlmIChzdGFydF9wZm4gPCAoMVVMPDwoMzItUEFHRV9T SElGVCkpKQorCQltYXhfbG93X3Bmbl9tYXBwZWQgPSBtYXgobWF4X2xvd19wZm5fbWFwcGVkLAor CQkJCQkgbWluKGVuZF9wZm4sIDFVTDw8KDMyLVBBR0VfU0hJRlQpKSk7CiB9CiAKIGJvb2wgcGZu X3JhbmdlX2lzX21hcHBlZCh1bnNpZ25lZCBsb25nIHN0YXJ0X3BmbiwgdW5zaWduZWQgbG9uZyBl bmRfcGZuKQo= --0015174c11c63240cb04cdf3f52c-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/