Re: [Qemu-devel] [RFC PATCH 1/1] nvdimm: let qemu requiring section alignment of pmem resource.

2018-06-11 Thread Zhang,Yi
On 一, 2018-06-11 at 19:55 -0700, Dan Williams wrote: > On Mon, Jun 11, 2018 at 9:26 AM, Stefan Hajnoczi > wrote: > > > > On Mon, Jun 11, 2018 at 06:54:25PM +0800, Zhang Yi wrote: > > > > > > Nvdimm driver use Memory hot-plug APIs to map it's pmem resource, > > > which at a section granularity.

Re: [PATCH v5 2/4] resource: Use list_head to link sibling resource

2018-06-11 Thread kbuild test robot
Hi Baoquan, I love your patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.17 next-20180608] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v5 2/4] resource: Use list_head to link sibling resource

2018-06-11 Thread kbuild test robot
Hi Baoquan, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17 next-20180608] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Jane Chu
On 6/11/2018 6:50 PM, Naoya Horiguchi wrote: On Mon, Jun 11, 2018 at 08:19:54AM -0700, Dan Williams wrote: On Mon, Jun 11, 2018 at 7:56 AM, Michal Hocko wrote: On Mon 11-06-18 07:44:39, Dan Williams wrote: [...] I'm still trying to understand the next level of detail on where you think the

Re: [PATCH v5 1/4] resource: Move reparent_resources() to kernel/resource.c and make it public

2018-06-11 Thread kbuild test robot
Hi Baoquan, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17 next-20180608] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v5 1/4] resource: Move reparent_resources() to kernel/resource.c and make it public

2018-06-11 Thread Baoquan He
On 06/12/18 at 11:28am, Baoquan He wrote: > reparent_resources() is duplicated in arch/microblaze/pci/pci-common.c > and arch/powerpc/kernel/pci-common.c, so move it to kernel/resource.c > so that it's shared. Later its code also need be updated using list_head > to replace singly linked list. >

[PATCH v5 1/4] resource: Move reparent_resources() to kernel/resource.c and make it public

2018-06-11 Thread Baoquan He
reparent_resources() is duplicated in arch/microblaze/pci/pci-common.c and arch/powerpc/kernel/pci-common.c, so move it to kernel/resource.c so that it's shared. Later its code also need be updated using list_head to replace singly linked list. Signed-off-by: Baoquan He Cc: Michal Simek Cc:

[PATCH v5 2/4] resource: Use list_head to link sibling resource

2018-06-11 Thread Baoquan He
The struct resource uses singly linked list to link siblings, implemented by pointer operation. Replace it with list_head for better code readability. Based on this list_head replacement, it will be very easy to do reverse iteration on iomem_resource's sibling list in later patch. Besides, type

[PATCH v5 0/4] resource: Use list_head to link sibling resource

2018-06-11 Thread Baoquan He
This patchset is doing: 1) Replace struct resource's sibling list from singly linked list to list_head. Clearing out those pointer operation within singly linked list for better code readability. 2) Based on list_head replacement, add a new function walk_system_ram_res_rev() which can does

Re: [Qemu-devel] [RFC PATCH 1/1] nvdimm: let qemu requiring section alignment of pmem resource.

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 9:26 AM, Stefan Hajnoczi wrote: > On Mon, Jun 11, 2018 at 06:54:25PM +0800, Zhang Yi wrote: >> Nvdimm driver use Memory hot-plug APIs to map it's pmem resource, >> which at a section granularity. >> >> When QEMU emulated the vNVDIMM device, decrease the label-storage, >>

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 6:50 PM, Naoya Horiguchi wrote: > On Mon, Jun 11, 2018 at 08:19:54AM -0700, Dan Williams wrote: [..] > Anyway I'll find time to work on this, while now I'm testing the dax > support patches and fixing a bug I found recently. Ok, with this and other review feedback these

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Naoya Horiguchi
On Mon, Jun 11, 2018 at 08:19:54AM -0700, Dan Williams wrote: > On Mon, Jun 11, 2018 at 7:56 AM, Michal Hocko wrote: > > On Mon 11-06-18 07:44:39, Dan Williams wrote: > > [...] > >> I'm still trying to understand the next level of detail on where you > >> think the design should go next? Is it

