From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Jens Axboe" <axboe@kernel.dk>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
linux390@de.ibm.com, "Alexander Viro" <viro@zeniv.linux.org.uk>,
"Matthew Wilcox" <willy@linux.intel.com>,
"Jeff Layton" <jlayton@primarydata.com>,
"Christoph Hellwig" <hch@lst.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Omar Sandoval" <osandov@osandov.com>,
"Boaz Harrosh" <boaz@plexistor.com>,
"Miklos Szeredi" <mszeredi@suse.cz>, "Jan Kara" <jack@suse.cz>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v2 7/7] pmem, dax: have direct_access use __pmem annotation
Date: Fri, 14 Aug 2015 10:55:18 -0600 [thread overview]
Message-ID: <1439571318.16263.3.camel@linux.intel.com> (raw)
In-Reply-To: <CAPcyv4j=h1FULCnmLbwNv6E0ySyZNKniM3GZEnNCpGeiqCb+Kg@mail.gmail.com>
On Thu, 2015-08-13 at 14:20 -0700, Dan Williams wrote:
> On Thu, Aug 13, 2015 at 9:51 AM, Ross Zwisler
> <ross.zwisler@linux.intel.com> wrote:
> > Update the annotation for the kaddr pointer returned by direct_access()
> > so that it is a __pmem pointer. This is consistent with the PMEM driver
> > and with how this direct_access() pointer is used in the DAX code.
> >
> > Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> > ---
> > Documentation/filesystems/Locking | 3 ++-
> > arch/powerpc/sysdev/axonram.c | 7 ++++---
> > drivers/block/brd.c | 4 ++--
> > drivers/nvdimm/pmem.c | 4 ++--
> > drivers/s390/block/dcssblk.c | 10 +++++----
> > fs/block_dev.c | 2 +-
> > fs/dax.c | 44 +++++++++++++++++++++------------------
> > include/linux/blkdev.h | 8 +++----
> > 8 files changed, 45 insertions(+), 37 deletions(-)
> >
> > diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking
> > index 6a34a0f..06d4434 100644
> > --- a/Documentation/filesystems/Locking
> > +++ b/Documentation/filesystems/Locking
> > @@ -397,7 +397,8 @@ prototypes:
> > int (*release) (struct gendisk *, fmode_t);
> > int (*ioctl) (struct block_device *, fmode_t, unsigned, unsigned long);
> > int (*compat_ioctl) (struct block_device *, fmode_t, unsigned, unsigned long);
> > - int (*direct_access) (struct block_device *, sector_t, void **, unsigned long *);
> > + int (*direct_access) (struct block_device *, sector_t, void __pmem **,
> > + unsigned long *);
>
> So this collides with the __pfn_t work. I think the we have a
> reasonable chance of getting that in to 4.3, so I'd wait to see if we
> hit any major roadblocks with that set [1] before merging these.
>
> [1]: https://lists.01.org/pipermail/linux-nvdimm/2015-August/001803.html
Fair enough. Yea, I hadn't merged with that series yet a) because I didn't
know when its review cycle would settle down and b) because that series hadn't
pulled in changes from Matthew for PMD support, which I was originally using
as a baseline.
I'll merge with your code for v3.
next prev parent reply other threads:[~2015-08-14 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 16:51 [PATCH v2 0/7] dax: I/O path enhancements Ross Zwisler
2015-08-13 16:51 ` [PATCH v2 6/7] dax: update I/O path to do proper PMEM flushing Ross Zwisler
2015-08-13 21:11 ` Dan Williams
2015-08-14 16:48 ` Ross Zwisler
2015-08-13 16:51 ` [PATCH v2 7/7] pmem, dax: have direct_access use __pmem annotation Ross Zwisler
2015-08-13 21:20 ` Dan Williams
2015-08-14 16:55 ` Ross Zwisler [this message]
2015-08-14 16:58 ` Dan Williams
2015-08-15 9:11 ` Christoph Hellwig
2015-08-15 15:49 ` Dan Williams
2015-08-15 9:19 ` Christoph Hellwig
2015-08-15 15:44 ` Dan Williams
2015-08-15 16:00 ` Christoph Hellwig
2015-08-15 18:05 ` Dan Williams
2015-08-17 20:07 ` Ross Zwisler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1439571318.16263.3.camel@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=benh@kernel.crashing.org \
--cc=boaz@plexistor.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jack@suse.cz \
--cc=jlayton@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux390@de.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=mszeredi@suse.cz \
--cc=osandov@osandov.com \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.com \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).