From: Ingo Molnar <mingo@elte.hu>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: "john stultz" <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Gabriel C" <nix.or.die@googlemail.com>,
"CSÉCSY László" <boobaa@frugalware.org>
Subject: Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade
Date: Thu, 22 Jan 2009 20:55:58 +0100 [thread overview]
Message-ID: <20090122195558.GA21118@elte.hu> (raw)
In-Reply-To: <20090122195132.GZ21473@genesis.frugalware.org>
* Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Wed, Jan 21, 2009 at 01:34:06PM -0800, john stultz <johnstul@us.ibm.com> wrote:
> > Miklos: Can you try bisecting this down some?
>
> I did it two times when I finally realised that it depends on the
> config. So currently I have two config files, with "-good" the clock is
> fine, with "-bad" it's too fast.
>
> Of course the diff contains unrelated changes as well, I'm trying to
> find which one is the problematic one.
these look suspect in the good->bad diff:
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_VSMP is not set
-# CONFIG_X86_VISWS is not set
-# CONFIG_X86_RDC321X is not set
+CONFIG_X86_VISWS=y
+CONFIG_X86_RDC321X=y
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
-# CONFIG_PARAVIRT_GUEST is not set
+CONFIG_PARAVIRT_GUEST=y
+# CONFIG_VMI is not set
+CONFIG_KVM_CLOCK=y
+CONFIG_KVM_GUEST=y
+CONFIG_LGUEST_GUEST=y
+CONFIG_PARAVIRT=y
+CONFIG_PARAVIRT_CLOCK=y
+# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_MEMTEST=y
Ingo
next prev parent reply other threads:[~2009-01-22 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 17:14 System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade Miklos Vajna
2009-01-21 20:00 ` john stultz
2009-01-21 21:07 ` Miklos Vajna
2009-01-21 21:34 ` john stultz
2009-01-22 19:51 ` Miklos Vajna
2009-01-22 19:55 ` Ingo Molnar [this message]
2009-01-23 0:12 ` Miklos Vajna
2009-01-22 20:03 ` john stultz
2009-01-22 23:57 ` Miklos Vajna
2009-01-23 1:43 ` john stultz
2009-01-23 11:04 ` Ingo Molnar
2009-01-24 1:36 ` john stultz
2009-01-24 9:14 ` Ingo Molnar
2009-01-25 11:18 ` Florian Fainelli
2009-01-25 15:03 ` Ingo Molnar
2009-01-25 15:38 ` Florian Fainelli
2009-01-25 16:00 ` Ingo Molnar
2009-01-25 11:17 ` Florian Fainelli
2009-01-25 15:02 ` Ingo Molnar
2009-01-25 14:59 ` Robert Schwebel
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=20090122195558.GA21118@elte.hu \
--to=mingo@elte.hu \
--cc=boobaa@frugalware.org \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nix.or.die@googlemail.com \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=vmiklos@frugalware.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