On Wed, Jun 6, 2018 at 4:20 PM, Elliott, Robert (Persistent Memory)
> > Okay, we can move to the symbolic names. Do you want them to be that
> long, or
> > would:
> > nvdimm-cap-cpu
> > nvdimm-cap-mem-ctrl
> > nvdimm-cap-mirroring
> Wait, why is mirroring part of this?
This data structure is intended to report any kind of platform capability, not
just platform persistence capabilities.
Yes, but here's nothing actionable that a qemu guest OS can do with
that mirroring information, so there's no need at this time to add cli
cruft and code to support it.