From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
Cc: 'Dan Williams' <dan.j.williams@intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Eduardo Habkost <ehabkost@redhat.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
Qemu Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [qemu PATCH v4 3/4] nvdimm, acpi: support NFIT platform capabilities
Date: Thu, 7 Jun 2018 18:30:52 +0300 [thread overview]
Message-ID: <20180607182949-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <AT5PR8401MB1169403448C8AA5FF267F6A6AB650@AT5PR8401MB1169.NAMPRD84.PROD.OUTLOOK.COM>
On Wed, Jun 06, 2018 at 11:20:58PM +0000, Elliott, Robert (Persistent Memory) wrote:
>
> > > 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.
>
> We could add a short symbolic name to the definitions in ACPI that matches
> the ones selected for this command line option, if that'll help people
> find the right names to use.
>
> I recommend mc rather than mem-ctrl to keep dashes as special.
>
I'm not sure it's a good idea:
dashes aren't special in qemu, and mc's way too brief.
--
MST
next prev parent reply other threads:[~2018-06-07 15:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 16:31 [Qemu-devel] [qemu PATCH v4 0/4] support NFIT platform capabilities Ross Zwisler
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 1/4] nvdimm: fix typo in label-size definition Ross Zwisler
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 2/4] tests/.gitignore: add entry for generated file Ross Zwisler
2018-05-21 16:41 ` Eric Blake
2018-05-21 17:32 ` Philippe Mathieu-Daudé
2018-05-21 18:29 ` Eric Blake
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 3/4] nvdimm, acpi: support NFIT platform capabilities Ross Zwisler
2018-06-05 15:25 ` Michael S. Tsirkin
2018-06-05 16:42 ` Ross Zwisler
2018-06-05 18:15 ` Dan Williams
2018-06-05 18:37 ` Michael S. Tsirkin
2018-06-05 22:07 ` Ross Zwisler
2018-06-05 22:21 ` Dan Williams
2018-06-06 16:50 ` Ross Zwisler
2018-06-06 17:00 ` Ross Zwisler
2018-06-06 17:08 ` Ross Zwisler
2018-06-06 19:06 ` Michael S. Tsirkin
2018-06-12 11:55 ` Igor Mammedov
2018-06-06 19:04 ` Michael S. Tsirkin
2018-06-06 19:07 ` Michael S. Tsirkin
2018-06-06 23:20 ` Elliott, Robert (Persistent Memory)
2018-06-06 23:40 ` Dan Williams
2018-06-07 15:29 ` Michael S. Tsirkin
2018-06-07 15:30 ` Michael S. Tsirkin [this message]
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 4/4] ACPI testing: test " Ross Zwisler
2018-05-25 17:51 ` [Qemu-devel] [qemu PATCH v4 0/4] support " Michael S. Tsirkin
2018-05-31 22:03 ` Ross Zwisler
2018-05-29 19:54 ` Ross Zwisler
2018-06-01 5:11 ` Elliott, Robert (Persistent Memory)
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=20180607182949-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=elliott@hpe.com \
--cc=imammedo@redhat.com \
--cc=linux-nvdimm@lists.01.org \
--cc=qemu-devel@nongnu.org \
--cc=ross.zwisler@linux.intel.com \
--cc=stefanha@redhat.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).