qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: pbonzini@redhat.com, imammedo@redhat.com
Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com>,
	ehabkost@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
	gleb@kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, dan.j.williams@intel.com, rth@twiddle.net
Subject: [Qemu-devel] [PATCH 00/15] NVDIMM: introduce nvdimm label support
Date: Thu, 17 Mar 2016 16:32:46 +0800	[thread overview]
Message-ID: <1458203581-59143-1-git-send-email-guangrong.xiao@linux.intel.com> (raw)

This patchset is against commit d4207b223eef3 (fw-cfg: support writeable
blobs) on pci branch of Michael's git tree and can be found at:
      https://github.com/xiaogr/qemu.git nvdimm-label-v1

This is the last part of vNVDIMM implementation which introduces nvdimm
label support

Currently Linux NVDIMM driver does not support namespace operation on this
kind of PMEM, apply below changes to support dynamical namespace:

@@ -798,7 +823,8 @@ static int acpi_nfit_register_dimms(struct acpi_nfit_desc *a
                        continue;
                }
 
-               if (nfit_mem->bdw && nfit_mem->memdev_pmem)
+               //if (nfit_mem->bdw && nfit_mem->memdev_pmem)
+               if (nfit_mem->memdev_pmem)
                        flags |= NDD_ALIASING;

You can append a NVDIMM device in guest and do:                       
# cd /sys/bus/nd/devices/
# cd namespace0.0/
# echo `uuidgen` > uuid
# echo `expr 1024 \* 1024 \* 128` > size
then reload nd.pmem.ko

You can see /dev/pmem0 appears

Xiao Guangrong (15):
  pc-dimm: get memory region from ->get_memory_region()
  pc-dimm: introduce realize callback
  pc-dimm: keep the state of the whole backend memory
  nvdimm: support nvdimm label
  acpi: add aml_object_type
  acpi: add aml_call5
  nvdimm acpi: set HDLE properly
  nvdimm acpi: save arg3 of _DSM method
  nvdimm acpi: check UUID
  nvdimm acpi: abstract the operations for root device and nvdimm
    devices
  nvdimm acpi: check revision
  nvdimm acpi: support Get Namespace Label Size function
  nvdimm acpi: support Get Namespace Label Data function
  nvdimm acpi: support Set Namespace Label Data function
  docs: add NVDIMM ACPI documentation

 docs/specs/acpi_nvdimm.txt  | 132 +++++++++++++++
 hw/acpi/aml-build.c         |  22 +++
 hw/acpi/nvdimm.c            | 392 ++++++++++++++++++++++++++++++++++++++++----
 hw/mem/nvdimm.c             |  95 +++++++++++
 hw/mem/pc-dimm.c            |  21 ++-
 include/hw/acpi/aml-build.h |   3 +
 include/hw/mem/nvdimm.h     |  61 ++++++-
 include/hw/mem/pc-dimm.h    |   6 +-
 8 files changed, 694 insertions(+), 38 deletions(-)
 create mode 100644 docs/specs/acpi_nvdimm.txt

-- 
1.8.3.1

             reply	other threads:[~2016-03-17  8:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17  8:32 Xiao Guangrong [this message]
2016-03-17  8:32 ` [Qemu-devel] [PATCH 01/15] pc-dimm: get memory region from ->get_memory_region() Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 02/15] pc-dimm: introduce realize callback Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 03/15] pc-dimm: keep the state of the whole backend memory Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 04/15] nvdimm: support nvdimm label Xiao Guangrong
2016-03-17 10:28   ` Stefan Hajnoczi
2016-03-23  3:40     ` Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 05/15] acpi: add aml_object_type Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 06/15] acpi: add aml_call5 Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 07/15] nvdimm acpi: set HDLE properly Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 08/15] nvdimm acpi: save arg3 of _DSM method Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 09/15] nvdimm acpi: check UUID Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 10/15] nvdimm acpi: abstract the operations for root device and nvdimm devices Xiao Guangrong
2016-03-17 10:35   ` Stefan Hajnoczi
2016-03-23  3:43     ` Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 11/15] nvdimm acpi: check revision Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 12/15] nvdimm acpi: support Get Namespace Label Size function Xiao Guangrong
2016-03-17 10:58   ` Stefan Hajnoczi
2016-03-23  3:46     ` Xiao Guangrong
2016-03-17  8:32 ` [Qemu-devel] [PATCH 13/15] nvdimm acpi: support Get Namespace Label Data function Xiao Guangrong
2016-03-17  8:33 ` [Qemu-devel] [PATCH 14/15] nvdimm acpi: support Set " Xiao Guangrong
2016-03-17  8:33 ` [Qemu-devel] [PATCH 15/15] docs: add NVDIMM ACPI documentation Xiao Guangrong
2016-03-17 10:04 ` [Qemu-devel] [PATCH 00/15] NVDIMM: introduce nvdimm label support Stefan Hajnoczi
2016-03-22 15:37   ` Dan Williams
2016-03-22 20:30     ` Stefan Hajnoczi
2016-03-23  2:46       ` Xiao Guangrong
2016-03-23 16:48         ` Stefan Hajnoczi
2016-03-22 11:17 ` Michael S. Tsirkin
2016-03-23  3:47   ` Xiao Guangrong

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=1458203581-59143-1-git-send-email-guangrong.xiao@linux.intel.com \
    --to=guangrong.xiao@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=gleb@kernel.org \
    --cc=imammedo@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.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).