From: frank.rowand@am.sony.com (Frank Rowand)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/6] ARM: Remove the __ARCH_WANT_INTERRUPTS_ON_CTXSW definition
Date: Mon, 19 Dec 2011 17:36:55 -0800 [thread overview]
Message-ID: <4EEFE6B7.2010101@am.sony.com> (raw)
In-Reply-To: <1324306673-4282-1-git-send-email-catalin.marinas@arm.com>
On 12/19/11 06:57, Catalin Marinas wrote:
> Hi,
>
> This is version 2 of the set of patches for removing
> __ARCH_WANT_INTERRUPTS_ON_CTXSW on ARM. The series was updated to allow
> for the pgd switch not to be deferred if switch_mm() is called with
> interrupts enabled. This is required for cases where switch_mm() is
> called directly (currently from use_mm() and idle_task_exit()) without a
> corresponding finish_arch_post_lock_switch() call. The original changes
> to activate_mm() were also reverted since switch_mm() can do the actual
> pgd switch when the interrupts are enabled.
>
> If there are no objections, I'd like to push the series to -next to get
> more exposure (the patches are aimed for 3.4-rc1 unless other issues are
> found in the meantime).
Version 2 looks good to me. Thanks!
-Frank
WARNING: multiple messages have this Message-ID (diff)
From: Frank Rowand <frank.rowand@am.sony.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
"Rowand, Frank" <Frank_Rowand@sonyusa.com>
Subject: Re: [RFC PATCH v2 0/6] ARM: Remove the __ARCH_WANT_INTERRUPTS_ON_CTXSW definition
Date: Mon, 19 Dec 2011 17:36:55 -0800 [thread overview]
Message-ID: <4EEFE6B7.2010101@am.sony.com> (raw)
In-Reply-To: <1324306673-4282-1-git-send-email-catalin.marinas@arm.com>
On 12/19/11 06:57, Catalin Marinas wrote:
> Hi,
>
> This is version 2 of the set of patches for removing
> __ARCH_WANT_INTERRUPTS_ON_CTXSW on ARM. The series was updated to allow
> for the pgd switch not to be deferred if switch_mm() is called with
> interrupts enabled. This is required for cases where switch_mm() is
> called directly (currently from use_mm() and idle_task_exit()) without a
> corresponding finish_arch_post_lock_switch() call. The original changes
> to activate_mm() were also reverted since switch_mm() can do the actual
> pgd switch when the interrupts are enabled.
>
> If there are no objections, I'd like to push the series to -next to get
> more exposure (the patches are aimed for 3.4-rc1 unless other issues are
> found in the meantime).
Version 2 looks good to me. Thanks!
-Frank
next prev parent reply other threads:[~2011-12-20 1:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 14:57 [RFC PATCH v2 0/6] ARM: Remove the __ARCH_WANT_INTERRUPTS_ON_CTXSW definition Catalin Marinas
2011-12-19 14:57 ` Catalin Marinas
2011-12-19 14:57 ` [RFC PATCH v2 1/6] sched: Introduce the finish_arch_post_lock_switch() scheduler hook Catalin Marinas
2011-12-19 14:57 ` Catalin Marinas
2011-12-19 14:57 ` [RFC PATCH v2 2/6] ARM: Use TTBR1 instead of reserved context ID Catalin Marinas
2011-12-19 14:57 ` Catalin Marinas
2011-12-19 14:57 ` [RFC PATCH v2 3/6] ARM: Allow ASID 0 to be allocated to tasks Catalin Marinas
2011-12-19 14:57 ` Catalin Marinas
2011-12-19 14:57 ` [RFC PATCH v2 4/6] ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on ASID-capable CPUs Catalin Marinas
2011-12-19 14:57 ` Catalin Marinas
2011-12-19 14:57 ` [RFC PATCH v2 5/6] ARM: Remove current_mm per-cpu variable Catalin Marinas
2011-12-19 14:57 ` Catalin Marinas
2011-12-19 14:57 ` [RFC PATCH v2 6/6] ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on pre-ARMv6 CPUs Catalin Marinas
2011-12-19 14:57 ` Catalin Marinas
2011-12-20 1:36 ` Frank Rowand
2011-12-20 1:36 ` Frank Rowand
2011-12-20 1:36 ` Frank Rowand [this message]
2011-12-20 1:36 ` [RFC PATCH v2 0/6] ARM: Remove the __ARCH_WANT_INTERRUPTS_ON_CTXSW definition Frank Rowand
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=4EEFE6B7.2010101@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.