[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4j67493ROvnC1EZBEFMiWB=gLu=C-Y-PrJf0BvO3A=y2w@mail.gmail.com>
Date: Wed, 29 Jul 2015 14:47:40 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "Luis R. Rodriguez" <mcgrof@...e.com>
Cc: Toshi Kani <toshi.kani@...com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-arch@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
"H. Peter Anvin" <hpa@...or.com>,
Russell King <rmk+kernel@....linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 08/25] arch: introduce memremap()
On Wed, Jul 29, 2015 at 2:43 PM, Luis R. Rodriguez <mcgrof@...e.com> wrote:
> While at it, Dan, will / should memremap() support overlapping calls ?
> What is the expectation on behaviour ?
It will be the same as ioremap(). Each mapping gets its own virtual
address and overlapping calls are permitted. The only protection is
that RAM is never mapped with an alias.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists