All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dante Cinco <dantecinco@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: PCI pass-through / MSI question: Is 30(hex) the lower limit for pirq?
Date: Fri, 28 May 2010 13:51:01 -0700	[thread overview]
Message-ID: <4C002CB5.5090102@gmail.com> (raw)
In-Reply-To: <20100528085003.GZ17817@reaktio.net>

Pasi, Jan,

Thank for your help. Adding the extra_guest_irqs Xen boot option 
resolved the issue I was having with the 8G QLogic card in the Windows 
domU. Each of the 2 QLogic devices requires 32 IRQs when MSI-X is 
enabled so I set the value to 80 (16 extra).

Dante

On 5/28/2010 1:50 AM, Pasi Kärkkäinen wrote:
> On Fri, May 28, 2010 at 08:30:40AM +0100, Jan Beulich wrote:
>    
>>>>> On 28.05.10 at 01:29, Dante Cinco<dantecinco@gmail.com>  wrote:
>>>>>            
>>> I'm trying to bring up a Windows domU with PCI pass-through and it looks
>>> like Xen is running out of pirqs (see log below). I'm using Xen 4.0.0 and
>>> dom0 2.6.32.12 pv-ops and pci-stub to hide the PCIe device.
>>>
>>> It looks like the first available pirq is 4e(hex) and the last available is
>>> 30(hex) and after that, Xen returns an msix error. What's the consequence of
>>> running out of pirqs?
>>>        
>> Did you try the extra_guest_irqs= Xen command line option to
>> increase the number of PIRQs (defaulting to 32) for the guest?
>>
>>      
> I added this xen.gz option to:
> http://wiki.xensource.com/xenwiki/XenHypervisorBootOptions
>
> -- Pasi
>
>    

      reply	other threads:[~2010-05-28 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 23:29 PCI pass-through / MSI question: Is 30(hex) the lower limit for pirq? Dante Cinco
2010-05-28  7:30 ` Jan Beulich
2010-05-28  8:50   ` Pasi Kärkkäinen
2010-05-28 20:51     ` Dante Cinco [this message]

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=4C002CB5.5090102@gmail.com \
    --to=dantecinco@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.