public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Schopp <jschopp@austin.ibm.com>
To: hagar <hagar@iinet.net.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	Nathan Lynch <nathanl@austin.ibm.com>,
	Ashok Raj <ashok.raj@intel.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: Fwd: Kernel Power management ?? turning off used devices that are in use.
Date: Fri, 04 Nov 2011 10:24:48 -0500	[thread overview]
Message-ID: <4EB403C0.3040803@austin.ibm.com> (raw)
In-Reply-To: <4EB38A44.5030606@iinet.net.au>


> I need to be able to either switch off cpu hotpluging - or at least 
> prevent hotplugging certain cpu's
>
> there should really be a mincpu's option or better a 
> nohotplug="0,1,2,5,7,etc" option.
>
> It would appear that cpu1 is the default cpu for those interrupts - 
> and they are not being transferred to cpu0 properly.
>
The proper way to fix this is to find why the interrupts are not being 
transferred and fix that.  Forcing cpus to not be hotpluggable is just 
hiding the problem.

> I have tried the kernel parameters noapic nosmp maxcpus acpi=off 
> possible_cpus=2 etc - with no success
>
> I did find a flaw in "possible_cpus=0" - this prevents the kernel 
> booting (no cpus available )
> This option should be set to a minimum of 1
>
We allow users to shoot themselves in the foot if they do silly things.  
This is a design decision.


  parent reply	other threads:[~2011-11-04 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25  8:37 Kernel Power management ?? turning off used devices that are in use hagar
     [not found] ` <4EB38A44.5030606@iinet.net.au>
2011-11-04  6:56   ` Fwd: " hagar
2011-11-07 17:04     ` Matthew Garrett
2011-11-04 15:24   ` Joel Schopp [this message]
2011-11-05  0:07     ` hagar

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=4EB403C0.3040803@austin.ibm.com \
    --to=jschopp@austin.ibm.com \
    --cc=ashok.raj@intel.com \
    --cc=hagar@iinet.net.au \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathanl@austin.ibm.com \
    --cc=rusty@rustcorp.com.au \
    --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