From: Tejun Heo <tj@kernel.org>
To: Robert Richter <robert.richter@caviumnetworks.com>
Cc: Robert Richter <rric@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Sunil Goutham <sgoutham@cavium.com>,
Jiang Liu <jiang.liu@linux.intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Alexander Gordeev <agordeev@redhat.com>
Subject: Re: [PATCH v2] AHCI: Add generic MSI-X interrupt support to SATA PCI driver
Date: Wed, 13 May 2015 10:39:06 -0400 [thread overview]
Message-ID: <20150513143906.GV11388@htj.duckdns.org> (raw)
In-Reply-To: <20150512114647.GN10428@rric.localhost>
Hello,
On Tue, May 12, 2015 at 01:46:47PM +0200, Robert Richter wrote:
> I don't think this is worth the effort as all internal and external
> drivers need to be changed basically from:
>
> ahci_host_activate(host, irq, &ahci_sht);
>
> to:
>
> host->irq = irq;
> ahci_host_activate(host, &ahci_sht);
>
> This looks not very useful to do. Since irq is used only a single
> time, there is no reason to store it in the host's data structure. It
Doesn't really matter tho.
> also makes the interface more error prone since host->irq might not be
> setup. Apart from that there is an abi change.
But large part of @host needs to be initialized before activation. I
don't think moving irq to that pool changes much if anything.
> I agree that we will need the implemention of host->ports[i]->irq for
> the case there irqs are no longer in sequential order as this might be
> the case for per-port msi-x interrupts. But this is not the focus of
> my implementation and as long there is no hardware for this available,
> it wouldn't make sense to implement this at all.
Why are we doing msix at all? I don't get it.
> So how to proceed? I could send you patches that implement host->irq
> for a single per-host interrupt, and also one that reworks multi-port
> interrupts to use host->ports[i]->irq. But I don't see any benefit
> here. That said, I would better keep my patch here as it is. That do
> you think?
Let's start with why we're doing this in the first place.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-05-13 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 7:45 Robert Richter
2015-05-04 16:06 ` Tejun Heo
2015-05-11 17:18 ` Robert Richter
2015-05-12 11:46 ` Robert Richter
2015-05-13 14:39 ` Tejun Heo [this message]
2015-05-13 17:28 ` Robert Richter
2015-05-13 17:46 ` Tejun Heo
2015-05-13 18:07 ` Robert Richter
2015-05-13 18:10 ` Tejun Heo
2015-05-13 14:33 ` Tejun Heo
2015-05-17 7:33 ` Alexander Gordeev
2015-05-18 8:06 ` Robert Richter
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=20150513143906.GV11388@htj.duckdns.org \
--to=tj@kernel.org \
--cc=agordeev@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.richter@caviumnetworks.com \
--cc=rric@kernel.org \
--cc=sgoutham@cavium.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®