public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Robert Hancock <hancockr@shaw.ca>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>,
	Ingo Molnar <mingo@elte.hu>,
	Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: [PATCH] x86: Document the hotplug code is incompatible with x86 irq handling
Date: Fri, 01 Jun 2007 13:48:29 -0600	[thread overview]
Message-ID: <m1d50fzcaa.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200705312212.34053.rjw@sisk.pl> (Rafael J. Wysocki's message of "Thu, 31 May 2007 22:12:33 +0200")

"Rafael J. Wysocki" <rjw@sisk.pl> writes:
>> Cool.
>> 
>> My patch does not change the functionality of the code just complains
>> very loudly that it is broken.
>> 
>> Further the code is broken at a design level.  The code isn't
>> problematic the code is impossible.  The cpu hotplug code can not be
>> fixed on x86 without a redesign of the generic cpu hotplug code.
>> 
>> Suspend does not need to use cpu hotplug because it already gets in
>> deep with the drivers, and can stop interrupts at the source.  I know
>> there was some talk about this doing this earlier, but I don't know if
>> anything came of that discussion.
>> 
>> Regardless if you care about this being a problem feel free to fix the
>> relevant code so it attempts to do something that the hardware
>> actually supports.
>> 
>> But if the suspend needs this code for smp support it is also broken.
>
> Well, from the functionality point of view, it's not.  We have no problems
> with it, at least not that I know of.

Luck, or enough other issues someone hasn't tracked their problems
down to this.  On the pure cpu hotplug path I just got a bug
report about it not working:  http://lkml.org/lkml/2007/5/31/419

So apparently real people can hit this one.  Not just theoretical
people seen by code reviewers.

The code is broken by design and cannot be made to support existing
x86 SMP systems.  Please find a way to use something that works.

The suspend path is already talking to the drivers and can stop IRQs
at their source so it should not be a big deal.

Eric

  reply	other threads:[~2007-06-01 19:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.tUMR7tAB+jMgtfyl/LJ7U9QMgBs@ifi.uio.no>
2007-05-31 14:34 ` [PATCH] x86: Document the hotplug code is incompatible with x86 irq handling Robert Hancock
2007-05-31 15:47   ` Eric W. Biederman
2007-05-31 20:12     ` Rafael J. Wysocki
2007-06-01 19:48       ` Eric W. Biederman [this message]
2007-06-01 20:06         ` Rafael J. Wysocki
2007-06-01 20:29           ` Eric W. Biederman
2007-06-01 20:44             ` Rafael J. Wysocki
2007-06-01 20:34         ` Rafael J. Wysocki
2007-05-31 13:32 Eric W. Biederman
2007-06-07 14:01 ` Pavel Machek
2007-06-12 18:19   ` Eric W. Biederman
2007-06-12 20:52     ` Rafael J. Wysocki
2007-06-12 21:56       ` Siddha, Suresh B
2007-06-12 22:16         ` Rafael J. Wysocki
2007-06-12 22:24           ` Siddha, Suresh B
2007-06-12 22:58             ` Rafael J. Wysocki
2007-06-22 17:27               ` Eric W. Biederman

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=m1d50fzcaa.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=neilb@suse.de \
    --cc=rjw@sisk.pl \
    --cc=zwane@linuxpower.ca \
    /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