All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-pci <linux-pci@vger.kernel.org>,
	linux@arm.linux.org.uk, "tony.luck" <tony.luck@intel.com>,
	fenghua.yu@intel.com, "David S.Miller" <davem@davemloft.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	mingo@redhat.com, Peter Anvin <hpa@zytor.com>,
	linux-mips@linux-mips.org,
	David Daney <ddaney@caviumnetworks.com>
Subject: Re: Time to make PCI_MSI default y ?
Date: Wed, 25 Nov 2009 11:31:34 +1100	[thread overview]
Message-ID: <1259109094.4017.5.camel@concordia> (raw)
In-Reply-To: <1259096952.16367.134.camel@pasglop>

[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]

On Wed, 2009-11-25 at 08:09 +1100, Benjamin Herrenschmidt wrote:
> On Tue, 2009-11-24 at 12:53 +0000, Ralf Baechle wrote:
> > On Tue, Nov 24, 2009 at 01:39:48PM +1100, Michael Ellerman wrote:
> > 
> > > Having just hit a build-break caused by a distro building with
> > > PCI_MSI=n, I set out to make it default y for powerpc. Unfortunately
> > > that's not possible, because it's in drivers/pci/Kconfig.
> > > 
> > > So is it time to make it default y for everyone? It seems to me having
> > > it off is more likely to cause problems than having it on these days,
> > > though I'm not sure if that is true for all archs.
> > > 
> > > An arch that really didn't want it default y could conditionally select
> > > ARCH_SUPPORTS_MSI, like x86 does already.
> > 
> > On MIPS the age of MSI only recently started; once single platform (Cavium)
> > out of all the many uses it.  Cavium does a "select ARCH_SUPPORTS_MSI" but
> > not "select PCI_MSI" because not all platform variants actually have PCI.
> > 
> > We should  not give a user a chance to select something wrong in kconfig
> > thus automatically as many options for a platform as possible is a good
> > thing - after all the kconfig dialog for any given platfrom has become
> > painfully long.  And we really should have to avoid users having to know
> > that the Frobnic 2000 they're trying to upgrade the kernel for requires
> > MSI to work ...
> 
> Still... select has nasty issues. I think default y is fine here. For
> platforms that don't need it, make sure their defconfigs don't have it
> set...
> 
> Or maybe default y if (X86 || PPC)

Oh yeah I forgot we could do that. So we could either do that, or add a
ARCH_MSI_DEFAULT and use that as the if condition. If people really
care.

cheers



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-11-25  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1259030388.20596.5.camel@concordia>
2009-11-24 12:53 ` Time to make PCI_MSI default y ? Ralf Baechle
2009-11-24 21:09   ` Benjamin Herrenschmidt
2009-11-25  0:31     ` Michael Ellerman [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=1259109094.4017.5.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=ddaney@caviumnetworks.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.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 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.