All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	KVM list <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: TSC in qem[-kvm] 1.1+ and in-kernel irqchip
Date: Sun, 12 Aug 2012 11:10:38 +0300	[thread overview]
Message-ID: <20120812081038.GJ3341@redhat.com> (raw)
In-Reply-To: <5024D336.5090108@msgid.tls.msk.ru>

On Fri, Aug 10, 2012 at 01:24:06PM +0400, Michael Tokarev wrote:
> On 10.08.2012 11:33, Gleb Natapov wrote:
> > On Thu, Aug 09, 2012 at 10:27:43PM +0400, Michael Tokarev wrote:
> >> As a follow-up to the patch "tsc: use kvmclock for
> >> calibration".
> >>
> >> There's another problem reported by several users.
> >> The sympthom is that grub does not show boot menu,
> >> it boots default entry right away without any pause.
> >>
> >> After quite some debugging it turned out to be
> >> TSC issue.  Grub uses tsc for its timeout handling.
> >> When setting timeout to some very large value
> >> (10000), I can see the counter is ticking backwards
> >> at a very high speed, ticking from 10000 to 0 in
> >> about 5 seconds.
> >>
> >> Running kvm -cpu host,-tsc forces grub to use
> >> rtc clocksource, and the problem goes away.
> >>
> > Can you try -no-kvm-pit-reinjection please.
> 
> It does not help.  With -no-kvm-pit-reinjection, the
> time in grub is ticking about 1000 times faster still,
> just like without.
> 
> >> The most interesting thing is that this is a
> >> problem new for qemu-kvm 1.1 (and is still
> >> present in current git), 1.0 version had no
> >> such issue.  And it only happens when in-kernel
> >> irqchip is enabled -- running with -no-kvm-irqchip
> >> also fixes the grub problem, so that tsc starts
> >> counting "correctly" for grub again.
> >>
> > 1.0 work on the same kernel 1.1 doesn't?
> 
> Yes.  This issue does not look like kernel-dependent -
> it happens the same way on 3.0, 3.2 and 3.5 kernels.
> Note that upstream qemu 1.1+ is also affected, when
> used with -machine pc,kernel_irqchip=on.
> 
Any chance to bisect it?

--
			Gleb.

WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	KVM list <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] TSC in qem[-kvm] 1.1+ and in-kernel irqchip
Date: Sun, 12 Aug 2012 11:10:38 +0300	[thread overview]
Message-ID: <20120812081038.GJ3341@redhat.com> (raw)
In-Reply-To: <5024D336.5090108@msgid.tls.msk.ru>

On Fri, Aug 10, 2012 at 01:24:06PM +0400, Michael Tokarev wrote:
> On 10.08.2012 11:33, Gleb Natapov wrote:
> > On Thu, Aug 09, 2012 at 10:27:43PM +0400, Michael Tokarev wrote:
> >> As a follow-up to the patch "tsc: use kvmclock for
> >> calibration".
> >>
> >> There's another problem reported by several users.
> >> The sympthom is that grub does not show boot menu,
> >> it boots default entry right away without any pause.
> >>
> >> After quite some debugging it turned out to be
> >> TSC issue.  Grub uses tsc for its timeout handling.
> >> When setting timeout to some very large value
> >> (10000), I can see the counter is ticking backwards
> >> at a very high speed, ticking from 10000 to 0 in
> >> about 5 seconds.
> >>
> >> Running kvm -cpu host,-tsc forces grub to use
> >> rtc clocksource, and the problem goes away.
> >>
> > Can you try -no-kvm-pit-reinjection please.
> 
> It does not help.  With -no-kvm-pit-reinjection, the
> time in grub is ticking about 1000 times faster still,
> just like without.
> 
> >> The most interesting thing is that this is a
> >> problem new for qemu-kvm 1.1 (and is still
> >> present in current git), 1.0 version had no
> >> such issue.  And it only happens when in-kernel
> >> irqchip is enabled -- running with -no-kvm-irqchip
> >> also fixes the grub problem, so that tsc starts
> >> counting "correctly" for grub again.
> >>
> > 1.0 work on the same kernel 1.1 doesn't?
> 
> Yes.  This issue does not look like kernel-dependent -
> it happens the same way on 3.0, 3.2 and 3.5 kernels.
> Note that upstream qemu 1.1+ is also affected, when
> used with -machine pc,kernel_irqchip=on.
> 
Any chance to bisect it?

--
			Gleb.

  reply	other threads:[~2012-08-12  8:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 18:27 TSC in qem[-kvm] 1.1+ and in-kernel irqchip Michael Tokarev
2012-08-09 18:27 ` [Qemu-devel] " Michael Tokarev
2012-08-09 19:06 ` Marcelo Tosatti
2012-08-09 19:06   ` [Qemu-devel] " Marcelo Tosatti
     [not found]   ` <20120809204748.GA32346@amt.cnet>
2012-08-09 21:36     ` Michael Tokarev
2012-08-09 21:36       ` [Qemu-devel] " Michael Tokarev
2012-08-10  7:33 ` Gleb Natapov
2012-08-10  7:33   ` Gleb Natapov
2012-08-10  9:24   ` Michael Tokarev
2012-08-10  9:24     ` Michael Tokarev
2012-08-12  8:10     ` Gleb Natapov [this message]
2012-08-12  8:10       ` Gleb Natapov
2012-08-12  9:24       ` Michael Tokarev
2012-08-12  9:24         ` [Qemu-devel] " Michael Tokarev
2012-08-13 13:07         ` Jan Kiszka
2012-08-13 13:07           ` [Qemu-devel] " Jan Kiszka
2012-08-13 13:16           ` Michael Tokarev
2012-08-13 13:16             ` Michael Tokarev
2012-08-13 13:41             ` Jan Kiszka
2012-08-13 13:41               ` Jan Kiszka
2012-08-13 18:18             ` [PATCH uq/master] kvm: i8254: Finish time conversion fix Jan Kiszka
2012-08-13 18:18               ` [Qemu-devel] " Jan Kiszka
2012-08-13 18:40               ` Michael Tokarev
2012-08-13 18:40                 ` [Qemu-devel] " Michael Tokarev
2012-08-14  7:41                 ` Jan Kiszka
2012-08-14  7:41                   ` [Qemu-devel] " Jan Kiszka

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=20120812081038.GJ3341@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.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 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.