o, 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...)
>
> For virtio-pmem, we are not providing advance features like
> namespace and various
> other features which ACPI/NVDIMM hardware provides. This is just to
> keep paravirt
> device simple.
Hmm, I see.
Thank you for your explanation.
Bye.
---
Yasunori Goto
>
> Moreover I have not yet looked at ndctl side of things. I am not
> 100% sure how
> ndctl will handle 'virtio-pmem'.
>
> Adding 'Dan' in loop, he can add his thoughts.
>
> Thanks,
> Pankaj
>
terface. This could be done with a new SPA Range GUID with
> the NFIT, or a custom virtio-pci device that registers a special
> nvdimm region with this property. My preference is whichever approach
> minimizes the code duplication, because the pmem driver should be
> re-used as much as possible.
Ok, I see.
Thank you very much for your explanation.
Bye,
---
Yasunori Goto
> On Tue, May 22, 2018 at 10:08 PM, Yasunori Goto <y-g...@jp.fujitsu.com> wrote:
> > 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,
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,
