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 1D1E7C3DA7F for ; Wed, 31 Jul 2024 14:15:15 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 7B2CC6B0085; Wed, 31 Jul 2024 10:15:15 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 73BA16B0088; Wed, 31 Jul 2024 10:15:15 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 5B5B06B0089; Wed, 31 Jul 2024 10:15:15 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 3D34B6B0085 for ; Wed, 31 Jul 2024 10:15:15 -0400 (EDT) Received: from smtpin30.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 94FD2A4C8F for ; Wed, 31 Jul 2024 14:15:14 +0000 (UTC) X-FDA: 82400244948.30.D67FE56 Received: from mail-qv1-f45.google.com (mail-qv1-f45.google.com [209.85.219.45]) by imf01.hostedemail.com (Postfix) with ESMTP id B7DF740022 for ; Wed, 31 Jul 2024 14:15:12 +0000 (UTC) Authentication-Results: imf01.hostedemail.com; dkim=pass header.d=gourry.net header.s=google header.b=BNMXAC2l; dmarc=none; spf=pass (imf01.hostedemail.com: domain of gourry@gourry.net designates 209.85.219.45 as permitted sender) smtp.mailfrom=gourry@gourry.net ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1722435271; a=rsa-sha256; cv=none; b=ey0WhfOl7Tya/23yi3d3XxSDYkpzQZlWL8rFC45Q8RNucPjyVrpasDK+V4t8MvuzzVKzvp aO8OiB0l7hisZW00EF8zFo7J47RvgR4Yl2kDdQaoR2dk3bb7UsyqWpZF+GKwJB9fYQRkJT JPIavaG1BMUzHGqmIsCUW0uJHfskkx0= ARC-Authentication-Results: i=1; imf01.hostedemail.com; dkim=pass header.d=gourry.net header.s=google header.b=BNMXAC2l; dmarc=none; spf=pass (imf01.hostedemail.com: domain of gourry@gourry.net designates 209.85.219.45 as permitted sender) smtp.mailfrom=gourry@gourry.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1722435271; 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=nZoGyjJaWEwHv/KfoCIN2q0gBEBBi+yquexZmDv5wAQ=; b=NLUuh6PohB1/PgmNMRy07sUCRY0kJUnF+/hGsp48rrgXGXeUWEpHJr8VawMYuke+vCnS2R uLPRuqqjN/Ww6PjitkLCGyTecSPGN/opRLV1Qhe2X71lpT9coVmBfA+6rEWzXXaOnddC57 EBx7QxOf2XUFFjcDM+P5fC8yqAPAnUI= Received: by mail-qv1-f45.google.com with SMTP id 6a1803df08f44-6b78c980981so30486586d6.2 for ; Wed, 31 Jul 2024 07:15:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gourry.net; s=google; t=1722435312; x=1723040112; darn=kvack.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=nZoGyjJaWEwHv/KfoCIN2q0gBEBBi+yquexZmDv5wAQ=; b=BNMXAC2lDtL6GtxT0g+bdmV2aUWMwOtIvSNGu7El/4vfI3jz0vMYRvROtWcQboY6So m0ic7HtC8rfpx97Ans4zz+p46Z+gheM6RYgxcR5LHe7PsQc6kFi1FqACYHZfYb7aq2aL 9RVBBBkprB30uK6z2OoNNbngb3HP19N3drq/ihzelPJFHx96FZA6bPAuEicfsJQPiTVt JqPPgPPa8qODlXtxalXxAWTsHotx+OlR70paNx9T9N75Lksl7VT4GXUTSrjFBAvdOhTJ NWi3sct5nm/w1oQFLCF81D1dNnTKSV3s3BOgalqwn+d4JbDmNQYKTo8wsy5MMKduSStl 3WPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722435312; x=1723040112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=nZoGyjJaWEwHv/KfoCIN2q0gBEBBi+yquexZmDv5wAQ=; b=LBnyjx2KVv++ANEDWLK+FCaVttWzP2pg+XIEOInIl8if+2INtBUDFFXv2vXGcYMGzw F3q3QYil3Sl1D5vQyOwQZhvgDTSvhpxMOqdYpIkUKizofizjNDSwVUjKHijuyvpGMbkR bM61hBy8FDwAQDgfb9DelrAoFGdh+Fjx9kRLHLnPjzK68kaboKYs4d7hI5wexj/Vp21A 8OiSp8Kb7+AzdsaXZX1/o+HupNQXr7HliGTczHemP+1ObEXsijvLwUyMhGwcJGASKB7r QaGKbi2ZXNagS7zBbumP3oN1OGywu1O7QpPMZuhBPfetS8+0B6RW0kVisHGyrcUpiL4d JCnw== X-Gm-Message-State: AOJu0YwB6VNb68+f8PFRtdeHCbkfCleXb+IAHzMKp0lh88jv0EaZ/aJ3 ayB3EzoyROIJlQ4NAJamrVaGLzNuv4K+ueoX1Jv3PXflccrCD5f4kaqG5doPED8= X-Google-Smtp-Source: AGHT+IFNREONZgm7zLR0cLrVINRHZAuZJz57NqpdO1aQ2JjmTspGlBRsHUwaFMQ8H7vcv4eyfHiRWw== X-Received: by 2002:ad4:5c6f:0:b0:6b5:d9ef:d56d with SMTP id 6a1803df08f44-6bb559c3461mr182732716d6.21.1722435311609; Wed, 31 Jul 2024 07:15:11 -0700 (PDT) Received: from PC2K9PVX.TheFacebook.com (pool-173-79-56-208.washdc.fios.verizon.net. [173.79.56.208]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6bb3fa950a3sm74461836d6.90.2024.07.31.07.15.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 31 Jul 2024 07:15:11 -0700 (PDT) Date: Tue, 30 Jul 2024 16:26:06 -0400 From: Gregory Price To: "Huang, Ying" Cc: linux-mm@kvack.org, akpm@linux-foundation.org, dave.jiang@intel.com, Jonathan.Cameron@huawei.com, horenchuang@bytedance.com, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, dan.j.williams@intel.com, lenb@kernel.org, "Aneesh Kumar K.V" Subject: Re: [PATCH] acpi/hmat,mm/memtier: always register hmat adist calculation callback Message-ID: References: <20240726215548.10653-1-gourry@gourry.net> <87ttg91046.fsf@yhuang6-desk2.ccr.corp.intel.com> <877cd3u1go.fsf@yhuang6-desk2.ccr.corp.intel.com> <87cymupd7r.fsf@yhuang6-desk2.ccr.corp.intel.com> <878qxiowmy.fsf@yhuang6-desk2.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <878qxiowmy.fsf@yhuang6-desk2.ccr.corp.intel.com> X-Rspamd-Queue-Id: B7DF740022 X-Rspam-User: X-Rspamd-Server: rspam05 X-Stat-Signature: n6tc9dqqhpaephzws898rqk9zmdozwxn X-HE-Tag: 1722435312-372017 X-HE-Meta: U2FsdGVkX1/XlWfby5UduPcD7OYXun7Ag29D4QMUX6LxR5ITxeuY755SFMkBZakHEE2tSLIVNIXFO5NjXOAdABbCBpKoLeMO8JfbvVcaoT/g90OWpO2z9NcLrpJb1gRNAt7BzZNgrH66S5yYeH8s1ChJY1M51vZy8U+267wO2n47HLU8TRb//DGeyy9qQcKwKXnqFFxtD066tqrZVoPH7Nq3+n59sRr9/ym0cD4FRyjz0nf2YQP3QN3KfocRljSJ5+TjbTOkmRxQl98ggh0jtJzdVmZL0go/GmDUTGPW/bpV6yfRH86C80Dv5JWEb3fredSBbdWqn3Yi8BHEFrh020rRtr5TRa+C7cquGb7c9Ibri9JiYG88Iqe5Q6Rpb9kZN8meRVfDfwtJwh0le9Ycd7y4YwdNyiKXFa8y1pre/svL3/0s8L0v3IlPw3SwWA+e+PArgvBCu/CiZmH5Occbgpnu23fr6SbhhQTpZhcz8IpEHl0fY9ljS6ugoL6308pIxSNUqKbYzlRGlLX30TmcRzp+PDY8fkvMyTfGD4zXGVhm32V81VzrxaYJIGF9c1LjAoJ721wBhHoJFJOT1QDdcAyOM1mB/mLXPduSeGfmDJaq3F/MtIC9JkjeEp5NkrDls/vLlFRTRgNbpL6lsysWyjHx8dlflWKArgbrL/xeYtj8kzo40QwehhIRdRaiJ7ebiHJ2zRGbh/0SgxV9aQePZAy/KrwIaIPOTUvSbx6IPGC6N15nP44KK+uXEOHfm1dfvTT1eTSMCSKiDqM88UK92hKp2T3Lfos7GNi+I3PeH7xltwkspKn8HoHkxg+ZEEAg2w6h4+XHBdNJ3S38svtxVrcAtH6Qhl981RFo9nY6N34HYQJGyPfuPMWX5WtSlJDBU/3Ub8T2LciIBIwFHHoZSR0PCJYcMyAnTUW5DR5dYRGb8akRSdjt+kqwi5uJq8xkAsCwJr9P//ZcEynUENt K/ZAGYCB /Z6/u3W5IiOAT8Le6ds5BDyNVAKQncHr8svqaoHpwn5onufzygvkvPZII//vSFP8SkdOstcbTwHOQcWgQhq606Nlhhfu2rRM5xTpc9jYcGK2ZTWvcmXBB2e+4vUZRFIOgpMaNPdJJ5lr2YvyZae82ev5lPhzoVK4lN6uEDhaNajZU4UF42eGkYjahyB0WKHeupfIPDF5AUj/u7CsnIz0Lbi7czypF6OhwMv5JSjJBSPAwI8TOkkhQKWeWO8LKjWugLuq8CsDvsTNfYDBrD8/3HSBd6Y1vzOMZxXLJ19XkTSjPPbYEYwUkxOglfcgSI4A7D8am 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: On Wed, Jul 31, 2024 at 03:20:37PM +0800, Huang, Ying wrote: > Gregory Price writes: > > > > In this case, the system is configured explicitly so that kmem does not > > manage it. In fact, some systems still cannot be managed with > > EFI_MEMORY_SP due to hpa!=spa issues that the driver cannot manage. > > Sorry, I don't understand. IIUC, kmem.c can manage almost any memory > range via drivers/dax/hmem. Please check > > drivers/dax/hmem/device.c > drivers/dax/hmem/hmem.c > > Could you elaborate why kmem.c doesn't work for some memory range? > Sorry I misunderstood, I thought you meant the cxl+kmem/hmem subsystem interaction and handing configuration of the CXL device over to the kernel. The boot parameter is not likely to be a solution for us but I will look at it. > > But I think a feature that worked in 5.x should work in 6.x, and right > > now the change in node placement breaks hardware that worked with 5.x > > which happened to have broken or missing HMAT.