All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>
Subject: Re: MSI and driver APIs
Date: Thu, 15 Dec 2005 16:51:38 -0800	[thread overview]
Message-ID: <20051216005138.GA20547@kroah.com> (raw)
In-Reply-To: <1134617893.16880.17.camel@gaston>

On Thu, Dec 15, 2005 at 02:38:12PM +1100, Benjamin Herrenschmidt wrote:
> So I want to start looking into separate implementation for powerpc, and
> based on what I come up with, find the commonalities and split the
> generic code.

That would be great, as it really is i386/x86-64 specific right now.

> However, there is at least one assumption that annoys me:
> 
> Currently, we assume that MSIs are disabled upon discovery of a device.
> That is, a driver probe() routine is called with MSIs off.
> 
> This is annoying on platforms with "intelligent" firmwares like POWER
> with hypervisor, as the firmware will have already configured MSIs for
> the full system & assigned them to devices.

If you are curious as to why this is, look at the lkml archives about a
month or two ago, where I tried to enable MSI by default.  It was a real
mess and caused way more problems than it tried to solve.

So, as David said, I don't think this is going to work out, sorry.

thanks,

greg k-h

      parent reply	other threads:[~2005-12-16  3:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15  3:38 MSI and driver APIs Benjamin Herrenschmidt
2005-12-15 21:07 ` Roland Dreier
2005-12-15 21:08   ` Benjamin Herrenschmidt
2005-12-15 21:18     ` Roland Dreier
2005-12-15 21:18       ` Benjamin Herrenschmidt
2005-12-15 21:36         ` Roland Dreier
2005-12-15 21:42       ` David S. Miller
2005-12-15 21:56         ` Benjamin Herrenschmidt
2005-12-16  0:51 ` Greg KH [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=20051216005138.GA20547@kroah.com \
    --to=greg@kroah.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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.