From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: Fw: [PATCH 01/01] arm: fix a preempt_count() corruption for CONFIG_PREEMPT=n
Date: Wed, 02 Jan 2013 16:41:00 -0800 [thread overview]
Message-ID: <50E4D39C.1030001@codeaurora.org> (raw)
In-Reply-To: <20121219000139.GV14363@n2100.arm.linux.org.uk>
On 12/18/12 16:01, Russell King - ARM Linux wrote:
> On Tue, Dec 18, 2012 at 03:54:12PM -0800, Stephen Boyd wrote:
>> Can you try this patch? I'll probably send a follow up patch that
>> consolidates the duplicated preempt_decrement code into some assembly
>> macro. We may also want to fix it up so that assembly stubs call into
>> the preempt tracer. I'm not sure how that works right now with VFP.
> This looks like a sensible fix to me - once tested of course.
Kluba, did the patch work for you?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-01-03 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 7:51 Fw: [PATCH 01/01] arm: fix a preempt_count() corruption for CONFIG_PREEMPT=n Patrik, Kluba
2012-12-18 23:54 ` Stephen Boyd
2012-12-19 0:01 ` Russell King - ARM Linux
2013-01-03 0:41 ` Stephen Boyd [this message]
2013-01-04 7:48 ` Patrik, Kluba
2013-01-04 22:21 ` Stephen Boyd
2013-01-08 11:51 ` Patrik, Kluba
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=50E4D39C.1030001@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).