From: Gregory Price <gourry@gourry.net>
To: David Hildenbrand <david@redhat.com>
Cc: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
dan.j.williams@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com
Subject: Re: [PATCH] DAX: warn when kmem regions are truncated for memory block alignment.
Date: Tue, 1 Apr 2025 10:44:17 -0400 [thread overview]
Message-ID: <Z-v7waimV3OZq_1H@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <88bce46e-a703-4935-b10e-638e33ea91b3@redhat.com>
On Tue, Apr 01, 2025 at 11:47:32AM +0200, David Hildenbrand wrote:
>
> Can't that be done a bit simpler?
Yes, this is better, lets do this. Thank you!
>
> diff --git a/drivers/dax/kmem.c b/drivers/dax/kmem.c
> index e97d47f42ee2e..23a68ff809cdf 100644
> --- a/drivers/dax/kmem.c
> +++ b/drivers/dax/kmem.c
> @@ -67,8 +67,8 @@ static void kmem_put_memory_types(void)
> static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
> {
> + unsigned long total_len = 0, orig_len = 0;
> struct device *dev = &dev_dax->dev;
> - unsigned long total_len = 0;
> struct dax_kmem_data *data;
> struct memory_dev_type *mtype;
> int i, rc, mapped = 0;
> @@ -97,6 +97,7 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
> for (i = 0; i < dev_dax->nr_range; i++) {
> struct range range;
> + orig_len += range_len(&dev_dax->ranges[i].range);
> rc = dax_kmem_range(dev_dax, i, &range);
> if (rc) {
> dev_info(dev, "mapping%d: %#llx-%#llx too small after alignment\n",
> @@ -109,6 +110,9 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
> if (!total_len) {
> dev_warn(dev, "rejecting DAX region without any memory after alignment\n");
> return -EINVAL;
> + } else if (total_len != orig_len) {
> + dev_warn(dev, "DAX region truncated by %lu bytes due to alignment\n",
> + orig_len - total_len);
> }
> init_node_memory_type(numa_node, mtype);
>
>
> --
> Cheers,
>
> David / dhildenb
>
next prev parent reply other threads:[~2025-04-01 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 18:07 Gregory Price
2025-03-31 18:27 ` Gregory Price
2025-04-01 9:33 ` David Hildenbrand
2025-04-01 14:43 ` Gregory Price
2025-04-01 14:50 ` David Hildenbrand
2025-04-01 15:16 ` Gregory Price
2025-04-01 15:19 ` David Hildenbrand
2025-04-01 15:26 ` Gregory Price
2025-04-01 15:29 ` David Hildenbrand
2025-04-01 9:47 ` David Hildenbrand
2025-04-01 14:44 ` Gregory Price [this message]
2025-04-01 17:47 ` Dan Williams
2025-04-01 18:27 ` Gregory Price
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=Z-v7waimV3OZq_1H@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@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
all inboxes | Powered by JetHome®