From: Andrew Morton <akpm@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Mike Travis <travis@sgi.com>, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@elte.hu>, David Miller <davem@davemloft.net>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] percpu: fix DEBUG_PREEMPT per_cpu checking
Date: Sat, 23 Feb 2008 12:06:10 -0800 [thread overview]
Message-ID: <20080223120610.a31dbdf4.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0802231927500.13934@blonde.site>
On Sat, 23 Feb 2008 19:40:17 +0000 (GMT) Hugh Dickins <hugh@veritas.com> wrote:
> 2.6.25-rc1 percpu changes broke CONFIG_DEBUG_PREEMPT's per_cpu checking
> on several architectures. On s390, sparc64 and x86 it's been weakened to
> not checking at all; whereas on powerpc64 it's become too strict, issuing
> warnings from __raw_get_cpu_var in io_schedule and init_timer for example.
>
> Fix this by weakening powerpc's __my_cpu_offset to use the non-checking
> local_paca instead of get_paca (which itself contains such a check);
> and strengthening the generic my_cpu_offset to go the old slow way via
> smp_processor_id when CONFIG_DEBUG_PREEMPT (debug_smp_processor_id is
> where all the knowledge of what's correct when lives).
>
> Signed-off-by: Hugh Dickins <hugh@veritas.com>
> Reviewed-by: Mike Travis <travis@sgi.com>
> ---
> I posted this a couple of weeks ago, but it seems we all expected
> someone else to forward it to you.
I merged it, but for non-critical fixes I'll tend to sit on them for a week
or so before sending them in to Linus.
This patch has now turned up in git-sched which is a considerable
inconvenience.
Ingo, please don't just merge everything which crosses your desk. I'm now
in the position that I either drop the patch and completely lose track of
it or I need to apply then revert it to make your tree apply.
Hopefully Linus will apply the patch from Hugh's email, but that isn't the
general solution to this increasingly worse problem.
next prev parent reply other threads:[~2008-02-23 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 19:40 [PATCH] percpu: fix DEBUG_PREEMPT per_cpu checking Hugh Dickins
2008-02-23 20:06 ` Andrew Morton [this message]
2008-02-23 20:09 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2008-02-08 18:23 Hugh Dickins
2008-02-11 19:37 ` Mike Travis
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=20080223120610.a31dbdf4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.com \
/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.