public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hp.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@lists.01.org, Neil Brown <neilb@suse.de>,
	Greg KH <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Robert Moore <robert.moore@intel.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [Linux-nvdimm] [PATCH v2 05/20] libnd, nd_acpi: dimm/memory-devices
Date: Fri, 01 May 2015 11:48:13 -0600	[thread overview]
Message-ID: <1430502493.23761.145.camel@misato.fc.hp.com> (raw)
In-Reply-To: <20150428182439.35812.81191.stgit@dwillia2-desk3.amr.corp.intel.com>

On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
> Register the memory devices described in the nfit as libnd 'dimm'
> devices on an nd bus.  The kernel assigned device id for dimms is
> dynamic.  If userspace needs a more static identifier it should consult
> a provider-specific attribute.  In the case where NFIT is the provider,
> the 'nmemX/nfit/handle' or 'nmemX/nfit/serial' attributes may be used
> for this purpose.
 :
> +
> +static int nd_acpi_register_dimms(struct acpi_nfit_desc *acpi_desc)
> +{
> +	struct nfit_mem *nfit_mem;
> +
> +	list_for_each_entry(nfit_mem, &acpi_desc->dimms, list) {
> +		struct nd_dimm *nd_dimm;
> +		unsigned long flags = 0;
> +		u32 nfit_handle;
> +
> +		nfit_handle = __to_nfit_memdev(nfit_mem)->nfit_handle;
> +		nd_dimm = nd_acpi_dimm_by_handle(acpi_desc, nfit_handle);
> +		if (nd_dimm) {
> +			/*
> +			 * If for some reason we find multiple DCRs the
> +			 * first one wins
> +			 */
> +			dev_err(acpi_desc->dev, "duplicate DCR detected: %s\n",
> +					nd_dimm_name(nd_dimm));
> +			continue;
> +		}
> +
> +		if (nfit_mem->bdw && nfit_mem->memdev_pmem)
> +			flags |= NDD_ALIASING;

Does this check work for a NVDIMM card which has multiple pmem regions
with label info, but does not have any bdw region configured?

The code assumes that namespace_pmem (NDD_ALIASING) and namespace_blk
have label info.  There may be an NVDIMM card with a single blk region
without label info.

Instead of using the namespace types to assume the label info, how about
adding a flag to indicate the presence of the label info?  This avoids
the separation of namespace_io and namespace_pmem for the same pmem
driver.

Thanks,
-Toshi



  reply	other threads:[~2015-05-01 18:07 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 18:24 [PATCH v2 00/20] libnd: non-volatile memory device support Dan Williams
2015-04-28 18:24 ` [PATCH v2 02/20] libnd, nd_acpi: initial libnd infrastructure and NFIT support Dan Williams
2015-04-30 23:23   ` Rafael J. Wysocki
2015-05-01  0:39     ` Dan Williams
2015-05-01  1:21       ` Rafael J. Wysocki
2015-05-01 16:23         ` Dan Williams
2015-05-04 23:58           ` Rafael J. Wysocki
2015-05-04 23:46             ` Dan Williams
2015-05-15 19:44   ` [Linux-nvdimm] " Jeff Moyer
2015-05-15 20:41     ` Dan Williams
2015-04-28 18:24 ` [PATCH v2 03/20] nd_acpi, nfit-test: manufactured NFITs for interface development Dan Williams
2015-05-15 20:25   ` [Linux-nvdimm] " Jeff Moyer
2015-05-15 20:50     ` Dan Williams
2015-04-28 18:24 ` [PATCH v2 04/20] libnd: ndctl class device, and nd bus attributes Dan Williams
2015-05-15 21:00   ` [Linux-nvdimm] " Jeff Moyer
2015-04-28 18:24 ` [PATCH v2 05/20] libnd, nd_acpi: dimm/memory-devices Dan Williams
2015-05-01 17:48   ` Toshi Kani [this message]
2015-05-01 18:22     ` [Linux-nvdimm] " Dan Williams
2015-05-01 18:19       ` Toshi Kani
2015-05-01 18:43         ` Dan Williams
2015-05-01 19:15           ` Toshi Kani
2015-05-01 19:38             ` Dan Williams
2015-05-01 20:08               ` Toshi Kani
2015-04-28 18:24 ` [PATCH v2 06/20] libnd: ndctl.h, the nd ioctl abi Dan Williams
2015-04-28 18:24 ` [PATCH v2 08/20] libnd, nd_acpi: regions (block-data-window, persistent memory, volatile memory) Dan Williams
2015-04-29 15:53   ` [Linux-nvdimm] " Elliott, Robert (Server Storage)
2015-04-29 15:59     ` Dan Williams
2015-05-04 20:26   ` Toshi Kani
2015-05-09 23:55     ` Dan Williams
2015-05-28 18:36       ` Toshi Kani
2015-05-28 19:59         ` Dan Williams
2015-05-28 20:51           ` Linda Knippers
2015-05-28 20:58             ` Dan Williams
2015-04-28 18:25 ` [PATCH v2 12/20] libnd, nd_acpi: add interleave-set state-tracking infrastructure Dan Williams
2015-04-28 20:52 ` [PATCH v2 00/20] libnd: non-volatile memory device support Andy Lutomirski
2015-04-28 20:59   ` Dan Williams
2015-04-28 21:06     ` Andy Lutomirski
2015-04-28 22:28       ` Dan Williams
2015-04-28 23:05         ` Andy Lutomirski
2015-04-30 20:56           ` Ross Zwisler
2015-04-28 21:24 ` [Linux-nvdimm] " Elliott, Robert (Server Storage)
2015-04-28 22:15   ` Dan Williams
2015-05-07  7:29     ` Christoph Hellwig
2015-04-29  0:25 ` Rafael J. Wysocki
2015-04-29  1:22   ` Dan Williams
2015-05-05  0:06     ` Rafael J. Wysocki
2015-05-08  6:31       ` Williams, Dan J

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=1430502493.23761.145.camel@misato.fc.hp.com \
    --to=toshi.kani@hp.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=neilb@suse.de \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@intel.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