From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "mcgrof@kernel.org" <mcgrof@kernel.org>
Cc: "toshi.kani@hp.com" <toshi.kani@hp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"bp@alien8.de" <bp@alien8.de>,
"julia.lawall@lip6.fr" <julia.lawall@lip6.fr>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>
Subject: Re: Enhancing semantics with memremap() - aliasing with memremap()
Date: Tue, 31 May 2016 23:31:54 +0000 [thread overview]
Message-ID: <1464736922.3504.85.camel@hpe.com> (raw)
In-Reply-To: <20160531172705.GJ11948@wotan.suse.de>
On Tue, 2016-05-31 at 19:27 +0200, Luis R. Rodriguez wrote:
> On Tue, May 31, 2016 at 07:25:14PM +0200, Luis R. Rodriguez wrote:
> >
> > On Tue, May 31, 2016 at 09:58:28AM -0700, Christoph Hellwig wrote:
> > >
> > > On Tue, May 24, 2016 at 04:36:42PM -0700, Luis R. Rodriguez wrote:
> > > >
> > > > Is it a good time for that now? I would hope identifying proper
> > > > aliasing uses for memremap() might be a bit easier now than for
> > > > ioremap() given its not used as widely. It may be an easier target
> > > > to also write some grammar rules for it as well.
> > >
> > > So you want an explicit opt-in flag to allow aliasing? Sounds fine to
> > > me.
> >
> > Yup! Can the default then safely already be no-aliasing then?
>
> Or if aliasing is truly not needed as often a different API, this
> maybe useful later if we pick up again module namespace stuff.
I agree that we should be able to change memremap() to fail an aliasing
request since it's a relatively new interface. ioremap() needs to start
from adding a warning message.
Thanks,
-Toshi
prev parent reply other threads:[~2016-06-01 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 23:36 Enhancing semantics with memremap() - aliasing with memremap() Luis R. Rodriguez
2016-05-31 16:58 ` Christoph Hellwig
2016-05-31 17:25 ` Luis R. Rodriguez
2016-05-31 17:25 ` Luis R. Rodriguez
2016-05-31 17:27 ` Luis R. Rodriguez
2016-05-31 23:31 ` Kani, Toshimitsu [this message]
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=1464736922.3504.85.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=toshi.kani@hp.com \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/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).