From: Tejun Heo <tj@kernel.org>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-pci@vger.kernel.org, linux-ide@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Jan Beulich <JBeulich@suse.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 0/4] AHCI: Conserve interrupts with pci_enable_msi_block_part() interface
Date: Wed, 4 Sep 2013 10:57:43 -0400 [thread overview]
Message-ID: <20130904145743.GC25788@mtj.dyndns.org> (raw)
In-Reply-To: <20130904123238.GC8726@dhcp-26-207.brq.redhat.com>
Hello,
On Wed, Sep 04, 2013 at 02:32:39PM +0200, Alexander Gordeev wrote:
> Hmm.. that is actually a great idea. What I am not sure about whether is
> a dummy port still can send (spurious?) interrupts? The hardware interrupt
> handler would have to be reworked then. Seems as a yet another topic to me ;)
Only unimplemented ports are assigned to be dummies and it's highly
unlikely that they'll generate spurious interrupts. That said, I
think it'd be a good idea to be ready for that if that doesn't add too
much complexity / overhead.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-09-04 14:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:59 [PATCH 0/4] AHCI: Conserve interrupts with pci_enable_msi_block_part() interface Alexander Gordeev
2013-09-02 8:59 ` [PATCH 1/4] PCI/MSI: Introduce " Alexander Gordeev
2013-09-03 14:19 ` Tejun Heo
2013-09-02 9:00 ` [PATCH 2/4] MSI/x86: Support " Alexander Gordeev
2013-09-03 13:32 ` Tejun Heo
2013-09-02 9:00 ` [PATCH 3/4] AHCI: Conserve interrupts with " Alexander Gordeev
2013-09-03 14:18 ` Tejun Heo
2013-09-03 16:19 ` Alexander Gordeev
2013-09-03 18:27 ` Tejun Heo
2013-09-04 7:22 ` Alexander Gordeev
2013-09-04 14:17 ` [PATCH v2 " Alexander Gordeev
2013-09-04 14:55 ` [PATCH " Tejun Heo
2013-09-04 16:14 ` Alexander Gordeev
2013-09-04 18:06 ` Tejun Heo
2013-09-04 18:47 ` Alexander Gordeev
2013-09-04 18:51 ` Tejun Heo
2013-09-02 9:00 ` [PATCH 4/4] PCI/MSI: Get rid of pci_enable_msi_block_auto() interface Alexander Gordeev
2013-09-03 7:58 ` [PATCH v2 " Alexander Gordeev
2013-09-03 13:55 ` [PATCH 0/4] AHCI: Conserve interrupts with pci_enable_msi_block_part() interface Tejun Heo
2013-09-03 14:09 ` Tejun Heo
2013-09-04 12:32 ` Alexander Gordeev
2013-09-04 14:57 ` Tejun Heo [this message]
2013-09-03 14:57 ` Alexander Gordeev
2013-09-03 16:24 ` Tejun Heo
2013-09-04 8:06 ` Alexander Gordeev
2013-09-04 15:02 ` Tejun Heo
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=20130904145743.GC25788@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=JBeulich@suse.com \
--cc=agordeev@redhat.com \
--cc=bhelgaas@google.com \
--cc=joro@8bytes.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.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).