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

[Xen-devel] Losing PS/2 Interrupts


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Thomas Goetz <tcgoetz@xxxxxxxxx>
  • Date: Thu, 19 May 2011 17:45:56 -0400
  • Delivery-date: Thu, 19 May 2011 14:46:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=ixdqxBltV2PJxuzHh6+XmyanfDEOK0CyUp2x+nPSC7ZX3RaRL5fMQ304pWp66sJAyp 2mPz5VPqp2VyftuzAg48ZipWlDSpHxBNyC7je2EaOPd+JXMXQqyVUYuK+MbNq4phe9gU TJmfRRToXo++Uq7M7Ms8FOZX1wXchrIKS/l0E=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm running PVOPs 2.6.38 on Xen 4.0.2 RC3 and while booting a guest I lose 
interrupts for the PS/2 trackpad. The trackpad stops functioning because the 
device is waiting for service. I added a work around that calls i8042_interupt 
form a timer if it hasn't been called in 1s and it started working again. I 
added some code to Xen to count IRQ 12 and compared that to the IRQ 12 count in 
//proc/interrupts (I stopped PS/2 activity and waited for PS/2 interrupt 
activity to stop before taking the counts). I lose one interrupt in Dom0 every 
time the trackpad freezes.


(XEN) IRQ 12 count 21048
12:      21047          0  xen-pirq-ioapic-edge  i8042   <--- lost an interrupt 
in dom0
...

(XEN) IRQ 12 count 48540
12:      48537          0  xen-pirq-ioapic-edge  i8042   <--- lost 3 interrupts 
in dom0


I looked at the point at which the trackpad gets it's last interrupt in a trace 
and the other major activity at that time is the event channel that services 
the Qemu vcpu io_req code.

This 2.6.38 tree has a merge of Stafano's 2.6.39 fixes in drivers/xen/events.c.

Anyone have any ideas or suggestions?

-Tom Goetz

---
Tom Goetz
tcgoetz@xxxxxxxxx





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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