From: Xiao Guangrong <xiaoguangrong.eric@gmail.com>
To: Yang Zhong <yang.zhong@intel.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, alex.williamson@redhat.com,
pbonzini@redhat.com, anthony.xu@intel.com
Subject: Re: [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file
Date: Mon, 16 Oct 2017 18:20:32 +0800 [thread overview]
Message-ID: <ebb88add-3173-78b9-397e-53a364ca0d53@gmail.com> (raw)
In-Reply-To: <1508144183-30844-1-git-send-email-yang.zhong@intel.com>
On 10/16/2017 04:56 PM, Yang Zhong wrote:
> 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.
No.
memory-backed-file does not dedicate for nvdimm only, it can be mapped
as normal memory as well. Rather more, this is no way to stop guest to
use it as DMA.
next prev parent reply other threads:[~2017-10-16 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 8:56 [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file Yang Zhong
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 ` Xiao Guangrong [this message]
2017-10-16 11:58 ` [Qemu-devel] [PATCH 0/2] add "nopin" option in the memory-backend-file 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=ebb88add-3173-78b9-397e-53a364ca0d53@gmail.com \
--to=xiaoguangrong.eric@gmail.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=yang.zhong@intel.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).