From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-arch@vger.kernel.org, mingo@elte.hu, JBeulich@novell.com,
andi@firstfloor.org, hpa@zytor.com, tglx@linutronix.de
Subject: [GIT PATCH core/percpu] x86,percpu: fix pageattr handling with remap allocator, take#4
Date: Wed, 17 Jun 2009 12:52:12 +0900 [thread overview]
Message-ID: <1245210739-25699-1-git-send-email-tj@kernel.org> (raw)
Hello,
Upon ack, please pull from the following git tree.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu-fix-remap
This is the third take of x86-percpu-fix-pageattr patchset. Changes
from the last take[L] are...
* Rebased on top of linus#master + tj-percpu-convert-most-archs, take#3
* Dup free in setup_pcpu_remap() fixed.
* remap allocator renamed to lpage.
* Changes to cpa_process_alias() updated such that the remap handling
code doesn't consider multipage case and trigger WARN_ON() if @cpa
at that point has numpages higher than 1. Because the target PMD
page is always partially recycled, it always ends up splitted to 4k
pages and thus numpages is guaranteed to be 1 at that point.
This patchset contains the following seven patches.
0001-x86-fix-duplicate-free-in-setup_pcpu_remap-failur.patch
0002-x86-rename-remap-percpu-first-chunk-allocator-to-lp.patch
0003-x86-prepare-setup_pcpu_lpage-for-pageattr-fix.patch
0004-x86-reorganize-cpa_process_alias.patch
0005-x86-fix-pageattr-handling-for-lpage-percpu-allocato.patch
0006-x86-implement-percpu_alloc-kernel-parameter.patch
0007-x86-ensure-percpu-lpage-doesn-t-consume-too-much-vm.patch
0001 and 0002 are new ones. 0005 has the cpa_process_alias() change
updated describd above. Other than that, no notable changes.
This patchset is on top of
linus-2.6#master (300df7dc89cc276377fc020704e34875d5c473b6)
+ [1] tj-percpu-convert-most-archs, take#3
and contains the following changes.
Documentation/kernel-parameters.txt | 6
arch/x86/include/asm/percpu.h | 9 +
arch/x86/kernel/setup_percpu.c | 219 ++++++++++++++++++++++++++----------
arch/x86/mm/pageattr.c | 65 ++++++----
mm/percpu.c | 13 +-
5 files changed, 226 insertions(+), 86 deletions(-)
Thanks.
--
tejun
[L] http://thread.gmane.org/gmane.linux.kernel/844298
[1] http://thread.gmane.org/gmane.linux.kernel.cross-arch/3818
next reply other threads:[~2009-06-17 3:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 3:52 Tejun Heo [this message]
2009-06-17 3:52 ` [PATCH 1/7] x86: fix duplicate free in setup_pcpu_remap() failure path Tejun Heo
2009-06-17 3:52 ` [PATCH 2/7] x86: rename remap percpu first chunk allocator to lpage Tejun Heo
2009-06-17 3:52 ` [PATCH 3/7] x86: prepare setup_pcpu_lpage() for pageattr fix Tejun Heo
2009-06-17 3:52 ` [PATCH 4/7] x86: reorganize cpa_process_alias() Tejun Heo
2009-06-17 3:52 ` [PATCH 5/7] x86: fix pageattr handling for lpage percpu allocator and re-enable it Tejun Heo
2009-06-17 3:52 ` [PATCH 6/7] x86: implement percpu_alloc kernel parameter Tejun Heo
2009-06-17 3:52 ` [PATCH 7/7] x86: ensure percpu lpage doesn't consume too much vmalloc space Tejun Heo
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=1245210739-25699-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=JBeulich@novell.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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