From: "Matt T. Yourst" <yourst@yourst.com>
To: xen-devel@lists.xensource.com
Cc: yourst@cs.binghamton.edu
Subject: Xen cpufreq support status: how to notify hypervisor of frequency change?
Date: Sat, 8 Apr 2006 18:29:00 -0400 [thread overview]
Message-ID: <200604081829.00179.yourst@yourst.com> (raw)
Hi,
I previously posted a patch to make the dom0 cpufreq drivers properly use
DOM0_MSR (instead of wrmsr) to adjust the processor frequency and voltage.
This does indeed adjust the frequency, but Xen seems to have major latency
problems whenever the frequency change takes affect, causing various problems
like losing mouse events, uncontrolled keyboard repeats, and choppy audio and
video playback for a few seconds after the shift.
This appears to happen because virtual timer interrupts do not get delivered
on a regular basis for a few seconds following the frequency change.
Assuming we want to keep the cpufreq driver itself in dom0, what's the proper
way to notify the hypervisor that the CPU frequency has just changed, so it
can adjust its timers like the cpufreq driver on the native kernel does?
I'd really like to have cpufreq working properly under Xen (for both
workstations and to a lesser extent servers), so what would be the best way
to get this running?
- Matt Yourst
-------------------------------------------------------
Matt T. Yourst yourst@cs.binghamton.edu
Binghamton University, Department of Computer Science
-------------------------------------------------------
next reply other threads:[~2006-04-08 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 22:29 Matt T. Yourst [this message]
2006-04-10 14:01 ` Xen cpufreq support status: how to notify hypervisor of frequency change? 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
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=200604081829.00179.yourst@yourst.com \
--to=yourst@yourst.com \
--cc=xen-devel@lists.xensource.com \
--cc=yourst@cs.binghamton.edu \
/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.