From: Tobias Geiger <tobias.geiger@vido.info>
To: xen-devel@lists.xensource.com
Subject: Re: A clocksource question
Date: Fri, 12 Mar 2010 22:56:02 +0100 [thread overview]
Message-ID: <201003122256.02254.tobias.geiger@vido.info> (raw)
In-Reply-To: <4B9AB126.1070406@goop.org>
Am Freitag 12 März 2010 22:24:54 schrieb Jeremy Fitzhardinge:
> On 03/12/2010 11:02 AM, Joanna Rutkowska wrote:
> > Today I upgraded to xen 3.4.3-rc3 and tried the 2.6.32 kernel (the
> > Micheal Young's one) -- the same problem :(
>
> Good, in a way. I can't think of a reason it would change from .31 -> .32.
>
> Experiment of the moment: does changing the clocksource in
> /sys/devices/system/clocksource/clocksource0/current_clocksource reset
> the problem after killing the other domains? Ie, switch it from
> xen->jiffies->xen for a while.
>
kbpc2:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
xen
kbpc2:~# cat
/sys/devices/system/clocksource/clocksource0/available_clocksource
xen
kbpc2:~# echo "jiffies"
>/sys/devices/system/clocksource/clocksource0/current_clocksource
kbpc2:~# dmesg | tail -1
[ 7898.642404] Override clocksource jiffies is not HRT compatible. Cannot switch
while in HRT/NOHZ mode
kbpc2:~#
Seems like it's not possible to switch to jiffies - however:
kbpc2:~# zcat /proc/config.gz | grep NO_HZ
# CONFIG_NO_HZ is not set
but CONFIG_SCHED_HRTICK=y
Greetings
Tobias
> Thanks,
> J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-03-12 21:56 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 10:47 A clocksource question Joanna Rutkowska
2010-03-09 10:50 ` Keir Fraser
2010-03-09 10:54 ` Joanna Rutkowska
2010-03-09 11:06 ` Joanna Rutkowska
2010-03-09 12:07 ` Pasi Kärkkäinen
2010-03-09 12:10 ` Joanna Rutkowska
2010-03-09 15:42 ` Konrad Rzeszutek Wilk
2010-03-09 23:36 ` Jeremy Fitzhardinge
2010-03-10 22:13 ` Joanna Rutkowska
2010-03-11 0:07 ` Dan Magenheimer
2010-03-11 0:15 ` Joanna Rutkowska
2010-03-11 0:21 ` Ian Pratt
2010-03-11 0:44 ` Dan Magenheimer
2010-03-12 0:34 ` Joanna Rutkowska
2010-03-11 0:52 ` Joanna Rutkowska
2010-03-11 1:06 ` Jeremy Fitzhardinge
2010-03-11 1:19 ` Joanna Rutkowska
2010-03-11 4:55 ` Jeremy Fitzhardinge
2010-03-11 10:49 ` Joanna Rutkowska
2010-03-12 0:27 ` Joanna Rutkowska
2010-03-12 0:49 ` Jeremy Fitzhardinge
2010-03-12 0:38 ` Joanna Rutkowska
2010-03-12 19:02 ` Joanna Rutkowska
2010-03-12 21:24 ` Jeremy Fitzhardinge
2010-03-12 21:56 ` Tobias Geiger [this message]
2010-03-12 22:02 ` Jeremy Fitzhardinge
2010-03-12 21:01 ` Joanna Rutkowska
2010-03-12 21:13 ` Joanna Rutkowska
2010-03-12 23:48 ` Jeremy Fitzhardinge
2010-03-13 9:58 ` Joanna Rutkowska
2010-03-13 19:30 ` Jeremy Fitzhardinge
2010-03-15 6:49 ` Tobias Geiger
2010-03-16 6:01 ` Joanna Rutkowska
2010-03-17 13:35 ` Tobias Geiger
2010-03-17 15:21 ` Joanna Rutkowska
2010-03-17 16:20 ` Jeremy Fitzhardinge
2010-03-17 17:05 ` Joanna Rutkowska
2010-03-17 17:21 ` Jeremy Fitzhardinge
2010-03-17 16:26 ` Dan Magenheimer
2010-03-12 22:56 ` Tobias Geiger
2010-03-11 7:47 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2010-03-12 11:42 Tobias Geiger
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=201003122256.02254.tobias.geiger@vido.info \
--to=tobias.geiger@vido.info \
--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 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).