Re: [PATCH 09/10] powerpc: Enable OpenCAPI Storage Class Memory driver on bare metal

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:47, Alastair D'Silva a écrit : From: Alastair D'Silva Enable OpenCAPI Storage Class Memory driver on bare metal Signed-off-by: Alastair D'Silva --- arch/powerpc/configs/powernv_defconfig | 4 1 file changed, 4 insertions(+) diff --git

Re: [QUESTION] Error on initializing dax by using different struct page size

2019-11-07 Thread Won-Kyo Choe
Thanks for the information. This is actually what I've been looking for! Regards, Won-Kyo ___ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-le...@lists.01.org

Re: [RFC PATCH v2 0/7] xfs: reflink & dedupe for fsdax (read/write path).

2019-11-07 Thread Dan Williams
On Thu, Nov 7, 2019 at 7:11 PM Shiyang Ruan wrote: > > Hi Darrick, Dave, > > Do you have any comment on this? Christoph pointed out at ALPSS that this problem has significant overlap with the shared page-cache for reflink problem. So I think we need to solve that first and then circle back to

Re: [RFC PATCH v2 0/7] xfs: reflink & dedupe for fsdax (read/write path).

2019-11-07 Thread Shiyang Ruan
Hi Darrick, Dave, Do you have any comment on this? On 10/30/19 12:13 PM, Shiyang Ruan wrote: This patchset aims to take care of this issue to make reflink and dedupe work correctly (actually in read/write path, there still has some problems, such as the page->mapping and page->index issue, in

Re: [PATCH v2 2/3] Maintainer Handbook: Maintainer Entry Profile

2019-11-07 Thread Dan Williams
On Thu, Nov 7, 2019 at 12:13 PM Jonathan Corbet wrote: > > Hi, Dan, > > A month or so ago I wrote... > > > > See Documentation/maintainer/maintainer-entry-profile.rst for more > > > details, > > > and a follow-on example profile for the libnvdimm subsystem. > > > > Thus far, the maintainer guide

Re: [PATCH 10/10] ocxl: Conditionally bind SCM devices to the generic OCXL driver

2019-11-07 Thread Alastair D'Silva
On Thu, 2019-11-07 at 19:08 +0100, Frederic Barrat wrote: > > Le 25/10/2019 à 06:47, Alastair D'Silva a écrit : > > From: Alastair D'Silva > > > > This patch allows the user to bind OpenCAPI SCM devices to the > > generic OCXL > > driver. > > > > Signed-off-by: Alastair D'Silva > > --- > >

Re: [QUESTION] Error on initializing dax by using different struct page size

2019-11-07 Thread Won-Kyo Choe
On Thu, Nov 07, 2019 at 07:54:21AM -0800, Dan Williams wrote: > On Thu, Nov 7, 2019 at 7:30 AM Won-Kyo Choe wrote: > > > > Hi, there. I'm using Opatne DC memory to use it a volatile memory. Recently, > > I found that if sizeof(struct page) is above 64 bytes (e.g. 128 byes), > > `device_dax`

Re: [PATCH 07/10] ocxl: Save the device serial number in ocxl_fn

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:47, Alastair D'Silva a écrit : From: Alastair D'Silva This patch retrieves the serial number of the card and makes it available to consumers of the ocxl driver via the ocxl_fn struct. Signed-off-by: Alastair D'Silva --- Acked-by: Frederic Barrat

Re: [PATCH 10/10] ocxl: Conditionally bind SCM devices to the generic OCXL driver

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:47, Alastair D'Silva a écrit : From: Alastair D'Silva This patch allows the user to bind OpenCAPI SCM devices to the generic OCXL driver. Signed-off-by: Alastair D'Silva --- I'm wondering if we should upstream this. Is it of any use outside of some serious debug

Re: [PATCH 06/10] ocxl: Add functions to map/unmap LPC memory

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:47, Alastair D'Silva a écrit : From: Alastair D'Silva Add functions to map/unmap LPC memory Signed-off-by: Alastair D'Silva --- drivers/misc/ocxl/config.c| 4 +++ drivers/misc/ocxl/core.c | 50 +++

Re: [PATCH 05/10] ocxl: Tally up the LPC memory on a link & allow it to be mapped

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:47, Alastair D'Silva a écrit : From: Alastair D'Silva Tally up the LPC memory on an OpenCAPI link & allow it to be mapped Signed-off-by: Alastair D'Silva --- drivers/misc/ocxl/core.c | 10 ++ drivers/misc/ocxl/link.c | 60

Re: [PATCH 04/10] powerpc: Map & release OpenCAPI LPC memory

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:46, Alastair D'Silva a écrit : From: Alastair D'Silva This patch adds platform support to map & release LPC memory. Signed-off-by: Alastair D'Silva --- arch/powerpc/include/asm/pnv-ocxl.h | 2 ++ arch/powerpc/platforms/powernv/ocxl.c | 41

Re: [PATCH 02/10] nvdimm: remove prototypes for nonexistent functions

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:46, Alastair D'Silva a écrit : From: Alastair D'Silva These functions don't exist, so remove the prototypes for them. Signed-off-by: Alastair D'Silva --- Reviewed-by: Frederic Barrat drivers/nvdimm/nd-core.h | 4 1 file changed, 4 deletions(-) diff --git

Re: [PATCH 03/10] powerpc: Add OPAL calls for LPC memory alloc/release

2019-11-07 Thread Frederic Barrat
Le 25/10/2019 à 06:46, Alastair D'Silva a écrit : From: Alastair D'Silva Add OPAL calls for LPC memory alloc/release Signed-off-by: Alastair D'Silva Acked-by: Andrew Donnellan --- Acked-by: Frederic Barrat arch/powerpc/include/asm/opal-api.h| 2 ++

Re: [QUESTION] Error on initializing dax by using different struct page size

2019-11-07 Thread Dan Williams
On Thu, Nov 7, 2019 at 7:30 AM Won-Kyo Choe wrote: > > Hi, there. I'm using Opatne DC memory to use it a volatile memory. Recently, > I found that if sizeof(struct page) is above 64 bytes (e.g. 128 byes), > `device_dax` cannot be initialized when system boots. I am aware that > for some reason

[QUESTION] Error on initializing dax by using different struct page size

2019-11-07 Thread Won-Kyo Choe
Hi, there. I'm using Opatne DC memory to use it a volatile memory. Recently, I found that if sizeof(struct page) is above 64 bytes (e.g. 128 byes), `device_dax` cannot be initialized when system boots. I am aware that for some reason there is a function, `__mm_zero_struct_page`, which limits the

Re: [PATCH v8 00/12] EFI Specific Purpose Memory Support

2019-11-07 Thread Rafael J. Wysocki
On Thu, Nov 7, 2019 at 2:49 PM Thomas Gleixner wrote: > > On Thu, 7 Nov 2019, Rafael J. Wysocki wrote: > > On Thu, Nov 7, 2019 at 2:57 AM Dan Williams > > wrote: > > > > Indeed. > > > > I have waited for comments on x86 bits from Thomas, but since they are > > not coming, I have just decided to

Re: [PATCH v8 00/12] EFI Specific Purpose Memory Support

2019-11-07 Thread Thomas Gleixner
On Thu, 7 Nov 2019, Rafael J. Wysocki wrote: > On Thu, Nov 7, 2019 at 2:57 AM Dan Williams wrote: > > Indeed. > > I have waited for comments on x86 bits from Thomas, but since they are > not coming, I have just decided to take patch [1/12] from this series, > which should be totally

Re: [PATCH v8 00/12] EFI Specific Purpose Memory Support

2019-11-07 Thread Rafael J. Wysocki
On Thu, Nov 7, 2019 at 2:57 AM Dan Williams wrote: > > Changes since v7: > - This is mostly a resend to get it refreshed in Ingo's inbox for v5.5 > consideration. It picks up a Reviewed-by on patch4 from Ard, has a > minor cosmetic rebase on v5.4-rc6 with no other changes, it merges >