回复:linux-nvdimm@lists.01.org

2018-06-11 Thread 吴先生
原邮件信息 - 发件人:cpqt...@nsuk.org 收件人:linux-nvdimm@lists.01.org; 发送时间:2018-6-19 7:45:24 主题: 敏捷软件开发(Agile Software Development ) 内*容 *请 *附-件-查-阅 959717 ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org

Re: [PATCH v11 3/7] mm: fix __gup_device_huge vs unmap

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 2:58 PM, Andrew Morton wrote: > On Fri, 18 May 2018 18:35:08 -0700 Dan Williams > wrote: > >> get_user_pages_fast() for device pages is missing the typical validation >> that all page references have been taken while the mapping was valid. >> Without this validation

Re: [PATCH v11 3/7] mm: fix __gup_device_huge vs unmap

2018-06-11 Thread Andrew Morton
On Fri, 18 May 2018 18:35:08 -0700 Dan Williams wrote: > get_user_pages_fast() for device pages is missing the typical validation > that all page references have been taken while the mapping was valid. > Without this validation truncate operations can not reliably coordinate > against new page

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Andi Kleen
On Mon, Jun 11, 2018 at 08:19:54AM -0700, Dan Williams wrote: > On Mon, Jun 11, 2018 at 7:56 AM, Michal Hocko wrote: > > On Mon 11-06-18 07:44:39, Dan Williams wrote: > > [...] > >> I'm still trying to understand the next level of detail on where you > >> think the design should go next? Is it

Re: [PATCH v4 02/12] device-dax: Cleanup vm_fault de-reference chains

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 10:12 AM, Laurent Dufour wrote: > On 09/06/2018 01:50, Dan Williams wrote: >> Define a local 'vma' variable rather than repetitively de-referencing >> the passed in 'struct vm_fault *' instance. > > Hi Dan, > > Why is this needed ? > > I can't see the real benefit, having

Re: [PATCH v4 02/12] device-dax: Cleanup vm_fault de-reference chains

2018-06-11 Thread Laurent Dufour
On 09/06/2018 01:50, Dan Williams wrote: > Define a local 'vma' variable rather than repetitively de-referencing > the passed in 'struct vm_fault *' instance. Hi Dan, Why is this needed ? I can't see the real benefit, having the vma deferenced from the vm_fault structure is not obfuscating the

Re: [PATCH v4 10/12] filesystem-dax: Introduce dax_lock_page()

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 8:41 AM, Jan Kara wrote: > On Fri 08-06-18 16:51:14, Dan Williams wrote: >> In preparation for implementing support for memory poison (media error) >> handling via dax mappings, implement a lock_page() equivalent. Poison >> error handling requires rmap and needs guarantees

[PATCH 0/2] test: add some helper function and cleanup test script

2018-06-11 Thread Masayoshi Mizuma
Some test scripts have same function. So, let's cleanup to stop the duplication by intoducing 'test/common' file. Test scripts includes the common file to use the functions. Masayoshi Mizuma (2): test: add some helper function for test script test: cleanup test scripts test/blk-exhaust.sh

[PATCH 1/2] test: add some helper function for test script

2018-06-11 Thread Masayoshi Mizuma
From: Masayoshi Mizuma Some test scripts have same function. So, this patch introduces the functions to 'test/common' new file. Signed-off-by: Masayoshi Mizuma --- test/common | 57 + 1 file changed, 57 insertions(+) create mode 100644

[PATCH 2/2] test: cleanup test scripts

