From: Peter Xu <peterx@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 1/1] system: improve migration debug
Date: Mon, 9 Sep 2024 10:55:52 -0400 [thread overview]
Message-ID: <Zt8MeHIUCdu3LqLE@x1n> (raw)
In-Reply-To: <20240905191941.310592-1-den@openvz.org>
On Thu, Sep 05, 2024 at 09:19:41PM +0200, Denis V. Lunev wrote:
> Right now migration_throttle() tracepoint lacks very important
> important information, i.e. no one could easily say how much the guest
> is throttled. This makes difficult to debug guest quality of service
> during migration.
>
> This patch adds one more tracepoint into cpu_throttle_set() which is
> actually doing this job.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Peter Xu <peterx@redhat.com>
> CC: Fabiano Rosas <farosas@suse.de>
> CC: Paolo Bonzini <pbonzini@redhat.com>
> ---
> Changes from v1:
> - adding tracepoint directly to cpu_throttle_set() as suggested by Peter
queued, thanks.
--
Peter Xu
prev parent reply other threads:[~2024-09-09 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 19:19 [PATCH v2 1/1] system: improve migration debug Denis V. Lunev via
2024-09-09 14:55 ` Peter Xu [this message]
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=Zt8MeHIUCdu3LqLE@x1n \
--to=peterx@redhat.com \
--cc=den@openvz.org \
--cc=farosas@suse.de \
--cc=pbonzini@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 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).