From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: KVM: x86: add module parameter to disable periodic kvmclock sync
Date: Thu, 13 Nov 2014 18:46:59 +0100 [thread overview]
Message-ID: <20141113174658.GA6801@potion.brq.redhat.com> (raw)
In-Reply-To: <20141113113219.GA5233@hawk.usersys.redhat.com>
2014-11-13 12:32+0100, Andrew Jones:
> On Thu, Nov 13, 2014 at 11:44:02AM +0100, Andrew Jones wrote:
> > On Thu, Nov 13, 2014 at 09:40:41AM +0100, Andrew Jones wrote:
> > > On Thu, Nov 13, 2014 at 12:44:39AM -0200, Marcelo Tosatti wrote:
> > > > The periodic kvmclock sync can be an undesired source of latencies.
[...]
> > > > +static bool kvmclock_periodic_sync = 1;
> > >
> > > Using 'true' would look nicer.
> >
> > Ahh, disregard this comment. 1 matches what the user would input.
The output is always Y|N and the user can input that as well.
(bool = {true, false}, so I'd prefer 'true'.)
> @@ -1717,7 +1717,8 @@ static void kvmclock_sync_fn(struct work_struct *work)
> kvmclock_sync_work);
> struct kvm *kvm = container_of(ka, struct kvm, arch);
>
> - schedule_delayed_work(&kvm->arch.kvmclock_update_work, 0);
> + if (kvmclock_periodic_sync)
> + schedule_delayed_work(&kvm->arch.kvmclock_update_work, 0);
> schedule_delayed_work(&kvm->arch.kvmclock_sync_work,
> KVMCLOCK_SYNC_PERIOD);
Yes, or add callbacks to sysfs writes that would schedule/cancel this
work. (But having a for_every_vm loop is quite ugly.)
I'd be happy with a 'const kvmclock_periodic_sync'.
(Having useless timers is weird if we care about latencies.)
next prev parent reply other threads:[~2014-11-13 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 2:44 KVM: x86: add module parameter to disable periodic kvmclock sync Marcelo Tosatti
2014-11-13 8:40 ` Andrew Jones
2014-11-13 10:44 ` Andrew Jones
2014-11-13 11:32 ` Andrew Jones
2014-11-13 17:46 ` Radim Krčmář [this message]
2014-11-13 17:47 ` Paolo Bonzini
2014-11-13 17:57 ` Andrew Jones
2014-11-13 18:24 ` Radim Krčmář
2014-11-14 18:51 ` Marcelo Tosatti
2014-11-13 14:14 ` Michael Tokarev
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=20141113174658.GA6801@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.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