From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: NVDIMM-ML <linux-nvdimm@lists.01.org>
Subject: Questions about vNVDIMM on qemu/KVM
Date: Wed, 23 May 2018 14:08:12 +0900 [thread overview]
Message-ID: <20180523140809.622F.E1E9C6FF@jp.fujitsu.com> (raw)
Hello,
I'm investigating status of vNVDIMM on qemu/KVM,
and I have some questions about it. I'm glad if anyone answer them.
In my understanding, qemu/KVM has a feature to show NFIT for guest,
and it will be still updated about platform capability with this patch set.
https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg04756.html
And libvirt also supports this feature with <memory model='nvdimm'>
https://libvirt.org/formatdomain.html#elementsMemory
However, virtio-pmem is developing now, and it is better
for archtectures to detect regions of NVDIMM without ACPI (like s390x)
In addition, It is also necessary to flush guest contents on vNVDIMM
who has a backend-file.
Q1) Does ACPI.NFIT bus of qemu/kvm remain with virtio-pmem?
How do each roles become it if both NFIT and virtio-pmem will be available?
If my understanding is correct, both NFIT and virtio-pmem is used to
detect vNVDIMM regions, but only one seems to be necessary....
Otherwize, is the NFIT bus just for keeping compatibility,
and virtio-pmem is promising way?
Q2) What bus is(will be?) created for virtio-pmem?
I could confirm the bus of NFIT is created with <memory model='nvdimm'>,
and I heard other bus will be created for virtio-pmem, but I could not
find what bus is created concretely.
---
# ndctl list -B
{
"provider":"ACPI.NFIT",
"dev":"ndbus0"
}
---
I think it affects what operations user will be able to, and what
notification is necessary for vNVDIMM.
ACPI defines some operations like namespace controll, and notification
for NVDIMM health status or others.
(I suppose that other status notification might be necessary for vNVDIMM,
but I'm not sure yet...)
If my understanding is wrong, please correct me.
Thanks,
---
Yasunori Goto
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next reply other threads:[~2018-05-23 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 5:08 Yasunori Goto [this message]
2018-05-23 18:39 ` Questions about vNVDIMM on qemu/KVM Dan Williams
2018-05-24 7:19 ` Yasunori Goto
2018-05-24 14:08 ` Dan Williams
2018-05-25 5:02 ` Yasunori Goto
2018-06-01 11:54 ` Stefan Hajnoczi
2018-06-04 8:03 ` [Qemu-devel] " Pankaj Gupta
2018-06-06 1:44 ` Yasunori Goto
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=20180523140809.622F.E1E9C6FF@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=linux-nvdimm@lists.01.org \
--cc=qemu-devel@nongnu.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