public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
	Bob Liu <lliubbo@gmail.com>
Subject: [GIT PULL] percpu fixes for 3.2-rc3
Date: Mon, 28 Nov 2011 13:35:17 -0800	[thread overview]
Message-ID: <20111128213517.GB3858@google.com> (raw)

Hello, Linus.

Each percpu chunk contains units for each CPU which can be offset by
arbitrary amount (usually determined by how early mem gets allocated
for static percpu areas).

Way back, the offsets were always monotonically increasing and
first/last units were assumed to have the lowest and highest offsets.
These were used to determine cache flush ranges and map percpu to
physical addresses.

However, with embedded first chunk allocation, the assumption is no
longer true.  There's no relation between unit number and its offset,
which broke percpu -> physical translation.  The bug is rather serious
as it has remote chance of causing extremely obscure and difficult to
reproduce problems on archs which require vmalloc area flushing.

This pull includes fix for the above problem, a patch explaining why
phys addr translation is done the way it's done, and a trivial percpu
internal function rename patch which was sitting in my queue for too
long.

Please pull from the following git branch,

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-3.2-fixes

Bob Liu (1):
      percpu: rename pcpu_mem_alloc to pcpu_mem_zalloc

Dave Young (1):
      percpu: explain why per_cpu_ptr_to_phys() is more complicated than necessary

Tejun Heo (1):
      percpu: fix chunk range calculation

 mm/percpu-vm.c |   17 +++++++--------
 mm/percpu.c    |   62 ++++++++++++++++++++++++++++++++++++-------------------
 2 files changed, 48 insertions(+), 31 deletions(-)

Thanks.

--
tejun

                 reply	other threads:[~2011-11-28 21:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111128213517.GB3858@google.com \
    --to=tj@kernel.org \
    --cc=dyoung@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lliubbo@gmail.com \
    --cc=torvalds@linux-foundation.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