[Fedora-xen] Xen/Linux 3.4.2 performance

[M A Young]

On Thu, 5 Jul 2012, Konrad Rzeszutek Wilk wrote:

> On Thu, Jul 05, 2012 at 11:00:05PM +0100, M A Young wrote:
>> On Tue, 3 Jul 2012, Konrad Rzeszutek Wilk wrote:
>>
>>> Besides that..there is:
>>>
>>> 9846ff1 xen: support pirq_eoi_map
>>> (and its fix) 521394e xen: use the pirq number to check the pirq_eoi_map
>>
>> In my case it is definitely IRQ related. From xl dmesg I get
>
> If you revert those two, are those issues still present?
>> (XEN) physdev.c:164: dom0: wrong map_pirq type 3
>
> This is one is due to another one - a fix that went in 3.3 (allowing
> PCI domains to work).
>
>> (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1)
>
> So vector 240...or 0xf0. That I am not sure about.
>
>
>> (XEN) traps.c:2488:d0 Domain attempted WRMSR 0000000000000079 from
>> 0x00000000000
>> 00000 to 0xffffc90005193030.
>> (XEN) traps.c:2488:d0 Domain attempted WRMSR 0000000000000079 from
>> 0x00000000000
>> 00000 to 0xffffc9000519b030.
>> (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1)
>> (XEN) traps.c:2488:d1 Domain attempted WRMSR 0000000000000079 from
>> 0x00000000000
>> 00000 to 0xffffc900001a9030.
>> (XEN) do_IRQ: 1.40 No irq handler for vector (irq -1)
>> (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1)
>> (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1)

40 and 240 should be IRQ 0 and 1

(XEN)    IRQ:   0 affinity:00000000,00000000,00000000,00000001 vec:f0 
type=IO-AP
IC-edge    status=00000000 mapped, unbound
(XEN)    IRQ:   1 affinity:00000000,00000000,00000000,00000001 vec:28 
type=IO-AP
IC-edge    status=00000050 in-flight=0 domain-list=0:  1(----),
(XEN) IO-APIC interrupt information:
(XEN)     IRQ  0 Vec240:
(XEN)       Apic 0x00, Pin  2: vec=f0 delivery=LoPri dest=L status=0 
polarity=0
irr=0 trig=E mask=0 dest_id:1
(XEN)     IRQ  1 Vec 40:
(XEN)       Apic 0x00, Pin  1: vec=28 delivery=LoPri dest=L status=0 
polarity=0
irr=0 trig=E mask=0 dest_id:1

Incidentally, I have had IRQ problems with this computer before, eg. see 
http://lists.xen.org/archives/html/xen-devel/2010-08/msg01390.html though 
that turned out to be on the xen side.

 	Michael Young