linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Alexander Gordeev <agordeev@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Yinghai Lu <yinghai@kernel.org>, Joerg Roedel <joro@8bytes.org>,
	Jan Beulich <JBeulich@suse.com>, Ingo Molnar <mingo@redhat.com>,
	Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Subject: Re: [PATCH v3 -tip x86/apic 1/2] PCI/MSI: Allocate as many multiple-MSIs as requested
Date: Wed, 5 Jun 2013 12:35:31 -0600	[thread overview]
Message-ID: <CAErSpo5pZupF3qq-w=EuJXswUOqZTXQmSnMioqtVSvSDmo2fjg@mail.gmail.com> (raw)
In-Reply-To: <20130605183318.GE12812@phenom.dumpdata.com>

On Wed, Jun 5, 2013 at 12:33 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Wed, Jun 05, 2013 at 11:18:54AM -0600, Bjorn Helgaas wrote:
>> On Tue, Jun 4, 2013 at 7:14 AM, Alexander Gordeev <agordeev@redhat.com> wrote:
>> > On Mon, Jun 03, 2013 at 02:46:59PM -0600, Bjorn Helgaas wrote:
>> >> On Wed, May 29, 2013 at 2:58 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>> >> I pushed these with updates to
>> >> http://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/log/?h=pci/alexander-msi
>> >>
>> >> Anybody want to ack the iommu/irq_remapping.c patch?  If so, I can
>> >> merge that branch into -next for v3.11.
>> >
>> > Konrad, Sebastian,
>> >
>> > Any chance to take a look and patch 2/2?
>
> I presume you mean:
> x86/MSI: Conserve interrupt resources when using multiple-MSI
>
> ? Looks good
> This one:
> PCI: Allocate only as many MSI vectors as requested by driver
>
>
> looks OK as well.

Great, thanks, Konrad!

  reply	other threads:[~2013-06-05 18:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 21:51 [PATCH v3 -tip x86/apic 1/2] PCI/MSI: Allocate as many multiple-MSIs as requested Bjorn Helgaas
2013-05-29  8:36 ` Alexander Gordeev
2013-05-29 20:58   ` Bjorn Helgaas
2013-06-03 20:46     ` Bjorn Helgaas
2013-06-04 13:14       ` Alexander Gordeev
2013-06-05 17:18         ` Bjorn Helgaas
2013-06-05 18:33           ` Konrad Rzeszutek Wilk
2013-06-05 18:35             ` Bjorn Helgaas [this message]
2013-06-20 12:51       ` Joerg Roedel
2013-06-25 17:34         ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2013-05-13  9:05 [PATCH v3 -tip x86/apic 0/2] " Alexander Gordeev
2013-05-13  9:05 ` [PATCH v3 -tip x86/apic 1/2] " Alexander Gordeev
2013-05-28  9:50   ` Ingo Molnar
2013-06-05 20:56   ` Sebastian Andrzej Siewior
2013-06-05 21:09     ` Bjorn Helgaas
2013-06-05 21:28       ` Sebastian Andrzej Siewior
2013-06-06  8:30     ` Alexander Gordeev
2013-06-06 19:51       ` Sebastian Andrzej Siewior

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='CAErSpo5pZupF3qq-w=EuJXswUOqZTXQmSnMioqtVSvSDmo2fjg@mail.gmail.com' \
    --to=bhelgaas@google.com \
    --cc=JBeulich@suse.com \
    --cc=agordeev@redhat.com \
    --cc=joro@8bytes.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sebastian@breakpoint.cc \
    --cc=x86@kernel.org \
    --cc=yinghai@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).