We want to be able to cross reference the region and bus devices
with the device tree node that they were spawned from. libNVDIMM
handles creating the actual devices for these internally, so we
need to pass in a pointer to the relevant node in the descriptor.
Signed-off-by: Oliver O'Halloran
Currently there's no way to remove a region from and nvdimm_bus without
tearing down the whole bus. This patch adds an API for removing a single
region from the bus so that we can implement a sensible unbind operation
for the of_nd_region platform driver.
Signed-off-by: Oliver O'Halloran
This patch adds peliminary device-tree bindings for the NVDIMM driver.
Currently this only supports one bus (created at probe time) which all
regions are added to with individual regions being created by a platform
device driver.
Signed-off-by: Oliver O'Halloran
---
I suspect
Add a way direct link between the region and the platform device that
creates the region.
Signed-off-by: Oliver O'Halloran
---
drivers/nvdimm/of_nvdimm.c | 11 +++
drivers/nvdimm/region_devs.c | 13 +
include/linux/libnvdimm.h| 1 +
3 files changed,
Add device-tree binding documentation for the nvdimm region driver.
Cc: devicet...@vger.kernel.org
Signed-off-by: Oliver O'Halloran
---
.../devicetree/bindings/nvdimm/nvdimm-region.txt | 45 ++
1 file changed, 45 insertions(+)
create mode 100644
Scan the devicetree for an nvdimm-bus compatible and create
a platform device for them.
Signed-off-by: Oliver O'Halloran
---
arch/powerpc/platforms/powernv/opal.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/platforms/powernv/opal.c
Use SPDX identifiers in the documentation source, and move the
"Copyright" boilerplate that is emitted into the man page into a common
header file.
Signed-off-by: Dan Williams
---
Documentation/copyright.txt |8
On Fri, Mar 23, 2018 at 1:12 AM, Oliver O'Halloran wrote:
> Currently there's no way to remove a region from and nvdimm_bus without
> tearing down the whole bus. This patch adds an API for removing a single
> region from the bus so that we can implement a sensible unbind
On Fri, Mar 23, 2018 at 1:12 AM, Oliver O'Halloran wrote:
> This patch adds peliminary device-tree bindings for the NVDIMM driver.
*preliminary
> Currently this only supports one bus (created at probe time) which all
> regions are added to with individual regions being created
On Fri, Mar 23, 2018 at 1:12 AM, Oliver O'Halloran wrote:
> Add a way direct link between the region and the platform device that
> creates the region.
>
This linking would not be needed if of_nd_regions each lived on their own bus.
On 23/03/18 03:50 PM, Bjorn Helgaas wrote:
> Popping way up the stack, my original point was that I'm trying to
> remove restrictions on what devices can participate in peer-to-peer
> DMA. I think it's fairly clear that in conventional PCI, any devices
> in the same PCI hierarchy, i.e., below
For systems that don't support NUMA, numactl gives a loud and fatal error:
# numactl -N 0 ls
numactl: This system does not support NUMA policy
Follow this model in ndctl for NUMA based filtering:
# ./ndctl/ndctl list --numa-node=0
Error: This system does not support NUMA
This is done
On Fri, Mar 23, 2018 at 4:08 PM, Ross Zwisler
wrote:
> For systems that don't support NUMA, numactl gives a loud and fatal error:
>
> # numactl -N 0 ls
> numactl: This system does not support NUMA policy
>
> Follow this model in ndctl for NUMA based filtering:
>
On Thu, Mar 22, 2018 at 10:57:32PM +, Stephen Bates wrote:
> > I've seen the response that peers directly below a Root Port could not
> > DMA to each other through the Root Port because of the "route to self"
> > issue, and I'm not disputing that.
>
> Bjorn
>
> You asked me for a
On Fri, Mar 23, 2018 at 03:59:14PM -0600, Logan Gunthorpe wrote:
> On 23/03/18 03:50 PM, Bjorn Helgaas wrote:
> > Popping way up the stack, my original point was that I'm trying to
> > remove restrictions on what devices can participate in
> > peer-to-peer DMA. I think it's fairly clear that in
15 matches
Mail list logo