mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Andrew Morton <akpm@osdl.org>, Anton Blanchard <anton@samba.org>,
	Paul Mackerras <paulus@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc64-dev@ozlabs.org,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PPC64] Tweaks to ppc64 cpu sysfs information
Date: Mon, 29 Nov 2004 08:58:11 +1100	[thread overview]
Message-ID: <1101679091.25347.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20041126035959.GK11370@zax>

On Fri, 2004-11-26 at 14:59 +1100, David Gibson wrote:
> Andrew, please apply:
> 
> Currently the ppc64 sysfs code registers an entry for each possible
> cpu in sysfs, rather than just online cpus.  That makes sense, since
> the sysfs entries are needed to control onlining of the cpus.
> However, this is done even if CONFIG_HOTPLUG_CPU is not set, or if it
> is not a hotplug capable (DLPAR) machine, which is a bit misleading.
> Secondly it also registers all the other sysfs entries (mostly
> performance monitoring controls) on all possible cpus, although they
> are quite meaningless on non-online cpus.

Surely if !CONFIG_HOTPLUG_CPU, then online == possible?  If not, it
should be.  That would solve part of the problem.

Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman


  reply	other threads:[~2004-11-28 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-26  3:59 David Gibson
2004-11-28 21:58 ` Rusty Russell [this message]
2004-11-29  0:50   ` David Gibson

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=1101679091.25347.9.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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®