From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "David S. Miller" <davem@davemloft.net>
Cc: anton@samba.org, paulus@samba.org, linux-ia64@vger.kernel.org,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch] improve SMP reschedule and idle routines
Date: Mon, 16 May 2005 15:34:06 +1000 [thread overview]
Message-ID: <428830CE.6010602@yahoo.com.au> (raw)
In-Reply-To: <20050515.222722.63128129.davem@davemloft.net>
David S. Miller wrote:
> From: Nick Piggin <nickpiggin@yahoo.com.au>
> Date: Mon, 16 May 2005 15:19:00 +1000
>
>
>>The other obvious problem with sparc64 that I didn't tackle is
>>your secondary CPU bringup - those CPUs will be calling cpu_idle
>>with preempt enabled as was previously required, but now should
>>have preempt disabled (ie. arch/sparc64/kernel/trampoline.S:
>>call cpu_idle)
>
>
> And adding a preempt_disable() call to the end of
> arch/sparc64/kernel/smp.c:smp_callin() won't work
> because?
>
No that looks like it should work. If that is the "right"
place to put it, then that's perfect. I'll resend the patch
to you privately.
next prev parent reply other threads:[~2005-05-16 5:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 4:21 [patch] improve SMP reschedule and idle routines Nick Piggin
[not found] ` <20050515.220455.59467677.davem@davemloft.net>
2005-05-16 5:19 ` Nick Piggin
[not found] ` <20050515.222722.63128129.davem@davemloft.net>
2005-05-16 5:34 ` Nick Piggin [this message]
2005-05-17 7:34 ` Nick Piggin
2005-05-17 7:40 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 13:51 Oleg Nesterov
2005-05-16 22:52 ` Nick Piggin
2005-05-27 7:21 Nick Piggin
2005-05-27 8:57 ` Ingo Molnar
2005-05-27 9:11 ` Nick Piggin
2005-05-27 9:20 ` Ingo Molnar
2005-05-27 9:37 ` Nick Piggin
2005-05-27 10:12 ` Ingo Molnar
2005-06-01 6:15 ` Andrew Morton
2005-06-01 6:31 ` Nick Piggin
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=428830CE.6010602@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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