All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryce Harrington <bryce@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
	vatsa@in.ibm.com, torvalds@osdl.org,
	linux-kernel@vger.kernel.org, shaohua.li@intel.com,
	hotplug_sig@osdl.org, lhcs-devel@lists.sourceforge.net
Subject: Re: Status on CPU hotplug issues
Date: Sat, 7 Oct 2006 13:25:21 -0700	[thread overview]
Message-ID: <20061007202521.GA24743@osdl.org> (raw)
In-Reply-To: <20061007102419.GB30034@elf.ucw.cz>

On Sat, Oct 07, 2006 at 12:24:19PM +0200, Pavel Machek wrote:
> > > > How well tested is this?  From my reading, this will cause
> > > > enable_nonboot_cpus() to panic.  Is that intended?
> > > 
> > > I wanted to give you an update on results of cpu testing I've done on
> > > recent kernels and several architectures.  Since -rc1 is out, I wanted
> > > to give added visibility to the few issues that remain.
> > > 
> > > The full results are available here:
> > > 
> > >     http://crucible.osdl.org/runs/hotplug_report.html
> > > 
> > > This is actually a report for cpu hotplug tests generated hourly,
> > > however we run it against all of the kernel -git snapshots posted to
> > > kernel.org.  Whereever you see a blank square, it indicates the kernel
> > > either failed to build or boot.
> 
> So... patch-2.6.18-git4 failed to boot on all architectures? I'm
> seeing very little green fields there... actually I only see two green
> fields in whole table.

No, it failed to build due to a patching issue that has since been fixed
(I can rerun those older runs if there is interest.)

> (And it would be nice to call ia64 "ia64", not "ita64" :-)

Done

> > Can you describe the nature of the cpu-hotplug tests you're running?  I'd
> > be fairly staggered if the kernel was able to survive a full-on cpu-hotplug
> > stress test for more than one second, frankly.  There's a lot of code in
> > there which is non-hotplug-aware.  Running a non-preemptible kernel would
> > make things appear more stable, perhaps.
> > 
> > iirc Pavel did some testing a month or two ago and was seeing userspace
> > misbehaviour?
> 
> Pavel did some testing (like two threads trying to plug/unplug cpus at
> the same time), and seen machines dying real fast; but that was fixed,
> IIRC, and I did not really torture it after that.

If this test is available, I could include it in my test runs if you
think it would be worth tracking.

Bryce

  reply	other threads:[~2006-10-07 20:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16 17:44 [PATCH] Check for online cpus before bringing them up Srivatsa Vaddagiri
2006-03-17  1:08 ` Andrew Morton
2006-03-17  1:16   ` Shaohua Li
2006-03-17  8:46   ` Srivatsa Vaddagiri
2006-03-17  9:04     ` Andrew Morton
2006-03-17 14:13       ` Srivatsa Vaddagiri
2006-03-18 14:09         ` Ashok Raj
2006-03-21  1:08           ` Shaohua Li
2006-03-21  1:25             ` Ashok Raj
2006-03-21  1:36               ` Shaohua Li
2006-10-06 23:10       ` Status on CPU hotplug issues Bryce Harrington
2006-10-06 23:29         ` Andrew Morton
2006-10-07  0:00           ` Bryce Harrington
2006-10-07 10:35             ` Pavel Machek
2006-10-07 20:42               ` Bryce Harrington
2006-10-08 18:29                 ` Heiko Carstens
2006-10-08 19:14                   ` Pavel Machek
2006-10-11  1:08                     ` [BUG] 2.6.19-rc1-mm1: fs/file.c138 on ia64 Bryce Harrington
2006-10-11  1:15                       ` Andrew Morton
2006-10-11  5:38                         ` Bryce Harrington
2006-10-07 10:24           ` Status on CPU hotplug issues Pavel Machek
2006-10-07 20:25             ` Bryce Harrington [this message]
2006-10-08 19:13               ` Pavel Machek
2006-10-09  7:42                 ` Bryce Harrington
2006-10-07 21:57         ` Pavel Machek
2006-10-09 21:40           ` Randy Dunlap
2006-10-23 22:26             ` Bryce Harrington
2006-11-08  5:35               ` Randy Dunlap
2006-11-08  5:52                 ` Bryce Harrington
2006-03-17 12:21     ` [PATCH] Check for online cpus before bringing them up Ashok Raj
2006-03-17 13:59       ` Srivatsa Vaddagiri

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=20061007202521.GA24743@osdl.org \
    --to=bryce@osdl.org \
    --cc=akpm@osdl.org \
    --cc=hotplug_sig@osdl.org \
    --cc=lhcs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shaohua.li@intel.com \
    --cc=torvalds@osdl.org \
    --cc=vatsa@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.