From: Eduardo Habkost <ehabkost@redhat.com>
To: Haozhong Zhang <haozhong.zhang@intel.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com,
Stefan Hajnoczi <stefanha@gmail.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Xiao Guangrong <guangrong.xiao@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for-2.12 v4 0/3] nvdimm: fixes for (non-)dax backends
Date: Tue, 9 Jan 2018 18:10:05 -0200 [thread overview]
Message-ID: <20180109201005.GE18022@localhost.localdomain> (raw)
In-Reply-To: <20171211072806.2812-1-haozhong.zhang@intel.com>
Queued on machine-next. Thanks, and sorry for the long delay.
On Mon, Dec 11, 2017 at 03:28:03PM +0800, Haozhong Zhang wrote:
> Previous versions can be found at
> v3: https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg04785.html
> v2: https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg01203.html
> v1: https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg05919.html
>
> Changes in v4:
> * Document new memory-backend-file option 'align' in qemu-options.hx. (Eduardo Habkost)
> * Add endian conversion when setting the unarmed flag in NFIT. (Stefan Hajnoczi)
>
> Changes in v3:
> * Add an option 'align' to 'memory-backend-file' to address the
> failure when mmap device dax (patch 1).
> * Remove device dax check, which needs to access sysfs and may not
> work with SELinux.
> * Add a boolean option 'unarmed' to '-device nvdimm', which allows
> users to control the unarmed flag in guest ACPI NFIT. I don't make
> it as OnOffAuto, because of the remove of device dax check.
> * Document new options added by this patch series.
>
> Haozhong Zhang (3):
> hostmem-file: add "align" option
> nvdimm: add a macro for property "label-size"
> nvdimm: add 'unarmed' option
>
> backends/hostmem-file.c | 41 ++++++++++++++++++++++++++++++++++++++++-
> docs/nvdimm.txt | 31 +++++++++++++++++++++++++++++++
> exec.c | 8 +++++++-
> hw/acpi/nvdimm.c | 7 +++++++
> hw/mem/nvdimm.c | 28 +++++++++++++++++++++++++++-
> include/exec/memory.h | 3 +++
> include/hw/mem/nvdimm.h | 12 ++++++++++++
> memory.c | 2 ++
> numa.c | 2 +-
> qemu-options.hx | 9 ++++++++-
> 10 files changed, 138 insertions(+), 5 deletions(-)
>
> --
> 2.14.1
>
>
--
Eduardo
prev parent reply other threads:[~2018-01-09 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 7:28 [Qemu-devel] [PATCH for-2.12 v4 0/3] nvdimm: fixes for (non-)dax backends Haozhong Zhang
2017-12-11 7:28 ` [Qemu-devel] [PATCH v4 1/3] hostmem-file: add "align" option Haozhong Zhang
2017-12-13 11:14 ` Stefan Hajnoczi
2017-12-11 7:28 ` [Qemu-devel] [PATCH v4 2/3] nvdimm: add a macro for property "label-size" Haozhong Zhang
2017-12-11 7:28 ` [Qemu-devel] [PATCH v4 3/3] nvdimm: add 'unarmed' option Haozhong Zhang
2017-12-13 11:15 ` Stefan Hajnoczi
2017-12-13 11:16 ` [Qemu-devel] [PATCH for-2.12 v4 0/3] nvdimm: fixes for (non-)dax backends Stefan Hajnoczi
2017-12-20 17:28 ` Michael S. Tsirkin
2018-01-09 20:10 ` Eduardo Habkost [this message]
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=20180109201005.GE18022@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=guangrong.xiao@gmail.com \
--cc=haozhong.zhang@intel.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 \
--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).