From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 1/1] sparc: task_cpu() for stopper thread on sparc32 returns 0
Date: Thu, 19 Apr 2012 17:35:13 +0000 [thread overview]
Message-ID: <20120419.133513.1487729675877616836.davem@davemloft.net> (raw)
In-Reply-To: <1334827362-3434-1-git-send-email-konrad@gaisler.com>
From: Konrad Eisele <konrad@gaisler.com>
Date: Thu, 19 Apr 2012 11:22:42 +0200
> The stopper thread for CPU > 0 (at least in sparc32)
> has on initialization task_cpu() set to zero even
> for CPUs > 0. The patch explicitly checks weather the
> CPU is allowed to run on the cpu that task_cpu()
> return or changes the return cpu.
>
> Signed-off-by: Konrad Eisele <konrad@gaisler.com>
Posting a patch to generic code like this only to the Sparc
list isn't going to drive us forward to a solution and will
not involve the people who need to help you look into this
problem.
Therefore you need to post this with at least linux-kernel
and the scheduler maintainer's CC:'d.
prev parent reply other threads:[~2012-04-19 17:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 9:22 [PATCH 1/1] sparc: task_cpu() for stopper thread on sparc32 returns 0 Konrad Eisele
2012-04-19 15:34 ` Sam Ravnborg
2012-04-19 15:34 ` Sam Ravnborg
2012-04-20 3:36 ` Yong Zhang
2012-04-20 3:36 ` Yong Zhang
2012-04-20 3:56 ` David Miller
2012-04-20 3:56 ` David Miller
2012-04-20 6:28 ` [PATCH 1/1] sparc32,leon: add notify_cpu_starting() Konrad Eisele
2012-04-20 6:28 ` Konrad Eisele
2012-04-20 6:32 ` Konrad Eisele
2012-04-20 6:32 ` Konrad Eisele
2012-04-20 7:06 ` David Miller
2012-04-20 7:06 ` David Miller
2012-04-20 7:46 ` [PATCH] " Konrad Eisele
2012-04-20 7:46 ` Konrad Eisele
2012-04-20 7:47 ` Konrad Eisele
2012-04-20 7:47 ` Konrad Eisele
2012-04-20 8:01 ` Srivatsa S. Bhat
2012-04-20 8:13 ` Srivatsa S. Bhat
2012-04-19 17:35 ` David Miller [this message]
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=20120419.133513.1487729675877616836.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@vger.kernel.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.