[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] W.: Aw: Re: Testreport Master-branch (4.3, github June 3rd, 23:15 MTZ (+2)



 Hi Ian,
after some disappointing error messages, I did many steps, but I'm sure to have 
checked out the newest commit on master, at 21 p.m. UTC on June 3rd, so you 
should be correct.

To get IOMMU working on my mainboard, I had to apply this patch:
http://lists.xen.org/archives/html/xen-devel/2013-05/msg00448.html

####
"I have patched iommu_acpi.c as follows:


--- orig/xen/drivers/passthrough/amd/iommu_acpi.c 2013-05-04
21:18:18.148000000 -0400
+++ 
xen-unstable-3f28d0077788e7f8cd3ee25b023a4225d7e26e87/xen/drivers/passthrough/amd/iommu_acpi.c
2013-04-23 22:27:28.028000000 -0400
@@ -679,8 +679,9 @@
                                     special->handle);
                 else
                 {
-                    printk(XENLOG_ERR "IVHD Error: Conflicting
IO-APIC %#x entries\n",
+                    printk(XENLOG_ERR "ignored - IVHD Error:
Conflicting IO-APIC %#x entries\n",
                            special->handle);
+                    break;
                     if ( amd_iommu_perdev_intremap )
                         return 0;
                 }
@@ -702,12 +703,14 @@
             }
             break;
         }
+ /*
         if ( apic == nr_ioapics )
         {
             printk(XENLOG_ERR "IVHD Error: Invalid IO-APIC %#x\n",
                    special->handle);
             return 0;
         }
+ */
         break;
     case ACPI_IVHD_HPET:
         /* set device id of hpet */


############

I applied this patch manually in the mentioned file, because I wanted to look 
up if it had already been applied in the git. With the patch I get as xl dmesg:
"[...]
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) ignored - IVHD Error: Conflicting IO-APIC 0x4 entries
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) AMD-Vi: Enabling per-device vector maps
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
[...]
"

And I use the boot options "iommu=pt iommu=1 iommu=amd-iommu-perdev-intremap"
Xen else disables IOMMU completely on my Supermicro-Board.

Do you need further information?
Regards,
Daniel

----- Original Nachricht ----
Von:     Ian Campbell <Ian.Campbell@xxxxxxxxxx>
An:      Daniel Mayer <danielmayer@xxxxxxxx>
Datum:   04.06.2013 10:13
Betreff: Re: [Xen-devel] Testreport Master-branch (4.3, github June 3rd,
 23:15 MTZ (+2)

> On Tue, 2013-06-04 at 00:19 +0200, Daniel Mayer wrote:
> > Fine so far!
> 
> Glad to hear it, thanks for reporting back.
> 
> From the date you give I suspect this was testing 
>         
>         commit 5cffb77c4072fa5b46700a2dbb3e46c5a54eba6d
>         Author: Aravindh Puthiyaparambil <aravindp@xxxxxxxxx>
>         Date:   Mon Jun 3 15:42:46 2013 +0200
>         
>             x86/MCE: disable if MCE banks are not present
>             
> which was the only commit on that day, does that sound right?
> 
> The previous commit was
>         commit b14fed71515bc6887d288169890c02f7bbe5d960
>         Author: Christoph Egger <chegger@xxxxxxxxx>
>         Date:   Thu May 30 14:24:57 2013 +0200
>         
>             tools/libxl: fix array subscript has type 'char'
> so I guess it depends a bit on when github updates its copy.
> 
> Ian.
> 
> 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.