From: Max Filippov <jcmvbkbc@gmail.com>
To: linux-xtensa@linux-xtensa.org
Cc: Chris Zankel <chris@zankel.net>, Marc Gauthier <marc@cadence.com>,
linux-kernel@vger.kernel.org, Max Filippov <jcmvbkbc@gmail.com>,
linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-mips@linux-mips.org, David Rientjes <rientjes@google.com>
Subject: [PATCH 0/8] xtensa: highmem support on cores with aliasing cache
Date: Tue, 22 Jul 2014 23:01:05 +0400 [thread overview]
Message-ID: <1406055673-10100-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Hi,
this series implements highmem support on xtensa cores with aliasing cache.
It does so by making sure that high memory pages are always mapped at
virtual addresses with color that match color of their physical address.
This involves changing the generic kmap code to make it aware of cache
coloring. This part with corresponding arch changes is cc'd linux-mm,
linux-arch and linux-mips.
The whole series can also be found at:
git://github.com/jcmvbkbc/linux-xtensa.git xtensa-highmem-ca
Leonid Yegoshin (1):
mm/highmem: make kmap cache coloring aware
Max Filippov (7):
xtensa: make fixmap region addressing grow with index
xtensa: allow fixmap and kmap span more than one page table
xtensa: fix TLBTEMP_BASE_2 region handling in fast_second_level_miss
xtensa: implement clear_user_highpage and copy_user_highpage
xtensa: support aliasing cache in k[un]map_atomic
xtensa: support aliasing cache in kmap
xtensa: support highmem in aliasing cache flushing code
arch/xtensa/include/asm/cacheflush.h | 2 +
arch/xtensa/include/asm/fixmap.h | 30 +++++++--
arch/xtensa/include/asm/highmem.h | 18 +++++-
arch/xtensa/include/asm/page.h | 14 ++++-
arch/xtensa/include/asm/pgtable.h | 7 ++-
arch/xtensa/kernel/entry.S | 2 +-
arch/xtensa/mm/cache.c | 77 ++++++++++++++++++++---
arch/xtensa/mm/highmem.c | 24 +++++---
arch/xtensa/mm/misc.S | 116 ++++++++++++++++-------------------
arch/xtensa/mm/mmu.c | 38 +++++++-----
mm/highmem.c | 19 +++++-
11 files changed, 235 insertions(+), 112 deletions(-)
Cc: linux-mm@kvack.org
Cc: linux-arch@vger.kernel.org
Cc: linux-mips@linux-mips.org
Cc: David Rientjes <rientjes@google.com>
--
1.8.1.4
next reply other threads:[~2014-07-22 19:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 19:01 Max Filippov [this message]
2014-07-22 19:01 ` [PATCH 6/8] mm/highmem: make kmap cache coloring aware Max Filippov
2014-07-22 19:01 ` Max Filippov
2014-07-22 19:35 ` Leonid Yegoshin
2014-07-22 19:35 ` Leonid Yegoshin
2014-07-22 19:46 ` Max Filippov
2014-07-22 19:46 ` Max Filippov
2014-07-22 19:01 ` Max Filippov
2014-07-22 19:01 ` [PATCH 7/8] xtensa: support aliasing cache in kmap Max Filippov
2014-07-22 19:01 ` Max Filippov
2014-07-22 19:01 ` Max Filippov
-- strict thread matches above, loose matches on Subject: below --
2014-07-22 19:01 [PATCH 0/8] xtensa: highmem support on cores with aliasing cache Max Filippov
2014-07-22 19:01 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=1406055673-10100-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--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).