From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Re-enable IO-APIC for non-SMP X86_32
Date: Thu, 22 Jan 2015 22:52:05 +0000 [thread overview]
Message-ID: <54C17F15.1070404@nexus-software.ie> (raw)
In-Reply-To: <alpine.DEB.2.11.1501222230180.5526@nanos>
On 22/01/15 21:42, Thomas Gleixner wrote:
> config X86_UP_APIC
> bool "Local APIC support on uniprocessors"
> - depends on X86_32 && !SMP && !X86_32_NON_STANDARD && !PCI_MSI
> + depends on X86_32 && !SMP && !X86_32_NON_STANDARD
> ---help---
> A local APIC (Advanced Programmable Interrupt Controller) is an
> integrated interrupt controller in the CPU. If you have a single-CPU
> @@ -872,6 +872,10 @@ config X86_UP_APIC
> performance counters), and the NMI watchdog which detects hard
> lockups.
>
> +config X86_UP_APIC_MSI
> + def_bool y
> + select X86_UP_APIC if X86_32 && !SMP && !X86_32_NON_STANDARD && PCI_MSI
> +
> config X86_UP_IOAPIC
> bool "IO-APIC support on uniprocessors"
> depends on X86_UP_APIC
OK.
That works.
You can select local apic and/or io-apic on X86_32 individually with
PCI_MSI swiched off.
If you switch on PCI_MSI the option for X86_UP_APIC_MSI disappears from
and is silently selected by X86_UP_APIC_MSI.
next prev parent reply other threads:[~2015-01-22 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 20:53 [PATCH] x86: Re-enable IO-APIC for non-SMP X86_32 Bryan O'Donoghue
2015-01-22 21:42 ` Thomas Gleixner
2015-01-22 22:52 ` Bryan O'Donoghue [this message]
2015-01-22 21:42 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2015-01-22 22:58 Bryan O'Donoghue
2015-01-29 15:19 ` Ong, Boon Leong
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=54C17F15.1070404@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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