linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Gordeev <agordeev@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Yinghai Lu <yinghai@kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
	Matthew Wilcox <willy@linux.intel.com>,
	x86@kernel.org, linux-pci@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH v3 -tip 1/5] x86, MSI: Support multiple MSIs in presense of IRQ remapping
Date: Tue, 2 Oct 2012 13:06:30 +0200	[thread overview]
Message-ID: <20121002110630.GA2258@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <20121002045518.GA7756@gmail.com>

On Tue, Oct 02, 2012 at 06:55:18AM +0200, Ingo Molnar wrote:

Thanks for the review, Ingo.

> > @@ -584,8 +586,12 @@ int __irq_alloc_descs(int irq, unsigned int from, unsigned int cnt, int node,
> >  #define irq_alloc_desc_from(from, node)		\
> >  	irq_alloc_descs(-1, from, 1, node)
> >  
> > +#define irq_alloc_descs_from(from, cnt, node)	\
> > +	irq_alloc_descs(-1, from, cnt, node)
> > +
> 
> Please use inlines instead of macros. Might transform the one 
> above it as well in the process.

You mean here do not introduce irq_alloc_descs_from, but rather use
irq_alloc_descs() directly?

> > +int irq_can_alloc_irqs(unsigned int from, unsigned int cnt)
> > +{
> > +	unsigned int start;
> > +	int ret = 0;
> > +
> > +	if (!cnt)
> > +		return -EINVAL;
> > +
> > +	mutex_lock(&sparse_irq_lock);
> > +	start = bitmap_find_next_zero_area(allocated_irqs, IRQ_BITMAP_BITS,
> > +					   from, cnt, 0);
> > +	mutex_unlock(&sparse_irq_lock);
> > +	if (start + cnt > nr_irqs)
> > +		ret = irq_can_expand_nr_irqs(start + cnt);
> > +	return ret;
> 
> How is this supposed to work wrt. races?

It is not supposed. Just a quick check if there are enough bits before an
attempt to allocate memory in __create_irqs(). Otherwise __create_irqs()
might allocate irq_cfg's, then realize there are no bits, then deallocate
and fail.

But strictly speaking, irq_can_alloc_irqs() is unnecessary.

-- 
Regards,
Alexander Gordeev
agordeev@redhat.com

  reply	other threads:[~2012-10-02 11:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01  8:08 [PATCH v3 -tip 0/5] x86, MSI, AHCI: Support multiple MSIs Alexander Gordeev
2012-10-01  8:09 ` [PATCH v3 -tip 1/5] x86, MSI: Support multiple MSIs in presense of IRQ remapping Alexander Gordeev
2012-10-02  4:55   ` Ingo Molnar
2012-10-02 11:06     ` Alexander Gordeev [this message]
2012-10-02 11:25       ` Ingo Molnar
2012-10-04  7:54         ` Alexander Gordeev
2012-10-04  9:17           ` Ingo Molnar
2012-10-01  8:10 ` [PATCH v3 -tip 2/5] x86, MSI: Allocate as many multiple IRQs as requested Alexander Gordeev
2012-10-02  4:58   ` Ingo Molnar
2012-10-01  8:11 ` [PATCH v3 -tip 3/5] x86, MSI: Minor readability fixes Alexander Gordeev
2012-10-02  4:57   ` Ingo Molnar
2012-10-01  8:12 ` [PATCH v3 -tip 4/5] PCI, MSI: Enable multiple MSIs with pci_enable_msi_block_auto() Alexander Gordeev
2012-10-01  8:13 ` [PATCH v3 -tip 5/5] AHCI: Support multiple MSIs Alexander Gordeev
2012-10-02  3:04   ` Jeff Garzik
2012-10-02  4:21     ` Bjorn Helgaas
2012-10-02  4:48       ` Jeff Garzik
2012-10-02  5:09   ` Ingo Molnar
2012-10-02 16:42     ` Alexander Gordeev
2012-10-02 16:45       ` Jeff Garzik
2012-10-04 14:35         ` 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=20121002110630.GA2258@dhcp-26-207.brq.redhat.com \
    --to=agordeev@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=willy@linux.intel.com \
    --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).