All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Is patches/linux-2.6.18/xen-hotplug.patch still necessary?
Date: Tue, 08 May 2007 16:26:05 -0600	[thread overview]
Message-ID: <1178663165.31282.18.camel@lappy> (raw)


   Is the patch below, that's currently in the Xen tree, still
necessary?  The original commit comment indicates this is so things like
'top' don't get upset during CPU hotplugs.  But should that be handled
by the hotplug infrastructure in the kernel (or top itself)?  IMHO, this
breaks top more than fixes it.  Now when I try to look at individual
processor statistics, I see quite a few lines of zeros (2 online CPUs,
16 possible CPUs).  AFAICT, this also breaks all of the NPROCESSORS
queries for sysconf.  Can we dump it?  Thanks,

	Alex


diff -pruN ../orig-linux-2.6.18/fs/proc/proc_misc.c ./fs/proc/proc_misc.c
--- ../orig-linux-2.6.18/fs/proc/proc_misc.c    2006-09-20 04:42:06.000000000 +0100
+++ ./fs/proc/proc_misc.c       2007-01-12 18:18:36.000000000 +0000
@@ -471,7 +471,7 @@ static int show_stat(struct seq_file *p,
                (unsigned long long)cputime64_to_clock_t(irq),
                (unsigned long long)cputime64_to_clock_t(softirq),
                (unsigned long long)cputime64_to_clock_t(steal));
-       for_each_online_cpu(i) {
+       for_each_possible_cpu(i) {
 
                /* Copy values here to work around gcc-2.95.3, gcc-2.96 */
                user = kstat_cpu(i).cpustat.user;


-- 
Alex Williamson                             HP Open Source & Linux Org.

             reply	other threads:[~2007-05-08 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 22:26 Alex Williamson [this message]
2007-05-09  7:05 ` Is patches/linux-2.6.18/xen-hotplug.patch still necessary? Keir Fraser
2007-05-09 13:52   ` Dave Lively
2007-05-09 15:07   ` Alex Williamson
2007-05-09 15:32     ` Keir Fraser
2007-05-09 15:38       ` Alex Williamson

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=1178663165.31282.18.camel@lappy \
    --to=alex.williamson@hp.com \
    --cc=xen-devel@lists.xensource.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.