mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: rusty@rustycorp.com.au, vatsa@in.ibm.com, zwane@arm.linux.org.uk,
	"kernel list" <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	tglx@linutronix.de
Subject: Re: highres timers break cpu hotplug in 2.6.23-rc5 [was Re: cpu hotplug support broken in 2.6.23-rc3]
Date: Mon, 3 Sep 2007 20:34:09 +0800	[thread overview]
Message-ID: <b6a2187b0709030534t6589772ahb1f8e45490a7b00d@mail.gmail.com> (raw)
In-Reply-To: <20070903035644.GC3655@ucw.cz>

On 9/3/07, Pavel Machek <pavel@ucw.cz> wrote:

> It gets weirder. With "nohz=off" on commandline, I have to press any
> key (generate interrupt?) for echo 1  > online to finish. 2.6.23-rc5
> kernel... but hotplug/unplug works reliably now.
>
> With nohz=off highres=off I can unplug/replug cpus as much as I
> want... running in tight loop now.

Yes. CONFIG_NO_HZ and and CONFIG_HIGH_RES_TIMERS has to be unset or
suspend-to-disk would just hang, unless you type something on the
keyboard, and then you can suspend to disk. It seems interrupts are
not missing.

Thanks,
Jeff.

  reply	other threads:[~2007-09-03 12:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27 10:43 cpu hotplug support broken in 2.6.23-rc3 Pavel Machek
2007-08-27 10:58 ` Pavel Machek
2007-08-27 14:36   ` Jeff Chua
2007-08-27 15:22     ` Michal Piotrowski
2007-08-27 21:32     ` Pavel Machek
2007-08-27 21:59       ` Rafael J. Wysocki
2007-08-27 21:58         ` Pavel Machek
2007-08-28 10:30           ` Rafael J. Wysocki
2007-08-28 13:00             ` Akinobu Mita
2007-08-28 14:21       ` Jeff Chua
2007-09-03  3:47         ` Pavel Machek
2007-09-03 10:19           ` Rafael J. Wysocki
2007-09-03 12:35             ` Thomas Gleixner
2007-09-04  7:27               ` Pavel Machek
2007-09-13 20:01                 ` Thomas Gleixner
2007-09-14 12:38                   ` Pavel Machek
2007-09-14 12:50                     ` Thomas Gleixner
2007-09-14 13:15                       ` Thomas Gleixner
2007-09-15  9:49                         ` Thomas Gleixner
2007-09-15 10:18                           ` Andrew Morton
2007-09-15 13:28                             ` Thomas Gleixner
2007-09-15 22:01                               ` Andrew Morton
2007-09-15 13:44                             ` Thomas Gleixner
2007-10-02  9:45                           ` Pavel Machek
2007-09-14 18:49                       ` Pallipadi, Venkatesh
2007-09-14 19:18                         ` Thomas Gleixner
2007-09-03  3:56         ` highres timers break cpu hotplug in 2.6.23-rc5 [was Re: cpu hotplug support broken in 2.6.23-rc3] Pavel Machek
2007-09-03 12:34           ` Jeff Chua [this message]
2007-08-29  8:08 ` cpu hotplug support broken in 2.6.23-rc3 Gautham R Shenoy
2007-09-03  3:58   ` Pavel Machek
2007-11-15 22:37     ` cpu hotplug strangeness in 2.6.24-rc2 (was Re: cpu hotplug support broken in 2.6.23-rc3) Pavel Machek

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=b6a2187b0709030534t6589772ahb1f8e45490a7b00d@mail.gmail.com \
    --to=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=rusty@rustycorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=vatsa@in.ibm.com \
    --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

all inboxes | Powered by JetHome®