From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f199.google.com (mail-wr0-f199.google.com [209.85.128.199]) by kanga.kvack.org (Postfix) with ESMTP id A489D6B0006 for ; Mon, 21 May 2018 05:04:14 -0400 (EDT) Received: by mail-wr0-f199.google.com with SMTP id l6-v6so10782801wrn.17 for ; Mon, 21 May 2018 02:04:14 -0700 (PDT) Received: from mx2.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id k64-v6si4150781edc.17.2018.05.21.02.04.13 for (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 21 May 2018 02:04:13 -0700 (PDT) Date: Mon, 21 May 2018 11:04:10 +0200 From: Jan Kara Subject: Re: [PATCH v10] mm: introduce MEMORY_DEVICE_FS_DAX and CONFIG_DEV_PAGEMAP_OPS Message-ID: <20180521090410.7ygosxzjfhceqrq4@quack2.suse.cz> References: <152658753673.26786.16458605771414761966.stgit@dwillia2-desk3.amr.corp.intel.com> <20180518094616.GA25838@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Dan Williams Cc: Christoph Hellwig , linux-nvdimm , Martin Schwidefsky , Heiko Carstens , Michal Hocko , kbuild test robot , Thomas Meyer , Dave Jiang , =?iso-8859-1?B?Suly9G1l?= Glisse , Jan Kara , linux-fsdevel , Linux MM , Gerald Schaefer On Fri 18-05-18 09:00:29, Dan Williams wrote: > On Fri, May 18, 2018 at 2:46 AM, Christoph Hellwig wrote: > >> + select DEV_PAGEMAP_OPS if (ZONE_DEVICE && !FS_DAX_LIMITED) > > > > Btw, what was the reason again we couldn't get rid of FS_DAX_LIMITED? > > The last I heard from Gerald they were still mildly interested in > keeping the dccssblk dax support going with this limited mode, and > threatened to add full page support at a later date: > > --- > From: Gerald > > dcssblk seems to work fine, I did not see any SIGBUS while "executing > in place" from dcssblk with the current upstream kernel, maybe because > we only use dcssblk with fs dax in read-only mode. > > Anyway, the dcssblk change is fine with me. I will look into adding > struct pages for dcssblk memory later, to make it work again with > this change, but for now I do not know of anyone needing this in the > upstream kernel. > > https://www.spinics.net/lists/linux-xfs/msg14628.html > --- We definitely do have customers using "execute in place" on s390x from dcssblk. I've got about two bug reports for it when customers were updating from old kernels using original XIP to kernels using DAX. So we need to keep that working. Honza -- Jan Kara SUSE Labs, CR