From: Max Krasnyansky <maxk@qualcomm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ingo Molnar <mingo@elte.hu>, Jason Baron <jbaron@redhat.com>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [patch 1/2] add ALL_CPUS option to stop_machine_run()
Date: Mon, 03 Mar 2008 20:11:10 -0800 [thread overview]
Message-ID: <47CCCBDE.6040609@qualcomm.com> (raw)
In-Reply-To: <200803041336.56524.rusty@rustcorp.com.au>
Rusty Russell wrote:
> On Tuesday 04 March 2008 11:30:52 Max Krasnyanskiy wrote:
>> Great. I might get some time later this week to think about this some more
>> and try things out. So if you have ideas/suggestions let me know.
>
> Hmm, might be worth making stop_machine_run take a cpumask: I balked at it
> originally, but introducing a section special case crosses the line I think.
Are you talking about a mask of which CPUs to stop ?
That's essentially what I did with the cpu_isolated_map. But as Ingo and
others pointed out it's the wrong thing to do.
Or did you mean something else ?
Max
next prev parent reply other threads:[~2008-03-04 4:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 21:08 [patch 0/7] Immediate Values Mathieu Desnoyers
2008-02-02 21:08 ` [patch 1/7] Immediate Values - Architecture Independent Code Mathieu Desnoyers
2008-02-26 22:52 ` Jason Baron
2008-02-26 23:12 ` Mathieu Desnoyers
2008-02-26 23:34 ` Mathieu Desnoyers
2008-02-27 16:44 ` Jason Baron
2008-02-27 17:01 ` Jason Baron
2008-02-27 19:05 ` Mathieu Desnoyers
2008-02-28 16:33 ` [patch 1/2] add ALL_CPUS option to stop_machine_run() Jason Baron
2008-02-28 22:09 ` Max Krasnyanskiy
2008-02-28 22:14 ` Mathieu Desnoyers
2008-02-29 2:39 ` Jason Baron
2008-02-29 9:00 ` Ingo Molnar
2008-02-29 18:24 ` Max Krasnyanskiy
2008-02-29 19:15 ` Ingo Molnar
2008-02-29 19:58 ` Max Krasnyanskiy
2008-03-03 4:12 ` Rusty Russell
2008-03-04 0:30 ` Max Krasnyanskiy
2008-03-04 2:36 ` Rusty Russell
2008-03-04 4:11 ` Max Krasnyansky [this message]
2008-03-02 23:32 ` Rusty Russell
2008-02-28 16:37 ` [patch 2/2] implement immediate updating via stop_machine_run() Jason Baron
2008-02-29 13:43 ` Mathieu Desnoyers
2008-02-28 16:50 ` [patch 1/7] Immediate Values - Architecture Independent Code Jason Baron
2008-02-02 21:08 ` [patch 2/7] Immediate Values - Kconfig menu in EMBEDDED Mathieu Desnoyers
2008-02-02 21:08 ` [patch 3/7] Immediate Values - x86 Optimization Mathieu Desnoyers
2008-02-02 21:08 ` [patch 4/7] Add text_poke and sync_core to powerpc Mathieu Desnoyers
2008-02-02 21:08 ` [patch 5/7] Immediate Values - Powerpc Optimization Mathieu Desnoyers
2008-02-02 21:08 ` [patch 6/7] Immediate Values - Documentation Mathieu Desnoyers
2008-02-02 21:08 ` [patch 7/7] Scheduler Profiling - Use Immediate Values Mathieu Desnoyers
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=47CCCBDE.6040609@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome