linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Gordeev <agordeev@redhat.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Joerg Roedel <joro@8bytes.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Jan Beulich <JBeulich@suse.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v2 2/6] PCI/MSI: Factor out pci_get_msi_cap() interface
Date: Tue, 1 Oct 2013 12:35:27 +0200	[thread overview]
Message-ID: <20131001103526.GA5053@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <20131001075133.GJ17966@concordia>

On Tue, Oct 01, 2013 at 05:51:33PM +1000, Michael Ellerman wrote:
> The disadvantage is that any restriction imposed on us above the quota
> can only be reported as an error from pci_enable_msix().
> 
> The quota code, called from pci_get_msix_limit(), can only do so much to
> interogate firmware about the limitations. The ultimate way to check if
> firmware will give us enough MSIs is to try and allocate them. But we
> can't do that from pci_get_msix_limit() because the driver is not asking
> us to enable MSIs, just query them.

If things are this way then pci_enable_msix() already exposed to this
problem internally on pSeries.

I see that even successful quota checks in rtas_msi_check_device() and
rtas_setup_msi_irqs() do not guarantee (as you say) that firmware will
give enough MSIs. Hence, pci_enable_msix() might fail even though the
its quota checks succeeded.

Therefore, nothing will really change if we make pci_get_msix_limit() check
quota and hope the follow-up call to pci_enable_msix() succeeded.

(Of course, we could allocate-deallocate MSIs at check time, but I think it
is an overkill).

> You'll also need to add another arch hook, for the quota check, and
> we'll have to add it to our per-platform indirection as well.

Already, in a branch, hidden from Bjorn & Tejun eyes ;)

> All a lot of bother for no real gain IMHO.

Well, I do not have a strong opinion here. I leave it to the ones who have :)
But few drivers have became clearer as result of this change (and messy ones
are still messy).

> cheers

-- 
Regards,
Alexander Gordeev
agordeev@redhat.com

  reply	other threads:[~2013-10-01 10:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130905150259.GA30984@dhcp-26-207.brq.redhat.com>
     [not found] ` <20130905150442.GA24148@htj.dyndns.org>
     [not found]   ` <20130905154041.GD30984@dhcp-26-207.brq.redhat.com>
     [not found]     ` <20130905154436.GC24148@htj.dyndns.org>
     [not found]       ` <20130905185440.GA13175@dhcp-26-207.brq.redhat.com>
     [not found]         ` <20130905200608.GA3846@htj.dyndns.org>
     [not found]           ` <CAErSpo4TU2geqzY3AYsL08KimBqtfwa4iUoFHgcFt0zMTBJkHw@mail.gmail.com>
     [not found]             ` <20130906160621.GF22763@mtj.dyndns.org>
     [not found]               ` <20130906233205.GF12956@google.com>
     [not found]                 ` <20130909152044.GA24962@dhcp-26-207.brq.redhat.com>
2013-09-16 10:22                   ` [PATCH v2 2/6] PCI/MSI: Factor out pci_get_msi_cap() interface Alexander Gordeev
2013-09-17 14:30                     ` Michael Ellerman
2013-09-18  9:48                       ` Alexander Gordeev
2013-09-18 14:22                         ` Tejun Heo
2013-09-18 16:50                           ` Alexander Gordeev
2013-09-20  8:24                             ` Alexander Gordeev
2013-09-20 12:27                               ` Tejun Heo
2013-09-25 18:02                                 ` Bjorn Helgaas
2013-09-25 20:58                                   ` Alexander Gordeev
2013-09-25 21:00                                     ` Tejun Heo
2013-09-26  7:46                                       ` Alexander Gordeev
2013-09-26  8:58                                         ` David Laight
2013-09-26 10:45                                           ` Alexander Gordeev
2013-09-26 11:34                                             ` David Laight
2013-09-26 12:13                                               ` Alexander Gordeev
2013-09-26 13:11                                         ` Tejun Heo
2013-09-26 14:39                                           ` Alexander Gordeev
2013-09-26 14:42                                             ` Tejun Heo
2013-10-01  7:19                                             ` Michael Ellerman
2013-09-20 12:26                             ` Tejun Heo
2013-10-01  7:26                               ` Michael Ellerman
2013-10-01  7:35                           ` Michael Ellerman
2013-10-01 11:55                             ` Tejun Heo
2013-10-02  2:33                               ` Michael Ellerman
2013-10-02  3:23                                 ` Tejun Heo
2013-09-26 12:32                         ` Mark Lord
2013-09-26 13:03                           ` Alexander Gordeev
2013-10-02  2:46                             ` Mark Lord
2013-10-02  7:26                               ` Alexander Gordeev
2013-12-18 18:26                           ` Bjorn Helgaas
2013-10-01  7:51                         ` Michael Ellerman
2013-10-01 10:35                           ` Alexander Gordeev [this message]
2013-10-02  2:43                             ` Michael Ellerman
2013-10-02  7:10                               ` Alexander Gordeev

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=20131001103526.GA5053@dhcp-26-207.brq.redhat.com \
    --to=agordeev@redhat.com \
    --cc=JBeulich@suse.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=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=mingo@kernel.org \
    --cc=tj@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).