xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Haozhong Zhang <haozhong.zhang@intel.com>
To: qemu-devel@nongnu.org, xen-devel@lists.xen.org
Cc: Haozhong Zhang <haozhong.zhang@intel.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Anthony Perard <anthony.perard@citrix.com>,
	Konrad Rzeszutek Wilk <konrad@darnok.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Eric Blake <eblake@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: [RFC QEMU PATCH v2 00/10] Implement vNVDIMM for Xen HVM guest
Date: Mon, 20 Mar 2017 08:12:39 +0800	[thread overview]
Message-ID: <20170320001249.25521-1-haozhong.zhang@intel.com> (raw)

This is the QEMU patch of v2 RFC patch series to enable vNVDIMM
support for Xen HVM guest. v1 can be found at
https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg01678.html.

The corresponding Xen patch series is sent in another thread
"[RFC XEN PATCH v2 00/15] Add vNVDIMM support to HVM domains".

All patch series can be found at
  Xen:  https://github.com/hzzhan9/xen.git nvdimm-rfc-v2
  Qemu: https://github.com/hzzhan9/qemu.git xen-nvdimm-rfc-v2


Patch 1 is to avoid dereferencing the NULL pointer to non-existing
label data, as the Xen side support for labels is not implemented yet.

Patch 2 - 7 build and cooy NFIT from QEMU to Xen guest, when QEMU is
used as the Xen device model.

Patch 8 & 9 add a memory backend dedicated for Xen usage and a hotplug
memory region for Xen guest, in order to make the existing nvdimm
device plugging path work on Xen.

Patch 10 extends the the existing qmp command "query-memory-device" to
return information of NVDIMM devices required by Xen.

Haozhong Zhang (10):
  01/10 nvdimm xen: disable label support on Xen
  02/10 xen-hvm: initialize DM ACPI
  03/10 xen-hvm: support copying ACPI to guest memory
  04/10 nvdimm acpi: do not use fw_cfg on Xen
  05/10 nvdimm acpi: copy NFIT to Xen guest
  06/10 nvdimm acpi: build and copy NVDIMM namespace devices to guest on Xen
  07/10 xen-hvm: enable building DM ACPI on i386 machine
  08/10 hostmem: add a host memory backend for Xen
  09/10 xen-hvm: create hotplug memory region on Xen
  10/10 qapi: extend 'query-memory-devices' to list devices of specified type

 backends/Makefile.objs   |   1 +
 backends/hostmem-xen.c   | 121 ++++++++++++++++++++++++++++
 backends/hostmem.c       |   8 ++
 hmp.c                    |   3 +-
 hw/acpi/aml-build.c      |   9 ++-
 hw/acpi/nvdimm.c         |  67 +++++++++++-----
 hw/i386/pc.c             |  98 ++++++++++++-----------
 hw/mem/nvdimm.c          |  44 ++++++++++-
 hw/mem/pc-dimm.c         |  76 +++++++++++-------
 include/hw/i386/pc.h     |   1 +
 include/hw/mem/nvdimm.h  |   2 +
 include/hw/mem/pc-dimm.h |   1 +
 include/hw/xen/xen.h     |  20 +++++
 qapi-schema.json         |  48 ++++++++++-
 qmp.c                    |  13 ++-
 xen-hvm-stub.c           |  10 +++
 xen-hvm.c                | 202 +++++++++++++++++++++++++++++++++++++++++++++++
 17 files changed, 620 insertions(+), 104 deletions(-)
 create mode 100644 backends/hostmem-xen.c

-- 
2.12.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-03-20  0:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20  0:12 Haozhong Zhang [this message]
2017-03-20  0:12 ` [RFC QEMU PATCH v2 01/10] nvdimm xen: disable label support on Xen Haozhong Zhang
2017-04-01 12:25   ` Konrad Rzeszutek Wilk
2017-03-20  0:12 ` [RFC QEMU PATCH v2 02/10] xen-hvm: initialize DM ACPI Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 03/10] xen-hvm: support copying ACPI to guest memory Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 04/10] nvdimm acpi: do not use fw_cfg on Xen Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 05/10] nvdimm acpi: copy NFIT to Xen guest Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 06/10] nvdimm acpi: build and copy NVDIMM namespace devices to guest on Xen Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 07/10] xen-hvm: initiate building DM ACPI on i386 machine Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 08/10] hostmem: add a host memory backend for Xen Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 09/10] xen-hvm: create hotplug memory region on Xen Haozhong Zhang
2017-03-20  0:12 ` [RFC QEMU PATCH v2 10/10] qapi: extend 'query-memory-devices' to list devices of specified type Haozhong Zhang
2017-04-11  8:56   ` [Qemu-devel] " Markus Armbruster
2017-03-20  0:26 ` [Qemu-devel] [RFC QEMU PATCH v2 00/10] Implement vNVDIMM for Xen HVM guest no-reply
2017-03-28 13:18 ` no-reply

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=20170320001249.25521-1-haozhong.zhang@intel.com \
    --to=haozhong.zhang@intel.com \
    --cc=anthony.perard@citrix.com \
    --cc=armbru@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=imammedo@redhat.com \
    --cc=konrad@darnok.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.org \
    /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).