On Mon, 2015-11-09 at 16:14 +0100, Dario Faggioli wrote: > > > As far as xl accessibility --- doesn't xenperf already read them out? > > > Mmm... ISTR having tried without much luck, and having heard that it > wasn't functional any longer, but maybe I'm confusing it with something > else. I'll try again.
I happened to have an xterm with this in its scroll buffer from earlier: root@marilith-n0:~# xenperf invalid hypercalls T= 0 0 0 0 0 trap: wfi T= 85068 56068 11762 8461 8777 trap: wfe T= 2811 614 716 964 517 trap: cp15 32-bit access T= 4 1 1 1 1 trap: cp15 64-bit access T= 0 0 0 0 0 trap: cp14 32-bit access T= 0 0 0 0 0 trap: cp14 64-bit access T= 0 0 0 0 0 trap: cp14 dbg access T= 0 0 0 0 0 trap: cp access T= 0 0 0 0 0 trap: 32-bit smc T= 0 0 0 0 0 trap: 32-bit hvc T= 1291 510 568 161 52 trap: guest instr abort T= 0 0 0 0 0 trap: guest data abort T= 16446 6885 4358 3431 1772 trap: condition failed T= 0 0 0 0 0 [...] So I think it works. You need to build the hypervisor binary with perfc=y (and optionally perfc_arrays=y) or it doesn't do anything. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
