From: Paolo Bonzini <pbonzini@redhat.com>
To: Sebastian Tanase <sebastian.tanase@openwide.fr>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
jeremy.rosen@openwide.fr, aliguori@amazon.com,
wenchaoqemu@gmail.com, quintela@redhat.com, mjt@tls.msk.ru,
mst@redhat.com, stefanha@redhat.com, armbru@redhat.com,
lcapitulino@redhat.com, michael@walle.cc,
camille.begue@openwide.fr, alex@alex.org.uk, crobinso@redhat.com,
pierre.lemagourou@openwide.fr, afaerber@suse.de, rth@twiddle.net
Subject: Re: [Qemu-devel] [RFC PATCH V2 5/5] cpu_exec: Print to console if the guest is late
Date: Fri, 13 Jun 2014 12:29:36 +0200 [thread overview]
Message-ID: <539AD290.7000103@redhat.com> (raw)
In-Reply-To: <1402652437-13194-6-git-send-email-sebastian.tanase@openwide.fr>
Il 13/06/2014 11:40, Sebastian Tanase ha scritto:
> If the align option is enabled, we print to the user whenever
> the guest clock is behind the host clock in order for he/she
> to have a hint about the actual performance. The maximum
> print interval is 2s so as not to spam the console.
>
> Signed-off-by: Sebastian Tanase <sebastian.tanase@openwide.fr>
> Tested-by: Camille Bégué <camille.begue@openwide.fr>
> ---
> cpu-exec.c | 32 +++++++++++++++++++++++++++++++-
> 1 file changed, 31 insertions(+), 1 deletion(-)
>
> diff --git a/cpu-exec.c b/cpu-exec.c
> index 5a3bc5e..a386592 100644
> --- a/cpu-exec.c
> +++ b/cpu-exec.c
> @@ -216,6 +216,8 @@ static void cpu_handle_debug_exception(CPUArchState *env)
> * oscillate around 0.
> */
> #define VM_CLOCK_ADVANCE 3000000
> +#define THRESHOLD_REDUCE 1.5
> +#define MAX_DELAY_PRINT_RATE 2
>
> static int64_t delay_host(int64_t diff_clk)
> {
> @@ -257,6 +259,29 @@ static int64_t align_clocks(int64_t diff_clk, int64_t *oic, CPUState *cpu)
> return diff_clk;
> }
>
> +static void print_delay(int64_t diff_clk, int64_t realtime_clock)
> +{
> + static float threshold_delay;
> + static int64_t last_realtime_clock;
> +
> + if ((realtime_clock - last_realtime_clock) / 1000000000LL
> + >= MAX_DELAY_PRINT_RATE) {
> + if (-diff_clk / (float)1000000000LL > threshold_delay) {
> + threshold_delay = (-diff_clk / 1000000000LL) + 1;
> + printf("Warning: The guest is late by %.1f to %.1f seconds\n",
> + threshold_delay - 1,
> + threshold_delay);
> + } else if (-diff_clk / (float)1000000000LL <
> + (threshold_delay - THRESHOLD_REDUCE)) {
> + threshold_delay = (-diff_clk / 1000000000LL) + 1;
> + printf("Warning: The guest has reduced the delay and is now "
> + "late by %.1f to %.1f seconds\n",
> + threshold_delay - 1,
> + threshold_delay);
> + }
> + last_realtime_clock = realtime_clock;
> + }
> +}
Perhaps stop printing the message after the first 50-100 times?
Paolo
> #endif /* CONFIG USER ONLY */
>
> /* main execution loop */
> @@ -278,6 +303,8 @@ int cpu_exec(CPUArchState *env)
> uint8_t *tc_ptr;
> uintptr_t next_tb;
> #if !(defined(CONFIG_USER_ONLY))
> + /* Print delay control */
> + static int64_t realtime_clock;
> /* Delay algorithm */
> int64_t diff_clk, original_instr_counter;
> #endif
> @@ -342,9 +369,12 @@ int cpu_exec(CPUArchState *env)
> This delay includes the delay of the last cycle, so
> what we have to do is sleep until it is 0. As for the
> advance/delay we gain here, we try to fix it next time. */
> + realtime_clock = qemu_clock_get_ns(QEMU_CLOCK_REALTIME);
> diff_clk = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) -
> - qemu_clock_get_ns(QEMU_CLOCK_REALTIME) + clocks_offset;
> + realtime_clock + clocks_offset;
> original_instr_counter = cpu->icount_extra + cpu->icount_decr.u16.low;
> + /* Print (every 2s max) if the guest is behind the host */
> + print_delay(diff_clk, realtime_clock);
> }
> #endif
> /* prepare setjmp context for exception handling */
>
next prev parent reply other threads:[~2014-06-13 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 9:40 [Qemu-devel] [RFC PATCH V2 0/5] icount: Implement delay algorithm between guest and host clocks Sebastian Tanase
2014-06-13 9:40 ` [Qemu-devel] [RFC PATCH V2 1/5] icount: Add 'align' and 'icount' options Sebastian Tanase
2014-06-13 10:17 ` Paolo Bonzini
2014-06-13 9:40 ` [Qemu-devel] [RFC PATCH V2 2/5] icount: Make icount_time_shift available everywhere Sebastian Tanase
2014-06-13 9:40 ` [Qemu-devel] [RFC PATCH V2 3/5] cpu_exec: Add sleeping algorithm Sebastian Tanase
2014-06-13 10:27 ` Paolo Bonzini
2014-06-13 9:40 ` [Qemu-devel] [RFC PATCH V2 4/5] icount_warp: Take into account initial offset between clocks Sebastian Tanase
2014-06-13 10:28 ` Paolo Bonzini
2014-06-13 9:40 ` [Qemu-devel] [RFC PATCH V2 5/5] cpu_exec: Print to console if the guest is late Sebastian Tanase
2014-06-13 10:29 ` Paolo Bonzini [this message]
2014-06-13 12:00 ` Sebastian Tanase
2014-06-13 12:03 ` Paolo Bonzini
2014-06-13 10:32 ` [Qemu-devel] [RFC PATCH V2 0/5] icount: Implement delay algorithm between guest and host clocks Paolo Bonzini
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=539AD290.7000103@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=alex@alex.org.uk \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=camille.begue@openwide.fr \
--cc=crobinso@redhat.com \
--cc=jeremy.rosen@openwide.fr \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=michael@walle.cc \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pierre.lemagourou@openwide.fr \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=sebastian.tanase@openwide.fr \
--cc=stefanha@redhat.com \
--cc=wenchaoqemu@gmail.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).