From: Yang Zhong <yang.zhong@intel.com>
To: qemu-devel@nongnu.org
Cc: xiaoguangrong.eric@gmail.com, ehabkost@redhat.com,
alex.williamson@redhat.com, pbonzini@redhat.com,
anthony.xu@intel.com, yang.zhong@intel.com
Subject: [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file
Date: Mon, 16 Oct 2017 16:56:21 +0800 [thread overview]
Message-ID: <1508144183-30844-1-git-send-email-yang.zhong@intel.com> (raw)
Qemu does not need pin NVDIMM memory for VFIO device during VFIO
hotplug, what's more, if there is no NVDIMM hw in the test machine,
the VFIO hotplug operation will need at least 10 minutes to pin RAM
as the NVDIMM, this time is not accepted. So we add "nopin=on" option
in the memory-backed-file, which can avoid to pin RAM memory for NVDIMM.
The new command like below:
-object memory-backend-file,id=mem0,share,nopin=on,mem-path=kvm.img,size=9161408512
The default of "nopin" still "off" value, which is same with previous value.
Yang Zhong (2):
hostmem-file: Add "nopin" option for memory-backend-file
nvdimm: Add "nopin" for related documents
backends/hostmem-file.c | 23 +++++++++++++++++++++++
docs/nvdimm.txt | 10 ++++++++--
hw/vfio/common.c | 12 +++++++++++-
qemu-options.hx | 6 +++++-
4 files changed, 47 insertions(+), 4 deletions(-)
--
1.9.1
next reply other threads:[~2017-10-16 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 8:56 Yang Zhong [this message]
2017-10-16 8:56 ` [Qemu-devel] [PATCH 1/2] hostmem-file: Add "nopin" option for memory-backend-file Yang Zhong
2017-10-16 8:56 ` [Qemu-devel] [PATCH 2/2] nvdimm: Add "nopin" for related documents Yang Zhong
2017-10-16 10:20 ` [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file Xiao Guangrong
2017-10-16 11:58 ` Paolo Bonzini
2017-10-18 5:57 ` Zhong Yang
2017-10-18 9:48 ` Paolo Bonzini
2017-10-18 9:56 ` Zhong Yang
2017-10-18 5:34 ` Zhong Yang
2017-10-16 15:47 ` Alex Williamson
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=1508144183-30844-1-git-send-email-yang.zhong@intel.com \
--to=yang.zhong@intel.com \
--cc=alex.williamson@redhat.com \
--cc=anthony.xu@intel.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 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).