From: Toshi Kani <toshi.kani@hp.com>
To: akpm@linux-foundation.org, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com
Cc: linux-mm@kvack.org, x86@kernel.org, linux-kernel@vger.kernel.org,
dave.hansen@intel.com, Elliott@hp.com, pebolle@tiscali.nl
Subject: [PATCH v2 0/4] mtrr, mm, x86: Enhance MTRR checks for huge I/O mapping
Date: Thu, 12 Mar 2015 11:18:06 -0600 [thread overview]
Message-ID: <1426180690-24234-1-git-send-email-toshi.kani@hp.com> (raw)
This patchset enhances MTRR checks for the kernel huge I/O mapping,
which was enabled by the patchset below:
https://lkml.org/lkml/2015/3/3/589
The following functional changes are made in patch 4/4.
- Allow pud_set_huge() and pmd_set_huge() to create a huge page
mapping to a range covered by a single MTRR entry of any memory
type.
- Log a pr_warn() message when a specified PMD map range spans more
than a single MTRR entry. Drivers should make a mapping request
aligned to a single MTRR entry when the range is covered by MTRRs.
Patch 1/4 addresses other review comments to the mapping funcs for
better code read-ability. Patch 2/4 and 3/4 are bug fix and clean up
to mtrr_type_lookup().
The patchset is based on the -mm tree.
---
v2:
- Update change logs and comments per review comments.
(Ingo Molnar)
- Add patch 3/4 to clean up mtrr_type_lookup(). (Ingo Molnar)
---
Toshi Kani (4):
1/4 mm, x86: Document return values of mapping funcs
2/4 mtrr, x86: Fix MTRR lookup to handle inclusive entry
3/4 mtrr, x86: Clean up mtrr_type_lookup()
4/4 mtrr, mm, x86: Enhance MTRR checks for KVA huge page mapping
---
arch/x86/Kconfig | 2 +-
arch/x86/include/asm/mtrr.h | 5 +-
arch/x86/kernel/cpu/mtrr/generic.c | 151 +++++++++++++++++++++----------------
arch/x86/mm/pat.c | 4 +-
arch/x86/mm/pgtable.c | 53 +++++++++----
5 files changed, 133 insertions(+), 82 deletions(-)
--
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:[~2015-03-12 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 17:18 Toshi Kani [this message]
2015-03-12 17:18 ` [PATCH v2 1/4] mm, x86: Document return values of mapping funcs Toshi Kani
2015-03-12 17:18 ` [PATCH v2 2/4] mtrr, x86: Fix MTRR lookup to handle inclusive entry Toshi Kani
2015-03-12 17:18 ` [PATCH v2 3/4] mtrr, x86: Clean up mtrr_type_lookup() Toshi Kani
2015-03-13 12:37 ` Ingo Molnar
2015-03-13 13:53 ` Toshi Kani
2015-03-12 17:18 ` [PATCH v2 4/4] mtrr, mm, x86: Enhance MTRR checks for KVA huge page mapping Toshi Kani
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=1426180690-24234-1-git-send-email-toshi.kani@hp.com \
--to=toshi.kani@hp.com \
--cc=Elliott@hp.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=pebolle@tiscali.nl \
--cc=tglx@linutronix.de \
--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