Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755955AbbHYTBu (ORCPT ); Tue, 25 Aug 2015 15:01:50 -0400 Received: from mail-ig0-f170.google.com ([209.85.213.170]:36370 "EHLO mail-ig0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751210AbbHYTBt (ORCPT ); Tue, 25 Aug 2015 15:01:49 -0400 MIME-Version: 1.0 In-Reply-To: References: <1415089784-28779-1-git-send-email-daniel@numascale.com> <1415089784-28779-4-git-send-email-daniel@numascale.com> <20150821181910.GA31378@agluck-desk.sc.intel.com> <20150821202707.GA920@agluck-desk.sc.intel.com> Date: Tue, 25 Aug 2015 12:01:48 -0700 X-Google-Sender-Auth: -4AMJ9n2wHnhE7ZjzBM_Np0evtU Message-ID: Subject: Re: [PATCH v4 4/4] Use 2GB memory block size on large-memory x86-64 systems From: Yinghai Lu To: Tony Luck Cc: Daniel J Blueman , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Bjorn Helgaas , "the arch/x86 maintainers" , Linux Kernel Mailing List , "linux-pci@vger.kernel.org" , Steffen Persvold Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1325 Lines: 35 On Tue, Aug 25, 2015 at 10:03 AM, Tony Luck wrote: > On Mon, Aug 24, 2015 at 4:59 PM, Yinghai Lu wrote: >> attached should fix the problem: > > It does ... but this (attached) is simpler. Your patch and mine both > allow the system to boot ... The version that fix with section_nr present checking may save couple thousands calling to get_nid_for_pfn(). section size / page_size = 128M/4k = 32k > but it is not happy. See all the chatter from systemd in the attached dmesg. because of you have "debug ignore_loglevel" ? > > x86 doesn't allow me to set CONFIG_HOLES_IN_ZONE ... but now I'm > worried about all the other places use pfn_valid_within() > > Still trying to get an answer from the BIOS folks on whether these > holes are normal when setting up mirrored areas of memory. The problem only happens when memory block size is 512M and section size is 128M. when you have them both at 128M, the system works. so current kernel should only has problem with hole size > 128M to leave some section not present. Thanks Yinghai -- 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/