From: "Matt T. Yourst" <yourst@yourst.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen cpufreq support status: how to notify hypervisor of frequency change?
Date: Wed, 12 Apr 2006 22:31:17 -0400 [thread overview]
Message-ID: <200604122231.17561.yourst@yourst.com> (raw)
In-Reply-To: <367ff4cc58e23ff395b7944b7b28b35b@cl.cam.ac.uk>
On Wednesday 12 April 2006 01:47 am, you wrote:
>
> local_time_calibration() won't really do the right thing. It will
> calibrate for the observed TSC rate over the last few seconds, most of
> which will have passed at the old TSC rate. The simplest fix would
> simply be to multiply the calculated TSC scale factor by
> new_mhz/old_mhz.
Doesn't set_time_scale() do exactly this by directly using the supplied
ticks_per_sec value? Why does it need to be scaled based on the old frequency
when the values can just be recalculated?
I removed the call to local_time_calibration() and it still works just fine,
so it looks like set_time_scale() overrides the other settings anyway.
I'm still having a strange issue (only in X sessions it appears) where the key
repeat rate and response time gets very slow after a frequency shift.
Everything else responds normally except for the keyboard, and that problem
goes away after a minute or two. Any idea what's going on?
- Matt
-------------------------------------------------------
Matt T. Yourst yourst@cs.binghamton.edu
Binghamton University, Department of Computer Science
-------------------------------------------------------
next prev parent reply other threads:[~2006-04-13 2:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 22:29 Xen cpufreq support status: how to notify hypervisor of frequency change? Matt T. Yourst
2006-04-10 14:01 ` Keir Fraser
2006-04-11 0:05 ` Matt T. Yourst
2006-04-11 8:25 ` Keir Fraser
2006-04-11 20:11 ` Matt T. Yourst
2006-04-12 5:47 ` Keir Fraser
2006-04-13 2:31 ` Matt T. Yourst [this message]
2006-04-13 10:44 ` Keir Fraser
2006-04-13 18:28 ` Matt T. Yourst
2006-04-14 6:44 ` Keir Fraser
2006-04-12 2:49 ` Matt T. Yourst
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=200604122231.17561.yourst@yourst.com \
--to=yourst@yourst.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.