On Tue, Aug 09, 2016 at 11:45:54AM +, Nir Levy wrote:
> I am continuing to learn your simple trace.
> I have used it and seen how it is working.
> the get_clock is saved as 8 octets but is converted via
> ./scripts/simpletrace.py to delta_ns = timestamp - self.last_timestamp
> which result wit
, 2016 6:11 PM
To: Nir Levy
Cc: qemu-devel@nongnu.org; Yan Fridland
Subject: Re: [Qemu-devel] QEMU-guestOS latencies.
On Thu, Jul 28, 2016 at 09:25:41AM +, Nir Levy wrote:
> in addition I wish to understand ram allocation and avoid host swaps.
I didn't read everything but this stood ou
On Thu, Jul 28, 2016 at 09:25:41AM +, Nir Levy wrote:
> in addition I wish to understand ram allocation and avoid host swaps.
I didn't read everything but this stood out. QEMU has a -realtime
mlock=on option if you wish to mlock(2) guest memory on the host.
Stefan
signature.asc
Description
After changing the
inside function qemuMonitorOpenUnix
int timeout to MAX_INT;
in file: ./src/qemu/qemu_monitor.c (libvirt)
I am now able to debug kvm and malloc
I would love hearing some tips regarding tracing for latencies.
regards,
Nir.
From: Nir Levy
Sent: Thursday, July 28, 2016 12:25 PM
To
Hi all,
First, thanks for your time and attention for reading this.
I wish to share with you some of my goals.
My main goal is to trace latencies qemu-kvm interface (in order to see if they
secondary goal is to figure out the way qemu thread are spawned.
in addition I wish to understand ram alloc
