From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: enable x2apic early at the first point
Date: Sun, 22 Feb 2009 18:21:23 +0100 [thread overview]
Message-ID: <20090222172123.GE6570@elte.hu> (raw)
In-Reply-To: <1235255001.14523.76.camel@vayu>
* Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> On Fri, 2009-02-20 at 01:55 -0800, Ingo Molnar wrote:
> > * Ingo Molnar <mingo@elte.hu> wrote:
> >
> > > > arch/x86/kernel/apic/apic.c | 3 +--
> > > > arch/x86/kernel/apic/x2apic_cluster.c | 5 ++++-
> > > > arch/x86/kernel/apic/x2apic_phys.c | 5 ++++-
> > > > arch/x86/kernel/apic/x2apic_uv_x.c | 4 +++-
> > > > drivers/pci/dmar.c | 3 ++-
> > > > 5 files changed, 14 insertions(+), 6 deletions(-)
> > >
> > > I've applied it because it fixes a real bug, but this code
> > > really needs a cleanup. Look at the repeat patterns:
> >
> > unapplied it again as it breaks the build:
> >
> > arch/x86/kernel/apic/x2apic_cluster.c: In function 'x2apic_acpi_madt_oem_check':
> > arch/x86/kernel/apic/x2apic_cluster.c:17: error: 'disable_x2apic' undeclared (first use in this function)
> > arch/x86/kernel/apic/x2apic_cluster.c:17: error: (Each undeclared identifier is reported only once
> > arch/x86/kernel/apic/x2apic_cluster.c:17: error: for each function it appears in.)
> >
> > so please resend the fixed and cleaned up version.
>
> From: Suresh Siddha <suresh.b.siddha@intel.com>
> Subject: x86: select x2apic ops in early apic probe only if x2apic mode is enabled
Applied to tip:x86/apic, thanks Suresh!
Ingo
prev parent reply other threads:[~2009-02-22 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 21:50 [PATCH] x86: enable x2apic early at the first point Yinghai Lu
2009-02-19 22:13 ` Suresh Siddha
2009-02-19 22:42 ` Yinghai Lu
2009-02-19 23:28 ` Suresh Siddha
2009-02-20 8:35 ` Ingo Molnar
2009-02-20 9:09 ` Gleb Natapov
2009-02-20 9:41 ` Ingo Molnar
2009-02-20 10:58 ` Gleb Natapov
2009-02-20 11:06 ` Ingo Molnar
2009-02-20 11:06 ` Gleb Natapov
2009-02-20 12:33 ` Gleb Natapov
2009-02-20 12:59 ` Ingo Molnar
2009-02-20 9:51 ` Ingo Molnar
2009-02-20 9:55 ` Ingo Molnar
2009-02-21 22:23 ` Suresh Siddha
2009-02-21 22:43 ` Yinghai Lu
2009-02-21 23:33 ` Suresh Siddha
2009-02-22 17:21 ` Ingo Molnar [this message]
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=20090222172123.GE6570@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.