qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>,
	Rob Bradford <robert.bradford@intel.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU/NEMU boot time with several x86 firmwares
Date: Wed, 5 Dec 2018 13:26:19 +0100	[thread overview]
Message-ID: <51ea7a7e-964a-0f05-75f2-11d6acd9ab77@redhat.com> (raw)
In-Reply-To: <CAGxU2F7Sg0JaxyPQw_FhSc6MzYu+YzZpv9=VHp8qvwfTWpf_MQ@mail.gmail.com>

Hi Stefano,

On 3/12/18 17:35, Stefano Garzarella wrote:
> On Mon, Dec 3, 2018 at 4:44 PM Rob Bradford <robert.bradford@intel.com> wrote:
>>
>> Hi Stefano, thanks for capturing all these numbers,
>>
>> On Mon, 2018-12-03 at 15:27 +0100, Stefano Garzarella wrote:
>>> Hi Rob,
>>> I continued to investigate the boot time, and as you suggested I
>>> looked also at qemu-lite 2.11.2
>>> (https://github.com/kata-containers/qemu) and NEMU "virt" machine. I
>>> did the following tests using the Kata kernel configuration
>>> (
>>> https://github.com/kata-containers/packaging/blob/master/kernel/configs/x86_64_kata_kvm_4.14.x
>>> )
>>>
>>> To compare the results with qemu-lite direct kernel load, I added
>>> another tracepoint:
>>> - linux_start_kernel: first entry of the Linux kernel
>>> (start_kernel())
>>>
>>
>> Great, do you have a set of patches available that all these trace
>> points. It would be great for reproduction.
> 
> For sure! I'm attaching a set of patches for qboot, seabios, ovmf,
> nemu/qemu/qemu-lite and linux 4.14 whit the tracepoints.
> I'm also sharing a python script that I'm using with perf to extract
> the numbers in this way:
> 
> $ perf record -a -e kvm:kvm_entry -e kvm:kvm_pio -e
> sched:sched_process_exec -o /tmp/qemu_perf.data &
> $ # start qemu/nemu multiple times
> $ killall perf
> $ perf script -s qemu-perf-script.py -i /tmp/qemu_perf.data
[...]
Good stuff. At some point I'd like to have such scripts in the QEMU
repository to run perf tests on a regular basis (eventually keep those
metrics somewhere) to be able to catch when we add code that add
timeoutes and increase boot time.

Regards,

Phil.

  parent reply	other threads:[~2018-12-05 12:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 16:40 [Qemu-devel] QEMU/NEMU boot time with several x86 firmwares Stefano Garzarella
2018-11-27  9:57 ` Rob Bradford
2018-11-27 14:21   ` Stefano Garzarella
2018-12-03 14:27     ` Stefano Garzarella
2018-12-03 15:44       ` Rob Bradford
2018-12-03 16:35         ` Stefano Garzarella
2018-12-04 22:44           ` Maran Wilson
2018-12-05 12:06             ` Stefano Garzarella
2018-12-05 13:20             ` Stefan Hajnoczi
2018-12-05 14:19               ` Boris Ostrovsky
2018-12-05 18:04               ` Maran Wilson
2018-12-06 10:38                 ` Stefan Hajnoczi
2018-12-06 14:47                   ` Maran Wilson
2018-12-07 10:02                     ` Stefan Hajnoczi
2018-12-10 13:46                 ` Stefano Garzarella
2018-12-05 12:26           ` Philippe Mathieu-Daudé [this message]
2018-12-05 16:23             ` Stefano Garzarella
2018-12-13 11:19       ` Stefano Garzarella

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51ea7a7e-964a-0f05-75f2-11d6acd9ab77@redhat.com \
    --to=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=robert.bradford@intel.com \
    --cc=sameo@linux.intel.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).