From: Joao Martins <joao.m.martins@oracle.com>
To: Jingqi Liu <jingqi.liu@intel.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v2 2/3] docs/nvdimm: add description of alignment requirement of device dax
Date: Tue, 28 Apr 2020 17:22:59 +0100 [thread overview]
Message-ID: <b520218c-a8f5-101e-1e3e-ad212fe35cdd@oracle.com> (raw)
In-Reply-To: <20200415033538.43329-3-jingqi.liu@intel.com>
On 4/15/20 4:35 AM, Jingqi Liu wrote:
> For device dax (e.g., /dev/dax0.0), the NUM of 'align=NUM' option
> needs to match the alignment requirement of the device dax.
> It must be larger than or equal to the 'align' of device dax.
>
> Signed-off-by: Jingqi Liu <jingqi.liu@intel.com>
> ---
> docs/nvdimm.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/docs/nvdimm.txt b/docs/nvdimm.txt
> index 362e99109e..3c7b6dab5f 100644
> --- a/docs/nvdimm.txt
> +++ b/docs/nvdimm.txt
> @@ -132,6 +132,15 @@ address to the page size (getpagesize(2)) by default. However, some
> types of backends may require an alignment different than the page
> size. In that case, QEMU v2.12.0 and later provide 'align' option to
> memory-backend-file to allow users to specify the proper alignment.
> +For device dax (e.g., /dev/dax0.0), this alignment needs to match the
> +alignment requirement of the device dax. The NUM of 'align=NUM' option
> +must be larger than or equal to the 'align' of device dax.
> +We can use the following command to show the 'align' of device dax.
> +
> + ndctl list -X
> +
> +In order to get the proper 'align' of device dax, you need to install
> +the library 'libdaxctl'.
>
> For example, device dax require the 2 MB alignment, so we can use
> following QEMU command line options to use it (/dev/dax0.0) as the
>
Given that this series introduces support for libdaxctl, perhaps suggesting in
the docs how you can also query the @align with daxctl tool? e.g.
"We can one of the following commands to show the 'align' of device dax:
ndctl list -X
daxctl list -R"
The unlikely reason being that users may only install daxctl-{,libs,devel} and
not ndctl-*. It also covers other users like ACPI HMAT/hmem which are not
instrumented with ndctl.
With that:
Reviewed-by: Joao Martins <joao.m.martins@oracle.com>
Joao
next prev parent reply other threads:[~2020-04-28 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 3:35 [PATCH v2 0/3] fetch the alignment of device dax Jingqi Liu
2020-04-15 3:35 ` [PATCH v2 1/3] exec: fetch the alignment of Linux devdax pmem character device nodes Jingqi Liu
2020-04-28 16:22 ` Joao Martins
2020-04-15 3:35 ` [PATCH v2 2/3] docs/nvdimm: add description of alignment requirement of device dax Jingqi Liu
2020-04-28 16:22 ` Joao Martins [this message]
2020-04-29 6:11 ` Liu, Jingqi
2020-04-15 3:35 ` [PATCH v2 3/3] configure: add libdaxctl support Jingqi Liu
2020-04-28 16:23 ` Joao Martins
2020-04-29 7:03 ` Liu, Jingqi
2020-04-19 13:48 ` [PATCH v2 0/3] fetch the alignment of device dax Liu, Jingqi
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=b520218c-a8f5-101e-1e3e-ad212fe35cdd@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=jingqi.liu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=xiaoguangrong.eric@gmail.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;
as well as URLs for NNTP newsgroup(s).