2018-06-11 Thread Masayoshi Mizuma
From: Masayoshi Mizuma Include 'common' file to use some fucntions for test scripts. Signed-off-by: Masayoshi Mizuma --- test/blk-exhaust.sh | 21 +++- test/btt-check.sh | 35 -- test/btt-errors.sh| 20 ---

Re: [PATCH v4 11/12] mm, memory_failure: Teach memory_failure() about dev_pagemap pages

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 8:50 AM, Jan Kara wrote: > On Fri 08-06-18 16:51:19, Dan Williams wrote: >> mce: Uncorrected hardware memory error in user-access at af34214200 >> {1}[Hardware Error]: It has been corrected by h/w and requires no >> further action >> mce: [Hardware Error]:

Important Notification

2018-06-11 Thread Information Update
Dear Recipent , This email address has won Three Million Pounds on the o2 mobile sweepstakes.Please Contact Payment Cordinator Mat on email : mrw...@o2loto.co.uk for explanation and payment processing . Yours Faithfully Debbie Spence Cordinator O2 Mobile Promotional Sweepstakes.

Re: [PATCH v4 11/12] mm, memory_failure: Teach memory_failure() about dev_pagemap pages

2018-06-11 Thread Jan Kara
On Fri 08-06-18 16:51:19, Dan Williams wrote: > mce: Uncorrected hardware memory error in user-access at af34214200 > {1}[Hardware Error]: It has been corrected by h/w and requires no further > action > mce: [Hardware Error]: Machine check events logged > {1}[Hardware Error]:

Re: [PATCH v4 10/12] filesystem-dax: Introduce dax_lock_page()

2018-06-11 Thread Jan Kara
On Fri 08-06-18 16:51:14, Dan Williams wrote: > In preparation for implementing support for memory poison (media error) > handling via dax mappings, implement a lock_page() equivalent. Poison > error handling requires rmap and needs guarantees that the page->mapping > association is maintained /

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 7:56 AM, Michal Hocko wrote: > On Mon 11-06-18 07:44:39, Dan Williams wrote: > [...] >> I'm still trying to understand the next level of detail on where you >> think the design should go next? Is it just the HWPoison page flag? >> Are you concerned about supporting greater

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Michal Hocko
On Mon 11-06-18 07:44:39, Dan Williams wrote: [...] > I'm still trying to understand the next level of detail on where you > think the design should go next? Is it just the HWPoison page flag? > Are you concerned about supporting greater than PAGE_SIZE poison? I simply do not want to check for

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Dan Williams
On Mon, Jun 11, 2018 at 12:50 AM, Michal Hocko wrote: > On Thu 07-06-18 09:52:22, Dan Williams wrote: >> On Thu, Jun 7, 2018 at 7:37 AM, Michal Hocko wrote: >> > On Wed 06-06-18 06:44:45, Dan Williams wrote: >> >> On Wed, Jun 6, 2018 at 12:39 AM, Michal Hocko wrote: >> >> > On Tue 05-06-18

[PATCH v1] libnvdimm, namespace: Replace kmemdup() with kstrndup()

2018-06-11 Thread Andy Shevchenko
kstrndup() takes care of '\0' terminator for the strings. Use it here instead of kmemdup() + explicit terminating the input string. Signed-off-by: Andy Shevchenko --- drivers/nvdimm/namespace_devs.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

Re: [PATCH v2 00/11] mm: Teach memory_failure() about ZONE_DEVICE pages

2018-06-11 Thread Michal Hocko
On Thu 07-06-18 09:52:22, Dan Williams wrote: > On Thu, Jun 7, 2018 at 7:37 AM, Michal Hocko wrote: > > On Wed 06-06-18 06:44:45, Dan Williams wrote: > >> On Wed, Jun 6, 2018 at 12:39 AM, Michal Hocko wrote: > >> > On Tue 05-06-18 07:33:17, Dan Williams wrote: > >> >> On Tue, Jun 5, 2018 at 7:11