public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Nathan Lynch <nathanl@austin.ibm.com>
Subject: Re: [PATCH] Run softirqs on proper processor on offline
Date: Wed, 16 Feb 2005 06:34:30 +0100	[thread overview]
Message-ID: <20050216053430.GA16766@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.61.0502152227090.26742@montezuma.fsmlabs.com>


* Zwane Mwaikambo <zwane@arm.linux.org.uk> wrote:

> Ensure that we only offline the processor when it's safe and never run 
> softirqs in another processor's ksoftirqd context. This also gets rid of 
> the warnings in ksoftirqd on cpu offline.
> 
> Signed-off-by: Zwane Mwaikambo <zwane@arm.linux.org.uk>

looks good.

Acked-by: Ingo Molnar <mingo@elte.hu>

	Ingo

  reply	other threads:[~2005-02-16  5:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 23:28 2.6-bk: cpu hotplug + preempt = smp_processor_id warnings galore Nathan Lynch
2005-02-11 23:56 ` Matthias-Christian Ott
2005-02-12  0:56   ` Nathan Lynch
2005-02-12 18:59 ` Zwane Mwaikambo
2005-02-14 21:59   ` Nathan Lynch
2005-02-15  7:02     ` Ingo Molnar
2005-02-16  2:06       ` [PATCH] kthread_bind new worker threads when onlining cpu Nathan Lynch
2005-02-16  5:31         ` [PATCH] Run softirqs on proper processor on offline Zwane Mwaikambo
2005-02-16  5:34           ` Ingo Molnar [this message]
2005-02-16  5:51           ` Andrew Morton
2005-02-16  6:17             ` Zwane Mwaikambo
2005-02-15 15:29     ` 2.6-bk: cpu hotplug + preempt = smp_processor_id warnings galore Zwane Mwaikambo
2005-02-15 17:26       ` Nathan Lynch

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=20050216053430.GA16766@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathanl@austin.ibm.com \
    --cc=rusty@rustcorp.com.au \
    --cc=zwane@arm.linux.org.uk \
    /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