public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [lhcs-devel] Re: [RFC] don't create cpu/online sysfs file
Date: Wed, 09 Jun 2004 07:10:36 +0000	[thread overview]
Message-ID: <20040609001036.7fae44fb.akpm@osdl.org> (raw)
In-Reply-To: <1086390257.24915.132.camel@nighthawk>

Ashok Raj <ashok.raj@intel.com> wrote:
>
> On Mon, Jun 07, 2004 at 09:41:49AM -0700, Dave Hansen wrote:
>  > On Mon, 2004-06-07 at 07:08, Ashok Raj wrote:plugging.
>  > > +		if (systemcfg->platform = PLATFORM_PSERIES_LPAR)
>  > > +			cpu->no_control=1;
>  > 
>  > That condition is also inverted.  Should read:
>  > 
>  > if (systemcfg->platform != PLATFORM_PSERIES_LPAR)
>  > 	cpu->no_control = 1;
> 
>  Good catch...I knew i mentioned untested :-)
> 
>  fixed patch attached...
> 
> ...
>  --- linux-2.6.7-rc2/arch/ppc64/kernel/sysfs.c~cpu_control_file	2004-06-06 13:12:06.467033408 -0700
>  +++ linux-2.6.7-rc2-root/arch/ppc64/kernel/sysfs.c	2004-06-07 10:12:45.999901454 -0700
>  @@ -325,6 +325,16 @@ static int __init topology_init(void)
>   #ifdef CONFIG_NUMA
>   		parent = &node_devices[cpu_to_node(cpu)];
>   #endif
>  +		/*
>  +		 * For now, we just see if the system supports making
>  +		 * the RTAS calls for CPU hotplug.  But, there may be a
>  +		 * more comprehensive way to do this for an individual
>  +		 * CPU.  For instance, the boot cpu might never be valid
>  +		 * for hotplugging.
>  +		 */
>  +		if (systemcfg->platform != PLATFORM_PSERIES_LPAR)
>  +			cpu->no_control=1;
>  +
>   		register_cpu(c, cpu, parent);
>   
>   		register_cpu_pmc(&c->sysdev);
> 

The ppc64 part doesn't compile - `cpu' is an integer.

  parent reply	other threads:[~2004-06-09  7:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 23:04 [lhcs-devel] Re: [RFC] don't create cpu/online sysfs file Dave Hansen
2004-06-04 23:17 ` Ashok Raj
2004-06-04 23:41 ` Dave Hansen
2004-06-05 14:38 ` Ashok Raj
2004-06-05 19:22 ` Dave Hansen
2004-06-06 20:27 ` Ashok Raj
2004-06-07  5:05 ` Dave Hansen
2004-06-07 14:07 ` Nathan Lynch
2004-06-07 14:08 ` Ashok Raj
2004-06-07 14:14 ` Ashok Raj
2004-06-07 16:41 ` Dave Hansen
2004-06-07 17:22 ` Ashok Raj
2004-06-07 19:25 ` Dave Hansen
2004-06-07 20:48 ` Ashok Raj
2004-06-09  7:10 ` Andrew Morton [this message]
2004-06-09 14:27 ` Ashok Raj

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=20040609001036.7fae44fb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-ia64@vger.kernel.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