LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Ingo Molnar <mingo@redhat.com>,
tglx@linutronix.de, "H. Peter Anvin" <hpa@zytor.com>,
pure.logic@nexus-software.ie, jgross@suse.com,
luto@amacapital.net, andy.shevchenko@gmail.com,
thomas.petazzoni@free-electrons.com, JBeulich@suse.com,
bp@suse.de, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, x86@kernel.org,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC v1 1/2] x86: kconfig: simplify enabling [IO]APIC for PCI_MSI
Date: Tue, 10 Mar 2015 17:49:10 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1503101746450.26407@chino.kir.corp.google.com> (raw)
In-Reply-To: <1426029275-9594-2-git-send-email-mcgrof@do-not-panic.com>
On Tue, 10 Mar 2015, Luis R. Rodriguez wrote:
> diff --git a/Documentation/PCI/MSI-HOWTO.txt b/Documentation/PCI/MSI-HOWTO.txt
> index 0d920d5..7306d2c 100644
> --- a/Documentation/PCI/MSI-HOWTO.txt
> +++ b/Documentation/PCI/MSI-HOWTO.txt
> @@ -71,10 +71,7 @@ will simply fail and the device will continue to use pin-based interrupts.
> 4.1 Include kernel support for MSIs
>
> To support MSI or MSI-X, the kernel must be built with the CONFIG_PCI_MSI
> -option enabled. This option is only available on some architectures,
> -and it may depend on some other options also being set. For example,
> -on x86, you must also enable X86_UP_APIC or SMP in order to see the
> -CONFIG_PCI_MSI option.
> +option enabled. This option is only available on some architectures.
>
> 4.2 Using MSI
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index d038475..0ecdeb1 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -902,10 +902,6 @@ 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
> @@ -924,7 +920,7 @@ config X86_LOCAL_APIC
> select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
>
> config X86_IO_APIC
> - def_bool X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC
> + def_bool X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC || PCI_MSI
> depends on X86_LOCAL_APIC
> select IRQ_DOMAIN
>
> diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
> index 7a8f1c5..01370c0 100644
> --- a/drivers/pci/Kconfig
> +++ b/drivers/pci/Kconfig
> @@ -5,6 +5,8 @@ config PCI_MSI
> bool "Message Signaled Interrupts (MSI and MSI-X)"
> depends on PCI
> select GENERIC_MSI_IRQ
> + select X86_LOCAL_APIC if X86_32 && !SMP && !X86_32_NON_STANDARD
> + select X86_IO_APIC if X86_32 && !SMP && !X86_32_NON_STANDARD
> help
> This allows device drivers to enable MSI (Message Signaled
> Interrupts). Message Signaled Interrupts enable a device to
This conflicts with commit 50849eefea3b ("x86/Kconfig: Simplify
X86_UP_APIC handling"), which has already been merged for the 4.0 release
cycle, and I think I prefer the simplification done there over the
additional "select"s for PCI_MSI.
next prev parent reply other threads:[~2015-03-11 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 23:14 [RFC v1 0/2] x86: kconfig: simplify APIC entries Luis R. Rodriguez
2015-03-10 23:14 ` [RFC v1 1/2] x86: kconfig: simplify enabling [IO]APIC for PCI_MSI Luis R. Rodriguez
2015-03-11 0:49 ` David Rientjes [this message]
2015-03-11 23:03 ` Luis R. Rodriguez
2015-03-10 23:14 ` [RFC v1 2/2] x86: kconfig: remove UP [IO]APIC options Luis R. Rodriguez
2015-03-11 0:58 ` David Rientjes
2015-03-11 18:35 ` Luis R. Rodriguez
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=alpine.DEB.2.10.1503101746450.26407@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=JBeulich@suse.com \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pure.logic@nexus-software.ie \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@free-electrons.com \
--cc=x86@kernel.org \
--subject='Re: [RFC v1 1/2] x86: kconfig: simplify enabling [IO]APIC for PCI_MSI' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).