From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] tsc=reliable in Linux guests
Date: Fri, 13 May 2016 11:15:21 +0100 [thread overview]
Message-ID: <20160513101521.GD728@redhat.com> (raw)
I was wondering why the Linux kernel was spending 21ms starting up
each secondary CPU when we boot it virtualized with qemu -smp >= 2.
It turns out the time was lost in check_tsc_sync_target().
This is easily avoided by using `tsc=reliable' on the command line,
saving 63ms when starting a guest with -smp 4 for example.
Is this option safe? If so, why don't we enable it automatically in
the kernel when we detect that we are a KVM guest?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
reply other threads:[~2016-05-13 10:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160513101521.GD728@redhat.com \
--to=rjones@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.