From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [git-pull -tip] x86: mpparse cleanup
Date: Wed, 18 Mar 2009 20:02:57 +0100 [thread overview]
Message-ID: <20090318190257.GB16286@elte.hu> (raw)
In-Reply-To: <1237396487.22438.2.camel@ht.satnam>
* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> On Wed, 2009-03-18 at 17:39 +0100, Ingo Molnar wrote:
> > * Ingo Molnar <mingo@elte.hu> wrote:
> >
> > > > 1 files changed, 120 insertions(+), 141 deletions(-)
> > >
> > > Looks good - pulled, thanks Jaswinder!
> > >
> > > Would you be interested in resurrecting the more mechanic cleanups
> > > you did as well, on top of this patch?
> > >
> > > They are still valuable, we just have to keep them separate from a
> > > potential breakage-causing change like the above one, so that if a
> > > tester bisects to it, we have an as single-purpose and focused
> > > commit to look at as possible.
> >
> > So it's helpful to have a small commit when we have a regression.
> >
> > Such as in this case - a -tip testbox crashed with:
> >
> > weird, boot CPU (#0) not listed by the BIOS.
> > Kernel panic - not syncing: Boot APIC ID in local APIC unexpected (0 vs 4)
> > Pid: 1, comm: swapper Not tainted
> > 2.6.29-rc8-tip-02595-g170ae27-dirty #21111
> > Call Trace:
> > [<c0599964>] ? printk+0x14/0x18
> > [<c05998a6>] panic+0x3e/0xe8
> > [<c08fc9e4>] native_smp_prepare_cpus+0x13e/0x1f8
> > [<c08f335a>] kernel_init+0x47/0xd8
> > [<c08f3313>] ? kernel_init+0x0/0xd8
> > [<c0103ea3>] kernel_thread_helper+0x7/0x10
> >
> > config and full crashlog attached.
> >
>
> As I told you earlier, I cannot check this on my side. Only
> suspect will be check_irq_src() please test this patch if this
> does not work I will revert check_irq_src():
no need to test on your side. If a patch is broken the first step is
to take a look at the patch and think about it. For example this
block:
case MP_PROCESSOR:
- {
- struct mpc_cpu *m = (struct mpc_cpu *)mpt;
- /* ACPI may have already provided this data */
- if (!acpi_lapic)
- MP_processor_info(m);
- mpt += sizeof(*m);
- count += sizeof(*m);
- break;
- }
+ /* ACPI may have already provided this data */
+ if (!acpi_lapic)
+ MP_processor_info((struct mpc_cpu *)&mpt);
+ skip_entry(&mpt, &count, sizeof(struct mpc_cpu));
+ break;
is buggy.
Ingo
next prev parent reply other threads:[~2009-03-18 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 18:33 Jaswinder Singh Rajput
2009-03-17 18:53 ` Thomas Gleixner
2009-03-18 12:45 ` Jaswinder Singh Rajput
2009-03-18 14:11 ` Ingo Molnar
2009-03-18 16:05 ` Jaswinder Singh Rajput
2009-03-18 16:18 ` Ingo Molnar
2009-03-18 16:39 ` Ingo Molnar
2009-03-18 17:14 ` Jaswinder Singh Rajput
2009-03-18 19:02 ` Ingo Molnar [this message]
2009-03-18 19:11 ` Jaswinder Singh Rajput
2009-03-18 21:57 ` Thomas Gleixner
2009-03-19 8:23 ` Ingo Molnar
2009-03-19 8:21 ` [tip:x86/cleanups] x86: mpparse: clean up code by introducing a few helper functions, fix Ingo Molnar
2009-03-20 8:02 ` [git-pull -tip] x86: mpparse cleanup Jaswinder Singh Rajput
2009-03-20 12:05 ` Jaswinder Singh Rajput
2009-03-20 18:43 ` Ingo Molnar
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=20090318190257.GB16286@elte.hu \
--to=mingo@elte.hu \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®