All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jingqi Liu <jingqi.liu@intel.com>
To: imammedo@redhat.com, xiaoguangrong.eric@gmail.com,
	mst@redhat.com, marcel.apfelbaum@gmail.com, pbonzini@redhat.com,
	richard.henderson@linaro.org, ehabkost@redhat.com
Cc: Jingqi Liu <jingqi.liu@intel.com>, qemu-devel@nongnu.org
Subject: [PATCH v2 0/1] nvdimm: add 'target-node' option
Date: Mon, 19 Jul 2021 10:01:52 +0800	[thread overview]
Message-ID: <20210719020153.30574-1-jingqi.liu@intel.com> (raw)

Linux kernel version 5.1 brings in support for the volatile-use of
persistent memory as a hotplugged memory region (KMEM DAX).
When this feature is enabled, persistent memory can be seen as a
separate memory-only NUMA node(s). This newly-added memory can be
selected by its unique NUMA node.

Add 'target-node' option for 'nvdimm' device to indicate this NUMA
node. It can be extended to a new node after all existing NUMA nodes.

Changelog:
    v2:
        - Per Igor's comments, adjust target node error handling,
          and make both 'node' and 'target-node' properties mutually exclusive.
          Create a callback of nvdimm_pre_plug() for checking
          whether the 'target-node' is correct.
    v1:
        - It's the initial version.

Jingqi Liu (1):
  nvdimm: add 'target-node' option

 docs/nvdimm.txt         | 93 +++++++++++++++++++++++++++++++++++++++++
 hw/acpi/nvdimm.c        | 18 ++++----
 hw/i386/acpi-build.c    | 12 +++++-
 hw/i386/pc.c            |  4 ++
 hw/mem/nvdimm.c         | 43 ++++++++++++++++++-
 include/hw/mem/nvdimm.h | 17 +++++++-
 util/nvdimm-utils.c     | 22 ++++++++++
 7 files changed, 198 insertions(+), 11 deletions(-)

-- 
2.21.3



             reply	other threads:[~2021-07-19  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  2:01 Jingqi Liu [this message]
2021-07-19  2:01 ` [PATCH v2 1/1] nvdimm: add 'target-node' option Jingqi Liu
2021-07-29 12:44   ` Igor Mammedov
2021-08-03  5:55     ` 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=20210719020153.30574-1-jingqi.liu@intel.com \
    --to=jingqi.liu@intel.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.