From: Gregory Price <gourry@gourry.net>
To: "Huang, Ying" <ying.huang@intel.com>
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" <aneesh.kumar@linux.ibm.com>
Subject: Re: [PATCH] acpi/hmat,mm/memtier: always register hmat adist calculation callback
Date: Tue, 30 Jul 2024 16:26:06 -0400 [thread overview]
Message-ID: <ZqlMXuBxi2oShb-u@PC2K9PVX.TheFacebook.com> (raw)
In-Reply-To: <878qxiowmy.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Wed, Jul 31, 2024 at 03:20:37PM +0800, Huang, Ying wrote:
> Gregory Price <gourry@gourry.net> 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.
next prev parent reply other threads:[~2024-07-31 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 21:55 Gregory Price
2024-07-29 1:02 ` Huang, Ying
2024-07-29 14:22 ` Gregory Price
2024-07-30 1:12 ` Huang, Ying
2024-07-30 3:18 ` Gregory Price
2024-07-31 1:22 ` Huang, Ying
2024-07-30 19:58 ` Gregory Price
2024-07-31 7:20 ` Huang, Ying
2024-07-30 20:26 ` Gregory Price [this message]
2024-08-27 14:33 ` Gregory Price
2024-07-30 5:19 ` Gregory Price
2024-07-30 6:12 ` Gregory Price
2024-07-31 1:10 ` Huang, Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZqlMXuBxi2oShb-u@PC2K9PVX.TheFacebook.com \
--to=gourry@gourry.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=horenchuang@bytedance.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox