From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG: commit "ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on pre-ARMv6 CPUs" breaks armv5 with CONFIG_PREEMPT
Date: Thu, 20 Jun 2013 13:35:51 +0200 [thread overview]
Message-ID: <51C2E917.9000708@pengutronix.de> (raw)
In-Reply-To: <20130620111255.GD18536@arm.com>
On 06/20/2013 01:12 PM, Catalin Marinas wrote:
> On Thu, Jun 20, 2013 at 11:28:56AM +0100, Catalin Marinas wrote:
>> We may need to place the preempt disable/enable at a higher level in the
>> scheduler. My theory is that we have a context switch from prev to next.
>> We get preempted just before finish_arch_post_lock_switch(), so the MMU
>> hasn't been switched yet. The new switch during preemption happens to a
>> thread with the same next mm, so the scheduler no longer switch_mm() and
>> the TIF_SWITCH_MM isn't set for the new thread.
>>
>> I'll come back with another patch shortly.
>
> Here's another attempt (as before, only compile-tested):
booting kernel from /image
zImage: concatenated oftree detected
booting Linux kernel with devicetree
...dead...
Does every process have a "mm"? Even Kernel threads?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130620/26b07f5f/attachment.sig>
next prev parent reply other threads:[~2013-06-20 11:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 8:43 BUG: commit "ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on pre-ARMv6 CPUs" breaks armv5 with CONFIG_PREEMPT Marc Kleine-Budde
2013-06-20 9:25 ` Will Deacon
2013-06-20 9:51 ` Marc Kleine-Budde
2013-06-20 9:57 ` Catalin Marinas
2013-06-20 10:08 ` Marc Kleine-Budde
2013-06-20 10:14 ` Marc Kleine-Budde
2013-06-20 10:28 ` Catalin Marinas
2013-06-20 11:12 ` Catalin Marinas
2013-06-20 11:35 ` Marc Kleine-Budde [this message]
2013-06-20 11:39 ` Marc Kleine-Budde
2013-06-20 11:47 ` Marc Kleine-Budde
2013-06-20 12:48 ` Marc Kleine-Budde
2013-06-20 13:01 ` Catalin Marinas
2013-06-20 13:05 ` Marc Kleine-Budde
2013-06-21 10:28 ` Marc Kleine-Budde
2013-06-21 13:52 ` Catalin Marinas
2013-07-17 8:41 ` Marc Kleine-Budde
2013-07-17 8:51 ` Russell King - ARM Linux
2013-07-17 11:48 ` Marc Kleine-Budde
2013-07-17 19:41 ` 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=51C2E917.9000708@pengutronix.de \
--to=mkl@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).