mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Max Krasnyanskiy" <maxk@qualcomm.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, "Paul Jackson" <pj@sgi.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH sched-devel 0/7] CPU isolation extensions
Date: Fri, 22 Feb 2008 09:36:28 +0100	[thread overview]
Message-ID: <b647ffbd0802220036v383961ddq5f07efe72f525ffc@mail.gmail.com> (raw)
In-Reply-To: <47BE35B7.2070104@qualcomm.com>

Hi Max,

>  [ ... ]
>  Last patch to the stop machine is potentially unsafe and is marked as experimental. Unfortunately
>  it's currently the only option that allows dynamic module insertion/removal for above scenarios.

I'm puzzled by the following part (can be a misunderstanding from my side)

+config CPUISOL_STOPMACHINE
+       bool "Do not halt isolated CPUs with Stop Machine (EXPERIMENTAL)"
+       depends on CPUISOL && STOP_MACHINE && EXPERIMENTAL
+       help
+         If this option is enabled kernel will not halt isolated CPUs
+         when Stop Machine is triggered. Stop Machine is currently only
+         used by the module insertion and removal.

this "only" part. What about e.g. a 'cpu hotplug' case (_cpu_down())?
(or we should abstract it a bit to the point that e.g. a cpu can be
considered as 'a module'? :-)


-- 
Best regards,
Dmitry Adamushko

  reply	other threads:[~2008-02-22  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  2:38 Max Krasnyanskiy
2008-02-22  8:36 ` Dmitry Adamushko [this message]
2008-02-22 21:04   ` Max Krasnyanskiy
2008-02-22 11:43 ` Peter Zijlstra
2008-02-22 13:38   ` Mark Hounschell
2008-02-22 13:59     ` Peter Zijlstra
2008-02-22 22:22       ` Max Krasnyanskiy
2008-02-22 22:08     ` Max Krasnyanskiy
2008-02-22 22:05   ` Max Krasnyanskiy
2008-02-23 13:05     ` Peter Zijlstra
2008-02-26  2:10       ` Max Krasnyanskiy

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=b647ffbd0802220036v383961ddq5f07efe72f525ffc@mail.gmail.com \
    --to=dmitry.adamushko@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=mingo@elte.hu \
    --cc=pj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome