From: Peter Xu <peterx@redhat.com>
To: "Denis V. Lunev" <den@virtuozzo.com>
Cc: "Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH 1/1] migration: improve migration_throttle tracepoint
Date: Thu, 5 Sep 2024 14:21:13 -0400 [thread overview]
Message-ID: <Ztn2mfWC8NoxuFY6@x1n> (raw)
In-Reply-To: <fae6629b-523f-46be-8b45-d3fa9174ed4d@virtuozzo.com>
On Thu, Sep 05, 2024 at 08:00:54PM +0200, Denis V. Lunev wrote:
> On 9/5/24 19:52, Peter Xu wrote:
> > On Thu, Sep 05, 2024 at 06:51:46PM +0200, Denis V. Lunev via wrote:
> > > Right now this tracepoint is just saying that the guest has been
> > > throttled, but this is not that good for debugging purposes. We should
> > > also know how much the guest is throttled in order to understand
> > > consequences for the guest behaviour.
> > >
> > > The patch moves the tracepoint from migration_trigger_throttle() to
> > > mig_throttle_guest_down() where this information is really available.
> > > This is not a problem as mig_throttle_guest_down() is called in the
> > > only one place.
> > >
> > > Signed-off-by: Denis V. Lunev <den@openvz.org>
> > > CC: Peter Xu <peterx@redhat.com>
> > > CC: Fabiano Rosas <farosas@suse.de>
> > Makes sense to me, but maybe we can further move it to cpu_throttle_set()?
> >
> in that case we should rename the tracepoint as in that case the
> module would be different :)
>
> 4 90 system/cpu-throttle.c <<cpu_throttle_set>>
> void cpu_throttle_set(int new_throttle_pct)
>
> Will it be OK for you?
Yes. Thanks.
--
Peter Xu
prev parent reply other threads:[~2024-09-05 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 16:51 [PATCH 1/1] migration: improve migration_throttle tracepoint Denis V. Lunev via
2024-09-05 17:52 ` Peter Xu
2024-09-05 18:00 ` Denis V. Lunev
2024-09-05 18:21 ` 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=Ztn2mfWC8NoxuFY6@x1n \
--to=peterx@redhat.com \
--cc=den@openvz.org \
--cc=den@virtuozzo.com \
--cc=farosas@suse.de \
--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).