From: Max Filippov <jcmvbkbc@gmail.com>
To: linux-xtensa@linux-xtensa.org
Cc: Chris Zankel <chris@zankel.net>, Marc Gauthier <marc@cadence.com>,
linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>,
Steven Hill <Steven.Hill@imgtec.com>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [PATCH v3 0/2] mm/highmem: make kmap cache coloring aware
Date: Fri, 25 Jul 2014 23:43:45 +0400 [thread overview]
Message-ID: <1406317427-10215-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Hi,
this series adds mapping color control to the generic kmap code, allowing
architectures with aliasing VIPT cache to use high memory. There's also
use example of this new interface by xtensa.
Max Filippov (2):
mm/highmem: make kmap cache coloring aware
xtensa: support aliasing cache in kmap
arch/xtensa/include/asm/highmem.h | 40 +++++++++++++++++-
arch/xtensa/mm/highmem.c | 18 ++++++++
mm/highmem.c | 89 ++++++++++++++++++++++++++++++++++-----
3 files changed, 134 insertions(+), 13 deletions(-)
--
1.8.1.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-07-25 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 19:43 Max Filippov [this message]
2014-07-25 19:43 ` [PATCH v3 1/2] mm/highmem: make kmap cache coloring aware Max Filippov
2014-08-01 13:37 ` Max Filippov
2014-08-01 20:10 ` Andrew Morton
2014-08-01 20:24 ` Max Filippov
2014-07-25 19:43 ` [PATCH v3 2/2] xtensa: support aliasing cache in kmap Max Filippov
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=1406317427-10215-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=marc@cadence.com \
--cc=rientjes@google.com \
/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).