From: Will Deacon <will.deacon@arm.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: cpandya@codeaurora.org, toshi.kani@hpe.com, tglx@linutronix.de,
mhocko@suse.com, akpm@linux-foundation.org,
sean.j.christopherson@intel.com,
Will Deacon <will.deacon@arm.com>
Subject: [PATCH v2 0/5] Clean up huge vmap and ioremap code
Date: Tue, 2 Oct 2018 12:05:58 +0100 [thread overview]
Message-ID: <1538478363-16255-1-git-send-email-will.deacon@arm.com> (raw)
Hi all,
This is version two of the patches I previously posted here:
http://lkml.kernel.org/r/1536747974-25875-1-git-send-email-will.deacon@arm.com
Changes since v1 include:
* Fixed increment of the physical address around the mapping loops
* Added Reviewed-by tags from Toshi
All feedback welcome,
Will
--->8
Will Deacon (5):
ioremap: Rework pXd_free_pYd_page() API
arm64: mmu: Drop pXd_present() checks from pXd_free_pYd_table()
x86: pgtable: Drop pXd_none() checks from pXd_free_pYd_table()
lib/ioremap: Ensure phys_addr actually corresponds to a physical
address
lib/ioremap: Ensure break-before-make is used for huge p4d mappings
arch/arm64/mm/mmu.c | 13 +++---
arch/x86/mm/pgtable.c | 14 +++---
include/asm-generic/pgtable.h | 5 ++
lib/ioremap.c | 103 +++++++++++++++++++++++++++++-------------
4 files changed, 91 insertions(+), 44 deletions(-)
--
2.1.4
next reply other threads:[~2018-10-02 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 11:05 Will Deacon [this message]
2018-10-02 11:05 ` [PATCH v2 1/5] ioremap: Rework pXd_free_pYd_page() API Will Deacon
2018-10-02 11:06 ` [PATCH v2 2/5] arm64: mmu: Drop pXd_present() checks from pXd_free_pYd_table() Will Deacon
2018-10-02 11:06 ` [PATCH v2 3/5] x86: pgtable: Drop pXd_none() " Will Deacon
2018-10-02 11:30 ` Thomas Gleixner
2018-10-02 11:06 ` [PATCH v2 4/5] lib/ioremap: Ensure phys_addr actually corresponds to a physical address Will Deacon
2018-10-02 11:06 ` [PATCH v2 5/5] lib/ioremap: Ensure break-before-make is used for huge p4d mappings Will Deacon
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=1538478363-16255-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=akpm@linux-foundation.org \
--cc=cpandya@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hpe.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).