From: Ingo Molnar <mingo@elte.hu>
To: Robert Richter <robert.richter@amd.com>
Cc: Jan Beulich <jbeulich@novell.com>,
linux-kernel@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: patch "x86: MOVE PCI IO ECS code to x86/pci" breaks CPU hotplug
Date: Fri, 22 Aug 2008 08:05:20 +0200 [thread overview]
Message-ID: <20080822060520.GG14110@elte.hu> (raw)
In-Reply-To: <20080821131652.GC13011@erda.amd.com>
* Robert Richter <robert.richter@amd.com> wrote:
> On 21.08.08 15:02:59, Ingo Molnar wrote:
> >
> > * Jan Beulich <jbeulich@novell.com> wrote:
> >
> > > Converting __cpuinit functions called out of init_amd() (and similar
> > > others) to __init (and making them subject of xxx_initcall() handling
> > > isn't valid, as they would no longer be called for hot plugged CPUs.
> > >
> > > Further, since it's likely that in virtualized environments the MSR
> > > write would at best be ignored, I'd also recommend using the
> > > fault-safe accessors here *and* check that the bit actually got set
> > > before setting PCI_HAS_IO_ECS (one would obviously have to BUG() when
> > > hot-plugged CPUs fail to set the bit when those available at boot
> > > successfully did so).
> >
> > hm, which patch is this exactly, and in what tree? It's not upstream nor
> > in -tip.
>
> Probably this in the mainline kernel is meant:
>
> commit 3a27dd1ce5de08e21e0266ddf00e6f1f843bfe8b
> Author: Robert Richter <robert.richter@amd.com>
> Date: Thu Jun 12 20:19:23 2008 +0200
>
> x86: Move PCI IO ECS code to x86/pci
>
> "Form follows function". Code is now where it belongs to.
>
> Signed-off-by: Robert Richter <robert.richter@amd.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> The problem is code like this:
>
> +static int __init enable_pci_io_ecs(void)
> +{
> + /* assume all cpus from fam10h have IO ECS */
> + if (boot_cpu_data.x86 < 0x10)
> + return 0;
> + on_each_cpu(enable_pci_io_ecs_per_cpu, NULL, 1, 1);
> + pci_probe |= PCI_HAS_IO_ECS;
> + return 0;
> +}
>
> It is only called during the setup and if the cpu is enabled. I intend
> to rewrite the cpu setup code using cpu notifiers.
ok. Unfortunately the revert looks quite non-trivial for v2.6.27. Could
we have some _really_ minimal fix for v2.6.27?
Ingo
next prev parent reply other threads:[~2008-08-22 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 12:45 Jan Beulich
2008-08-21 13:02 ` Ingo Molnar
2008-08-21 13:16 ` Robert Richter
2008-08-22 6:05 ` Ingo Molnar [this message]
2008-08-21 13:19 ` Jan Beulich
2008-08-21 12:59 Jan Beulich
2008-08-21 13:29 ` Robert Richter
2008-08-21 16:25 ` Yinghai Lu
2008-08-21 16:46 ` Robert Richter
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=20080822060520.GG14110@elte.hu \
--to=mingo@elte.hu \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.richter@amd.com \
--cc=yhlu.kernel@gmail.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 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®