From: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>
To: qemu-devel@nongnu.org
Subject: The -icount option document are confusing
Date: Sat, 25 Apr 2020 23:28:18 +0800 [thread overview]
Message-ID: <CAE2XoE9FP=5SdGZKNAv5ZqvPR-go59eWP4pPKTTuNYCKUHe4xA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
-icount [shift=N|auto][,rr=record|replay,rrfile=filename,rrsnapshot=snapshot
]
When the virtual cpu is sleeping, the virtual time will advance at default
speed unless sleep=on|off is specified. With sleep=on|off, the virtual time
will jump to the next timer deadline instantly whenever the virtual cpu
goes to sleep mode and will not advance if no timer is enabled. This
behavior give deterministic execution times from the guest point of view.
I wanna to know what's the meaning when sleep=on, and what's the meaning
when sleep=off
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
[-- Attachment #2: Type: text/html, Size: 1440 bytes --]
reply other threads:[~2020-04-25 15:29 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='CAE2XoE9FP=5SdGZKNAv5ZqvPR-go59eWP4pPKTTuNYCKUHe4xA@mail.gmail.com' \
--to=luoyonggang@gmail.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 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).