From: Andrew Morton <akpm@linux-foundation.org>
To: Cyril Bur <cyrilbur@gmail.com>
Cc: mpe@ellerman.id.au, drjones@redhat.com, dzickus@redhat.com,
linux-kernel@vger.kernel.org, mingo@kernel.org,
uobergfe@redhat.com, chaiw.fnst@cn.fujitsu.com, fabf@skynet.be,
atomlin@redhat.com, benzh@chromium.org, schwidefsky@de.ibm.com
Subject: Re: [PATCH v2 0/2] Quieten softlockup detector on virtualised kernels
Date: Mon, 2 Feb 2015 15:08:39 -0800 [thread overview]
Message-ID: <20150202150839.30174a1313e83d1708ace4fc@linux-foundation.org> (raw)
In-Reply-To: <1422853118.2863.1.camel@cyril>
On Mon, 02 Feb 2015 15:58:38 +1100 Cyril Bur <cyrilbur@gmail.com> wrote:
> On Fri, 2015-01-09 at 14:34 +1100, Cyril Bur wrote:
> > 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.
> >
(Top-posting repaired. Please don't).
> Could you please pick these patches up through your tree?
I shall. There were quite a few review comments last time and I *think*
they've been addressed(?). I'll cc the involved parties on the commits
- please check?
next prev parent reply other threads:[~2015-02-02 23:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 3:34 Cyril Bur
2015-01-09 3:34 ` [PATCH v2 1/2] Add another clock for use with the soft lockup watchdog Cyril Bur
2015-02-10 6:19 ` Chai Wen
2015-01-09 3:34 ` [PATCH v2 2/2] powerpc: add running_clock for powerpc to prevent spurious softlockup warnings Cyril Bur
2015-02-04 10:42 ` Paul Bolle
2015-02-05 4:08 ` Cyril Bur
2015-02-02 4:58 ` [PATCH v2 0/2] Quieten softlockup detector on virtualised kernels Cyril Bur
2015-02-02 23:08 ` Andrew Morton [this message]
2015-02-05 20:48 ` Don Zickus
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=20150202150839.30174a1313e83d1708ace4fc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=benzh@chromium.org \
--cc=chaiw.fnst@cn.fujitsu.com \
--cc=cyrilbur@gmail.com \
--cc=drjones@redhat.com \
--cc=dzickus@redhat.com \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=schwidefsky@de.ibm.com \
--cc=uobergfe@redhat.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
all inboxes | Powered by JetHome®