From: Linda Knippers <linda.knippers@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH 1/3] Allow all supported HPE DSM functions to be called
Date: Thu, 16 Feb 2017 17:52:29 -0500 [thread overview]
Message-ID: <8cfa36e1-2bdd-3e8a-1124-e210db2d7eb8@hpe.com> (raw)
In-Reply-To: <CAPcyv4gL3GCT6YnfOWpRG23vvmkf+ctZKXeXqGKrsJucKCxKqA@mail.gmail.com>
On 2/16/2017 5:49 PM, Dan Williams wrote:
> On Thu, Feb 16, 2017 at 2:47 PM, Linda Knippers <linda.knippers@hpe.com> wrote:
>>>> Several problems.
>>>> That family is documented for RFIC 0x0201.
>>>> No NVDIMM-N platform supports that DSM family.
>>>> When platforms do support 0x0201, some will also support NVDIMM-N. Since
>>>> opcodes are not documented, how do would they not step on each other?
>>>>
>>>> I don't think that works at all.
>>>>
>>>
>>> I'm confused there is no correlation between FIC and DSM family,
>>
>>
>> Page 7 of version 1.3 of your DSM spec says:
>>
>> Platforms that have the _DSM interface implemented, as outlined in this
>> section, can support a NVDIMM region with Region Format Interface Code
>> (RFIC) of 0x0201.
>>
>> Other DSM documents reference RFIC 0x0101.
>>
>>> at least not one Linux enforces.
>>
>>
>> That is true, but FW developers aren't being as loose.
>
> Yes, they are. We have 3 0x101 DSM families.
And they're all implemented for 0x101 devices.
-- ljk
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-02-16 22:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 16:27 [PATCH 0/3] apci, nfit: DSM improvements Linda Knippers
2017-02-13 16:27 ` [PATCH 1/3] Allow all supported HPE DSM functions to be called Linda Knippers
2017-02-13 17:28 ` Dan Williams
2017-02-13 18:17 ` Linda Knippers
2017-02-13 18:30 ` Dan Williams
2017-02-15 23:19 ` Linda Knippers
2017-02-16 0:29 ` Dan Williams
2017-02-16 0:45 ` Linda Knippers
2017-02-16 2:03 ` Dan Williams
2017-02-16 18:51 ` Linda Knippers
2017-02-16 19:35 ` Dan Williams
2017-02-16 20:13 ` Linda Knippers
2017-02-16 20:48 ` Dan Williams
2017-02-16 21:07 ` Dan Williams
2017-02-16 22:40 ` Linda Knippers
2017-02-16 22:43 ` Dan Williams
2017-02-16 22:47 ` Linda Knippers
2017-02-16 22:49 ` Dan Williams
2017-02-16 22:52 ` Linda Knippers [this message]
2017-02-16 22:33 ` Linda Knippers
2017-02-19 16:28 ` Boaz Harrosh
2017-02-13 16:27 ` [PATCH 2/3] Allow specifying a default DSM family Linda Knippers
2017-02-13 16:27 ` [PATCH 3/3] Remove unnecessary newline Linda Knippers
2017-02-13 17:32 ` Dan Williams
2017-02-13 18:02 ` Linda Knippers
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=8cfa36e1-2bdd-3e8a-1124-e210db2d7eb8@hpe.com \
--to=linda.knippers@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=linux-nvdimm@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.