public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Catalin Marinas <catalin.marinas@arm•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Russell King - ARM Linux <linux@arm•linux.org.uk>,
	Peter Zijlstra <peterz@infradead•org>,
	linux-next@vger•kernel.org
Subject: ARM context switch changes for -next
Date: Tue, 3 Jan 2012 18:14:18 +0000	[thread overview]
Message-ID: <20120103181418.GH22876@arm.com> (raw)

Hi Stephen,

Could you please pull the branch below into -next? I'd like to give it a
few weeks of exposure before sending an official pull request to
Russell. One of the patches introduces a scheduler hook and Peter Z
agreed with it. You may get a conflict in -next since some scheduler
files have been renamed.

Thanks.


The following changes since commit 384703b8e6cd4c8ef08512e596024e028c91c339:

  Linux 3.2-rc6 (2011-12-16 18:36:26 -0800)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux.git intr-ctxsw

Catalin Marinas (4):
      sched: Introduce the finish_arch_post_lock_switch() scheduler hook
      ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on ASID-capable CPUs
      ARM: Remove current_mm per-cpu variable
      ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on pre-ARMv6 CPUs

Will Deacon (2):
      ARM: Use TTBR1 instead of reserved context ID
      ARM: Allow ASID 0 to be allocated to tasks

 arch/arm/include/asm/mmu_context.h |  104 +++++++++++++++++++++++++++---------
 arch/arm/include/asm/system.h      |    7 ---
 arch/arm/include/asm/thread_info.h |    1 +
 arch/arm/mm/context.c              |   40 ++++++--------
 arch/arm/mm/proc-v7.S              |    9 +---
 kernel/sched.c                     |    4 ++
 6 files changed, 104 insertions(+), 61 deletions(-)

-- 
Catalin

next             reply	other threads:[~2012-01-03 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 18:14 Catalin Marinas [this message]
2012-01-03 22:56 ` ARM context switch changes for -next Stephen Rothwell
2012-01-04  9:25   ` Catalin Marinas

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=20120103181418.GH22876@arm.com \
    --to=catalin.marinas@arm$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux@arm$(echo .)linux.org.uk \
    --cc=peterz@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox