From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 687BCEE0209 for ; Wed, 11 Sep 2024 05:22:18 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id EF9A98D00F9; Wed, 11 Sep 2024 01:22:17 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E83388D0056; Wed, 11 Sep 2024 01:22:17 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D23C38D00F9; Wed, 11 Sep 2024 01:22:17 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id B3B8F8D0056 for ; Wed, 11 Sep 2024 01:22:17 -0400 (EDT) Received: from smtpin12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 32C721C5340 for ; Wed, 11 Sep 2024 05:22:17 +0000 (UTC) X-FDA: 82551311514.12.30071F2 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.19]) by imf29.hostedemail.com (Postfix) with ESMTP id F070A12000E for ; Wed, 11 Sep 2024 05:22:14 +0000 (UTC) Authentication-Results: imf29.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=Llh4++fl; spf=pass (imf29.hostedemail.com: domain of ying.huang@intel.com designates 198.175.65.19 as permitted sender) smtp.mailfrom=ying.huang@intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1726031997; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=KsoaV274/YNCpjm22HdB2VYB9Sz7vDWyAS4sNHhHw6U=; b=7LZ5t3HQJ59Aks92hkBCOkOEPbHy6QUL2HDVS9FW9zYY+XgoYYAz76AgQKtoFifG5sgHGW vWPePyjdsdwiF8ErksDxKgIna+VETVeUbrxeYLZsJet6s/xzpDGqH3f9h6LoBu1Fwld6i1 JDPQ2rXGU+jRgF4BS+vcnMFbKoAUSwM= ARC-Authentication-Results: i=1; imf29.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=Llh4++fl; spf=pass (imf29.hostedemail.com: domain of ying.huang@intel.com designates 198.175.65.19 as permitted sender) smtp.mailfrom=ying.huang@intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1726031997; a=rsa-sha256; cv=none; b=tjrKpU1/PuS8TWWwGY4drUt7wuCDq2KyA0b4cGTKfPZeqM2xHXfCqN5GeZvVEjtBcnAqfi syTWqrEktdK0JDijW7bv+6hfJh45utAUT4zNYE5Y86IVO+D3+E1YlimLp1i3G7MYSO99cr ouKh8YsiTUChIanNX0uWXXGf1AROBsI= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1726032136; x=1757568136; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=fOQJKeXoo0J5Jf2UkW332F7tvEqUUop5G1yJ4OcGFQQ=; b=Llh4++flWh5z61YDwtvYO8l2pQqX6jPaIb4VhYaWnm3FOm0zvNyiXDod ZOLDrmYhKhEgx/ICTvy8ASqVbgl0dugx4Egmrqi803FKF2zWTmRBkG3xd rPu5B9CHqW6H90jBl963uuFYkO7V8/Yl2eIKBg9eo9dHTKozUlZYuP9TC Xi6rTcFGo6/hUUDhWKhkCldFv1KKykZEOtIzZahYMXskpL3iYNEtKmiH0 SLL/WOWSXCVj/YREOxe6ij8ikFdnZWzDgJwVzmN/BB3BZBtXRcdzisR1H mcj2hKMWrT8M2LpAJ9cxTheQ0mQGHuQBMzPhp17NpLFGtCW5XUCo09hxO w==; X-CSE-ConnectionGUID: ZF2MQ//kS1mxl3qkqkVXfA== X-CSE-MsgGUID: WqTUtu6yToeEWeAJhwAb4Q== X-IronPort-AV: E=McAfee;i="6700,10204,11191"; a="24679626" X-IronPort-AV: E=Sophos;i="6.10,219,1719903600"; d="scan'208";a="24679626" Received: from orviesa005.jf.intel.com ([10.64.159.145]) by orvoesa111.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Sep 2024 22:22:14 -0700 X-CSE-ConnectionGUID: tRWuOCHCQJSSLX1p0+vMwQ== X-CSE-MsgGUID: uF8FTi2ESCeBdITbc2P7sg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.10,219,1719903600"; d="scan'208";a="72051162" Received: from yhuang6-desk2.sh.intel.com (HELO yhuang6-desk2.ccr.corp.intel.com) ([10.238.208.55]) by orviesa005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Sep 2024 22:22:12 -0700 From: "Huang, Ying" To: Andrew Morton Cc: Stephen Rothwell , kernel test robot , oe-kbuild-all@lists.linux.dev, Linux Memory Management List , Thomas Gleixner Subject: Re: [linux-next:master 10352/10516] include/linux/mm.h:101:35: error: 'MAX_PHYSMEM_BITS' undeclared In-Reply-To: <20240910204534.94fe988e2865c0e187b7653b@linux-foundation.org> (Andrew Morton's message of "Tue, 10 Sep 2024 20:45:34 -0700") References: <202409100913.RxkfrKU6-lkp@intel.com> <20240909204555.ab57c729531c83a0685cfa8e@linux-foundation.org> <87wmjkyshl.fsf@yhuang6-desk2.ccr.corp.intel.com> <20240910104056.343d7154134fb7fc6942075a@linux-foundation.org> <87ttenvw0i.fsf@yhuang6-desk2.ccr.corp.intel.com> <20240910204534.94fe988e2865c0e187b7653b@linux-foundation.org> Date: Wed, 11 Sep 2024 13:18:39 +0800 Message-ID: <87ldzywyxc.fsf@yhuang6-desk2.ccr.corp.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: F070A12000E X-Stat-Signature: 7o1dczzhuf6zpqfhme88974jj59mjb9e X-Rspam-User: X-HE-Tag: 1726032134-260445 X-HE-Meta: U2FsdGVkX1/c4meB0H5gDmvbSmPzbAkHCFlFsnuG3qkWmvk5t7JWSzuYF8ORXo9i4rSkgQ9jWMw7VFouuVguufc5rHqwu0ehxWbeIuuQq8+Eol6t6djjVxDee84RcdfPUD4dGo5ANdqqCLMv4xIPNJ5etoTccvBA3NVbmS8RK57J6QraAYYrI6I210oYAWGSJH8OnF1/Jbc2uzrRofjsX/VF6PpeVDFCQ4w+92j1xKuPE4Nleir0R3tkaRFL5P4TgKH8Gi8e3Yf7bJ7+drWmbMFH0wZnimTS4Z7d2t8l4O5xjCXiP5R/O28yqazF54RWVcmH3lZzBNFN3j6srfn4HVeqLmJmQjn6LF+NAcehwpaF1H94MMBGimb4vUldXyZGJtsR7lkEpvugvYEXyZz1Bev4tmLkyKoHG4KY4X3ToQBUJeGqY7KUmJv+D+HSmEU10cwq54V8LfeiOPIUkt6Oq7B7RNZWCL7OzKJM33bQ0Ni6EtxMyWpCpj/6ZfHBgqHPbH87ECvzZUfw9kzbD2kLDLSfgj5uoh6jleG5uMek/aT4jTjSutLInUgznQ55q98hLJqDWE6TiA+856+zU5B4Oee//2QywIpV285hQeZ+kia/CC/FfB59Y0+YzaAd/VZ/jMwo1S4xsjZ2lHAsXqtdR6H5D+LdGN2El2VXhRnakRoZxzaAogUyzy0kyWv0AHwUk9Bdj3OHR2O2ZIgU0mspve9dFBAYT2xJxdNueUIUUIFbHPHTqNQ7sAIJVMRL5WyIdd1/aTHzxMcy8rp3iHgsz4fbWasXcPXOeo+CFP9ZwF9c9OHrF+HU/Zl8cRhkwDHxEfC9Ilt/159v6eObiEGl2vfeDdC231InpEE/1dbOZfv+Eygobh6H0L4HJghhwJoZDJeWjL4fY01WihT1cx9EgDMvSG+UW/VzXIpjj73hkoM+F1+cu4wZbCHjrvM+HrO9N4dmbNP6dqA+tf2CDWw 0Wear+qg xlHmn1zfR6umZqMVWZlWBTWqqGMm07vAkJNKFzCsLhQfAs53miVOtzP0e6tOBYINHXQp3g/Xm+6yalr5Lda6jalbU/o1UcA2qWhVs01qzJ8mm9klqv+g/zEc5y/kUCG65CKs+pK/+Bl8O2yKCu6mO1ZO6JOG/hBjE1o9IAwpHOCi70dlSjRgY4QTzGE8ikC4Q196QMjBpLca70WXFj9ZTw/kv8Xp5XhbRqVoAdOurWAvD/CxPZym7/EA6pDlOaKiAqeZTMqwcEj5FLGmepVHE3kqCW4gu8yPtjcpcHgOO17Vxur020FrYypXkHICAGnQNdoYaZdyWENsywAaOcxvks1yoy+H0s1V6Mf/YAQsjQauq7TZxZhiq0eFp9g== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: Andrew Morton writes: > On Wed, 11 Sep 2024 09:06:53 +0800 "Huang, Ying" wrote: > >> > linux-next?) requires the presence of ea72ce5da228 ("x86/kaslr: Expose >> > and use the end of the physical memory address space"), which is not >> > present in mm.git. Yet mm.git exhibits the build failure. >> >> The original test report is against linux-next tree instead mm tree. >> >> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git >> >> The first bad commit (bisection result) is: >> >> 5f445800cbdfc4b4185d496a43dfd78df63d2265 [10352/10516] Merge branch 'mm-everything' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm >> >> That is, mm tree is merged in linux-next, and commit ea72ce5da228 >> ("x86/kaslr: Expose and use the end of the physical memory address >> space") is merged in linux-next too. In fact, there's a merge conflict >> for MAX_PHYSMEM_BITS related code. Maybe this can be part of merge >> conflict resolving patch? >> >> Hi, Stephen, >> >> Can you use the patch above as part of merged conflict resolving patch >> for patch >> >> e2941fe697c8 ("resource, kunit: add test case for region_intersects()") >> >> You have resolved it in >> >> https://lore.kernel.org/lkml/20240909100043.60668995@canb.auug.org.au/ > > mm-unstable is presently broken, and fixing up linux-next won't change that. > > I'd prefer to fix mm-stable and then provide Linus directions for merging that > with the x86 tree. The real bug fix patch is [1/3]: resource: Fix region_intersects() vs add_memory_driver_managed() The merge conflict is for the new kunit test case, which isn't urgent. So, another option is to merge the bug fix ([1/3]) through mm now and backport it to stable kernels. Then I can resend the kunit test case after v6.12-rc1 is released. -- Best Regards, Huang, Ying