|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-users
AW: AW: [Xen-users] Debian Kernel and Xen 3.4 
| In the past I used Debian Etch Xen 3.2-1 with the Bastian Blank (waldi) kernels.
I noticed some problems with MSI handling in that combination. As Debian kernels
and Xen builds created problems for me with respect to powermanagement (time 
went
backwards), I changed to the Xen kernel.
So that was the basis of my guess, when I read that someones using a Debian 
kernel
and an MSI based error message occured. By the option - as explained - you 
switch 
that off and use GSI instead. 
For me, I will check in one of the next steps, whether I can use my 4th PCI 
slot, 
that up to MSI support shared GSI IRQ with the PCIe slots that now have their 
own
MSI.
BR,
Carsten.
----- Originalnachricht -----
Von: Jeff Williams <jeffw@xxxxxxxxxxxxxx>
Gesendet: Don, 4.6.2009 08:15
An: Christoph Kaminski <mangel@xxxxxx>
Cc: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Betreff: Re: AW: [Xen-users] Debian Kernel and Xen 3.4
On 04/06/09 14:00, Christoph Kaminski wrote:
> Hi!
>
> It does work with pci=nomsi... But what is the function of this 
> parameter?
>
nomsi
    If the PCI_MSI kernel config parameter is enabled, this kernel
    boot option can be used to disable the use of MSI interrupts
    system-wide.
http://en.wikipedia.org/wiki/Message_Signaled_Interrupts
Not sure why this has changed for 3.4 though?
Regards,
Jeff
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
 | 
 
| <Prev in Thread] | Current Thread | [Next in Thread> |  | 
AW: AW: [Xen-users] Debian Kernel and Xen 3.4,
Carsten Schiers <=
 |  |  | 
  
    |  |  |