|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [GIT PULL] Xen updates
On 10/27/2010 12:40 PM, Sander Eikelenboom wrote:
> Ah ok you are (of course) completely right thx !
> What strikes me now .. is that when i used this xhci controller passed
> through to a domU i:
> a) saw only one IRQ/vector coupled to xhci_hcd in the /proc/interrupts
> b) i don't see them being counted now in the dom0 although i use the
> controller (i the domU this caused +/- 8000 interrupts a second .. so i
> should be seeing something else the 0 i assume.
The device is working but you're not seeing any interrupts for it? Strange.
J
> --
> Sander
>
>
> CPU0 CPU1 CPU2 CPU3
> 1: 8 0 0 0 xen-pirq-ioapic-edge i8042
> 8: 0 0 0 0 xen-pirq-ioapic-edge rtc0
> 9: 0 0 0 0 xen-pirq-ioapic-level acpi
> 12: 103 0 0 0 xen-pirq-ioapic-edge i8042
> 16: 0 0 0 0 xen-pirq-ioapic-level
> uhci_hcd:usb3
> 18: 0 0 0 0 xen-pirq-ioapic-level
> ehci_hcd:usb1, uhci_hcd:usb5, uhci_hcd:usb8
> 19: 0 0 0 0 xen-pirq-ioapic-level
> uhci_hcd:usb7
> 21: 0 0 0 0 xen-pirq-ioapic-level
> uhci_hcd:usb4
> 23: 73410 0 0 0 xen-pirq-ioapic-level
> ehci_hcd:usb2, uhci_hcd:usb6
> 990: 0 0 0 0 xen-dyn-event
> evtchn:xenstored
> 991: 188 0 0 0 xen-dyn-event
> evtchn:xenstored
> 992: 10583 0 0 0 xen-pirq-msi eth1
> 993: 1 0 0 0 xen-pirq-msi
> 994: 0 0 0 0 xen-pirq-msi-x xhci_hcd
> 995: 0 0 0 0 xen-pirq-msi-x xhci_hcd
> 996: 0 0 0 0 xen-pirq-msi-x xhci_hcd
> 997: 0 0 0 0 xen-pirq-msi-x xhci_hcd
> 998: 1 0 0 0 xen-pirq-msi-x xhci_hcd
> 1000: 51648 0 0 0 xen-pirq-msi ahci
> 1001: 1 0 0 0 xen-pirq-msi i915
> 1002: 0 0 0 0 xen-percpu-virq
> hvc_console
> 1003: 133 0 0 0 xen-dyn-event xenbus
> 1004: 0 0 0 15729 xen-percpu-ipi
> callfuncsingle3
> 1005: 0 0 0 0 xen-percpu-virq debug3
> 1006: 0 0 0 538 xen-percpu-ipi
> callfunc3
> 1007: 0 0 0 24048 xen-percpu-ipi
> resched3
> 1008: 0 0 0 525075 xen-percpu-virq timer3
> 1009: 0 0 19569 0 xen-percpu-ipi
> callfuncsingle2
> 1010: 0 0 0 0 xen-percpu-virq debug2
> 1011: 0 0 451 0 xen-percpu-ipi
> callfunc2
> 1012: 0 0 23590 0 xen-percpu-ipi
> resched2
> 1013: 0 0 523891 0 xen-percpu-virq timer2
> 1014: 0 13911 0 0 xen-percpu-ipi
> callfuncsingle1
> 1015: 0 0 0 0 xen-percpu-virq debug1
> 1016: 0 563 0 0 xen-percpu-ipi
> callfunc1
> 1017: 0 22079 0 0 xen-percpu-ipi
> resched1
> 1018: 0 519767 0 0 xen-percpu-virq timer1
> 1019: 1445 0 0 0 xen-percpu-ipi
> callfuncsingle0
> 1020: 0 0 0 0 xen-percpu-virq debug0
> 1021: 395 0 0 0 xen-percpu-ipi
> callfunc0
> 1022: 22182 0 0 0 xen-percpu-ipi
> resched0
> 1023: 583133 0 0 0 xen-percpu-virq timer0
> NMI: 0 0 0 0 Non-maskable interrupts
> LOC: 0 0 0 0 Local timer interrupts
> SPU: 0 0 0 0 Spurious interrupts
> PMI: 0 0 0 0 Performance monitoring
> interrupts
> IWI: 0 0 0 0 IRQ work interrupts
> RES: 22182 22079 23590 24048 Rescheduling interrupts
> CAL: 1840 14474 20020 16268 Function call interrupts
> TLB: 0 0 0 0 TLB shootdowns
> TRM: 0 0 0 0 Thermal event interrupts
> THR: 0 0 0 0 Threshold APIC interrupts
> MCE: 0 0 0 0 Machine check exceptions
> MCP: 0 0 0 0 Machine check polls
> ERR: 0
> MIS: 0
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |