From: Michal Suchanek <msuchanek@suse.de>
To: nvdimm@lists.linux.dev
Cc: Michal Suchanek <msuchanek@suse.de>
Subject: [PATCH] daxctl: Fix kernel option typo in "Soft Reservation" theory of operation
Date: Sun, 10 Apr 2022 14:32:04 +0200 [thread overview]
Message-ID: <20220410123205.6045-2-msuchanek@suse.de> (raw)
In-Reply-To: <20220410123205.6045-1-msuchanek@suse.de>
Fixes: 8f4e42c ("daxctl: Add "Soft Reservation" theory of operation")
Signed-off-by: Michal Suchanek <msuchanek@suse.de>
---
Documentation/daxctl/daxctl-reconfigure-device.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/daxctl/daxctl-reconfigure-device.txt b/Documentation/daxctl/daxctl-reconfigure-device.txt
index 385c0c5..09691d2 100644
--- a/Documentation/daxctl/daxctl-reconfigure-device.txt
+++ b/Documentation/daxctl/daxctl-reconfigure-device.txt
@@ -91,8 +91,8 @@ details.
Outside of the NUMA performance details linked above the other method to
detect the presence of "Soft Reserved" memory is to dump /proc/iomem and
look for "Soft Reserved" ranges. If the kernel was not built with
-CONFIG_EFI_SOFTRESERVE, predates the introduction of
-CONFIG_EFI_SOFTRESERVE (v5.5), or was booted with the efi=nosoftreserve
+CONFIG_EFI_SOFT_RESERVE, predates the introduction of
+CONFIG_EFI_SOFT_RESERVE (v5.5), or was booted with the efi=nosoftreserve
command line then device-dax will not attach and the expectation is that
the memory shows up as a memory-only NUMA node. Otherwise the memory
shows up as a device-dax instance and DAXCTL(1) can be used to
--
2.35.1
next prev parent reply other threads:[~2022-04-10 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 12:32 [PATCH] namespace-action: Drop more zero namespace checks Michal Suchanek
2022-04-10 12:32 ` Michal Suchanek [this message]
2022-04-10 12:32 ` [PATCH] meson: make modprobedatadir an option Michal Suchanek
-- strict thread matches above, loose matches on Subject: below --
2022-03-10 13:30 [PATCH] daxctl: Fix kernel option typo in "Soft Reservation" theory of operation Michal Suchanek
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=20220410123205.6045-2-msuchanek@suse.de \
--to=msuchanek@suse.de \
--cc=nvdimm@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.