From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Olof Johannsson <olof@lixom.net>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 2/7] Powerpc MSI implementation
Date: Fri, 12 Jan 2007 08:54:57 +1100 [thread overview]
Message-ID: <1168552498.22458.428.camel@localhost.localdomain> (raw)
In-Reply-To: <1168550403.22458.414.camel@localhost.localdomain>
On Fri, 2007-01-12 at 08:20 +1100, Benjamin Herrenschmidt wrote:
> > So, no, I don't agree with this implementation and don't want to see it
> > go through anyone's tree into mainline just yet.
>
> So why, when we posted it earlier, you said the exact opposite ? That
> you actually liked it and wanted to see it as a replacement of the
> current cruft ?
>
> That's been the logic from day one. We implement a generic MSI support
> that supports multiple backends, we do it as a powerpc version at first
> since that's what we can actively test and provide backends for, then as
> a second step, we work with the intel folks to port their stuff over to
> our implementation and replace the current crappy generic one.
/me calms down a bit ... :-)
Ok, so what about we do:
- Move that new implementation to drivers/pci
- Have a CONFIG_NEW_MSI or something like that to select between
the old and the new implementation
- Have the change to pci_dev be based on that config option
Note: There should be no impact on drivers nor anything out of
drivers/pci and associated arch support code, the API exposed to drivers
should be identical.
That way, it will be easier for Intel/Altix folks to port over to the
new code as it will be accessible to all archs via a config option. Once
Intel & Altix have ported over, the old code can be removed and
CONFIG_NEW_MSI too.
I know that other archs have actually been waiting for that new
infrastructure (well, according to some feedback we got when Michael
first posted it) so that's probably a better approach than having it in
arch/powerpc indeed.
Cheers,
Ben.
next prev parent reply other threads:[~2007-01-11 21:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 11:25 [PATCH 0/7] Powerpc MSI Implementation Michael Ellerman
2007-01-11 11:25 ` [PATCH 1/7] Rip out the existing powerpc msi stubs Michael Ellerman
2007-01-11 21:31 ` Christoph Hellwig
2007-01-11 11:25 ` [PATCH 2/7] Powerpc MSI implementation Michael Ellerman
2007-01-11 19:44 ` Greg KH
2007-01-11 21:20 ` Benjamin Herrenschmidt
2007-01-11 21:54 ` Benjamin Herrenschmidt [this message]
2007-01-12 23:13 ` Greg KH
2007-01-13 5:57 ` Benjamin Herrenschmidt
2007-01-13 19:27 ` Greg KH
2007-01-13 20:40 ` Benjamin Herrenschmidt
2007-01-12 23:11 ` Greg KH
2007-01-11 21:36 ` Christoph Hellwig
2007-01-12 7:27 ` Benjamin Herrenschmidt
2007-01-11 11:25 ` [PATCH 3/7] Enable MSI on Powerpc Michael Ellerman
2007-01-11 21:37 ` Christoph Hellwig
2007-01-12 7:24 ` Benjamin Herrenschmidt
2007-01-11 11:25 ` [PATCH 5/7] MPIC MSI backend Michael Ellerman
2007-01-11 11:25 ` [PATCH 4/7] MPIC MSI allocator Michael Ellerman
2007-01-11 15:14 ` Segher Boessenkool
2007-01-11 17:19 ` Will Schmidt
2007-01-11 17:27 ` Segher Boessenkool
2007-01-12 0:27 ` Olof Johansson
2007-01-12 0:33 ` Michael Ellerman
2007-01-11 11:25 ` [PATCH 6/7] Enable MSI mappings for MPIC Michael Ellerman
2007-01-11 15:22 ` Segher Boessenkool
2007-01-11 11:25 ` [PATCH 7/7] Activate MSI for the MPIC backend on U3 Michael Ellerman
2007-01-11 15:23 ` [PATCH 0/7] Powerpc MSI Implementation Segher Boessenkool
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=1168552498.22458.428.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).