Well, I'll humbly apologize for wasting everyone's time :(
Our client connections are coming from Brazil and the server is hosted in
Canada. Turns out, the ISP we are using had issues that were resolved last
night. I haven't changed any qemu parameters for the last couple of days.
Last night we ha
On 18 August 2014 15:32, Dale R. Worley wrote:
> The "per each function call" metric is tricky, because you'd need to
> define what a "function call" is.
In particular, on some guest CPU architectures it's genuinely
not possible to reliably distinguish function call return from a
computed branch.
> From: "Mie Ite"
>
> I would like to know the following information of the guest
> application executed in QEMU:
>
> - the number of guest instructions executed per each function call
> - the number of memory access instructions
> - the address and size of each executed load / store
>
> It it
You could look at the KVM perf support, but I'm unsure if that gives you
enough detail: http://www.linux-kvm.org/page/Perf_events
On 8/18/2014 8:26 AM, Mie Ite wrote:
Hi everyone,
I would like to know the following information of the guest application
executed in QEMU:
- the number of gue
On 8/18/2014 2:26 PM, Mie Ite wrote:
Hi everyone,
I would like to know the following information of the guest application
executed in QEMU:
- the number of guest instructions executed per each function call
- the number of memory access instructions
- the address and size of each executed lo
Hi everyone,
I would like to know the following information of the guest application
executed in QEMU:
- the number of guest instructions executed per each function call
- the number of memory access instructions
- the address and size of each executed load / store
It it possible to extract
