From: Cyril Bur <cyrilbur@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mpe@ellerman.id.au, akpm@linux-foundation.org,
Cyril Bur <cyrilbur@gmail.com>
Subject: [PATCH 0/2] Quieten softlockup detector on virtualised kernels
Date: Mon, 1 Dec 2014 13:38:58 +1100 [thread overview]
Message-ID: <1417401540-12121-1-git-send-email-cyrilbur@gmail.com> (raw)
When the hypervisor pauses a virtualised kernel the kernel will observe a jump
in timebase, this can cause spurious messages from the softlockup detector.
Whilst these messages are harmless, they are accompanied with a stack trace
which causes undue concern and more problematically the stack trace in the
guest has nothing to do with the observed problem and can only be misleading.
Futhermore, on POWER8 this is completely avoidable with the introduction of
the Virtual Time Base (VTB) register.
Cyril Bur (2):
Add another clock for use with the soft lockup watchdog.
powerpc: add running_clock for powerpc to prevent spurious softlockup
warnings
arch/powerpc/kernel/time.c | 24 ++++++++++++++++++++++++
include/linux/sched.h | 1 +
kernel/sched/clock.c | 14 ++++++++++++++
kernel/watchdog.c | 2 +-
4 files changed, 40 insertions(+), 1 deletion(-)
--
1.9.1
next reply other threads:[~2014-12-01 2:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 2:38 Cyril Bur [this message]
2014-12-01 2:38 ` [PATCH 1/2] Add another clock for use with the soft lockup watchdog Cyril Bur
2014-12-01 2:39 ` [PATCH 2/2] powerpc: add running_clock for powerpc to prevent spurious softlockup warnings Cyril Bur
-- strict thread matches above, loose matches on Subject: below --
2014-12-22 5:06 [PATCH 0/2] Quieten softlockup detector on virtualised kernels Cyril Bur
2015-01-05 16:50 ` Don Zickus
2015-01-05 23:53 ` Cyril Bur
2015-01-06 15:01 ` Don Zickus
2015-01-09 3:15 ` Cyril Bur
2015-01-09 14:56 ` Don Zickus
2015-01-05 22:09 ` Andrew Morton
2015-01-06 2:43 ` Cyril Bur
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=1417401540-12121-1-git-send-email-cyrilbur@gmail.com \
--to=cyrilbur@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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).