From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, Xiao Guangrong <guangrong.xiao@gmail.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Richard Henderson <rth@twiddle.net>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/3] hostmem-file: add "align" option
Date: Wed, 29 Nov 2017 08:05:19 -0200 [thread overview]
Message-ID: <20171129100519.GW3037@localhost.localdomain> (raw)
In-Reply-To: <20171129003329.g562dwn233rftyty@hz-desktop>
On Wed, Nov 29, 2017 at 08:33:29AM +0800, Haozhong Zhang wrote:
> On 11/27/17 23:07 -0200, Eduardo Habkost wrote:
> > On Mon, Nov 27, 2017 at 12:35:15PM +0800, Haozhong Zhang wrote:
> > > When mmap(2) the backend files, QEMU uses the host page size
> > > (getpagesize(2)) by default as the alignment of mapping address.
> > > However, some backends may require alignments different than the page
> > > size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
> > > kernel 4.13 to an address, which is 4K-aligned but not 2M-aligned,
> > > fails with a kernel message like
> > >
> > > [617494.969768] dax dax0.0: qemu-system-x86: dax_mmap: fail, unaligned vma (0x7fa37c579000 - 0x7fa43c579000, 0x1fffff)
> > >
> > > Because there is no common approach to get such alignment requirement,
> > > we add the 'align' option to 'memory-backend-file', so that users or
> > > management utils, which have enough knowledge about the backend, can
> > > specify a proper alignment via this option.
> > >
> > > Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> >
> > The new option needs to be documented on qemu-options.hx.
>
> will add in the next version.
Note that there are patches on on machine-next that change the memory backend
documentation.
See:
git://github.com/ehabkost/qemu.git machine-next
https://github.com/ehabkost/qemu/commit/869f7f61c557a46b46e41b5e38a61551d45b6d0d
But the conflicts should be trivial to solve if you document the new option in
a separate paragraph.
--
Eduardo
next prev parent reply other threads:[~2017-11-29 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 4:35 [Qemu-devel] [PATCH-for-2.12 v3 0/3] nvdimm: fixes for (non-)dax backends Haozhong Zhang
2017-11-27 4:35 ` [Qemu-devel] [PATCH v3 1/3] hostmem-file: add "align" option Haozhong Zhang
2017-11-28 1:07 ` Eduardo Habkost
2017-11-29 0:33 ` Haozhong Zhang
2017-11-29 10:05 ` Eduardo Habkost [this message]
2017-11-29 0:31 ` Haozhong Zhang
2017-11-29 0:38 ` Haozhong Zhang
2017-11-27 4:35 ` [Qemu-devel] [PATCH v3 2/3] nvdimm: add a macro for property "label-size" Haozhong Zhang
2017-11-27 4:35 ` [Qemu-devel] [PATCH v3 3/3] nvdimm: add 'unarmed' option Haozhong Zhang
2017-12-01 10:44 ` Stefan Hajnoczi
2017-12-04 5:47 ` Haozhong Zhang
2017-11-28 18:44 ` [Qemu-devel] [PATCH-for-2.12 v3 0/3] nvdimm: fixes for (non-)dax backends Michael S. Tsirkin
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=20171129100519.GW3037@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=guangrong.xiao@gmail.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@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).