[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4jhoxDXUwv4vgDYo=aLAAOxZ-Yq0qcgi5kHF_ybGUd-gg@mail.gmail.com>
Date: Fri, 7 Jun 2019 13:07:30 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Vishal Verma <vishal.l.verma@...el.com>,
Keith Busch <keith.busch@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
kbuild test robot <lkp@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
X86 ML <x86@...nel.org>, linux-efi <linux-efi@...r.kernel.org>
Subject: Re: [PATCH v3 08/10] device-dax: Add a driver for "hmem" devices
On Fri, Jun 7, 2019 at 12:54 PM Dave Hansen <dave.hansen@...el.com> wrote:
>
> On 6/7/19 12:27 PM, Dan Williams wrote:
> > This consumes "hmem" devices the producer of "hmem" devices is saved for
> > a follow-on patch so that it can reference the new CONFIG_DEV_DAX_HMEM
> > symbol to gate performing the enumeration work.
>
> Do these literally show up as /dev/hmemX?
No, everything shows as daxX.Y character devices across hmem and pmem
producers. For example:
# daxctl list -RDu
[
{
"path":"/platform/hmem.1",
"id":1,
"size":"4.00 GiB (4.29 GB)",
"align":2097152,
"devices":[
{
"chardev":"dax1.0",
"size":"4.00 GiB (4.29 GB)"
}
]
},
{
"path":"/LNXSYSTM:00/LNXSYBUS:00/ACPI0012:00/ndbus0/region2/dax2.1",
"id":2,
"size":"125.01 GiB (134.23 GB)",
"align":2097152,
"devices":[
{
"chardev":"dax2.0",
"size":"125.01 GiB (134.23 GB)"
}
]
},
{
"path":"/platform/hmem.0",
"id":0,
"size":"4.00 GiB (4.29 GB)",
"align":2097152,
"devices":[
{
"chardev":"dax0.0",
"size":"4.00 GiB (4.29 GB)"
}
]
}
]
Powered by blists - more mailing lists