From: Don Zickus <dzickus@redhat.com>
To: Cyril Bur <cyrilbur@gmail.com>
Cc: linux-kernel@vger.kernel.org, mpe@ellerman.id.au,
drjones@redhat.com, akpm@linux-foundation.org, mingo@kernel.org,
uobergfe@redhat.com, chaiw.fnst@cn.fujitsu.com, cl@linu.com,
fabf@skynet.be, atomlin@redhat.com, benzh@chromium.org,
mtosatti@redhat.com
Subject: Re: [PATCH 0/2] Quieten softlockup detector on virtualised kernels
Date: Fri, 9 Jan 2015 09:56:51 -0500 [thread overview]
Message-ID: <20150109145651.GE116159@redhat.com> (raw)
In-Reply-To: <1420773300.2801.13.camel@cyril>
On Fri, Jan 09, 2015 at 02:15:00PM +1100, Cyril Bur wrote:
> >
> > I am not too familar with it, but the kernel/watchdog.c code has calls to
> > kvm_check_and_clear_guest_paused(), which is probably a good place to
> > start.
> >
> Ah yes that, I did initially have a look at what it does when I
> undertook to solve the problem on power and I suppose the two solutions
> are similar in that they both just use a virtualised time source. The
> similarities stop there though, the paravirtualised clock that x86 uses
> provides (as the name of the function implies) a 'was paused' flag.
> Obviously the flag isn't something the vtb register on power8 can
> provide and since we have a vtb, its preferable to use that.
> Perhaps x86 can do something with running_clock?
Marcello? Drew?
Cheers,
Don
>
> Regards,
>
> Cyril
>
> > Cheers,
> > Don
> >
> > >
> > > > Not sure if that is useful or could be incoporated into the power8 code.
> > > > Though to be honest I am curious if the steal_time code could be ported to
> > > > your solution as it seems the watchdog code could remove all the
> > > > steal_time warts.
> > > Happy to help sus out the situation here, again, if you could pass on
> > > what the x86 guys are working on, thanks.
> > >
> > >
> > > Thanks,
> > >
> > > Cyril
> > > > I have cc'd Marcelo into this discussion as he was the last person I
> > > > remember talking with about this problem.
> > > >
> > > > Cheers,
> > > > Don
> > >
> > >
>
>
>
next prev parent reply other threads:[~2015-01-09 14:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 5:06 [PATCH 0/2] Quieten softlockup detector on virtualised kernels Cyril Bur
2014-12-22 5:06 ` [PATCH 1/2] Add another clock for use with the soft lockup watchdog Cyril Bur
2015-01-05 22:09 ` Andrew Morton
2014-12-22 5:06 ` [PATCH 2/2] powerpc: add running_clock for powerpc to prevent spurious softlockup warnings Cyril Bur
2015-01-05 22:10 ` Andrew Morton
2015-01-06 2:44 ` Cyril Bur
2015-01-07 10:20 ` Martin Schwidefsky
2015-01-09 3:22 ` Cyril Bur
2015-01-05 16:50 ` [PATCH 0/2] Quieten softlockup detector on virtualised kernels 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 [this message]
2015-01-05 22:09 ` Andrew Morton
2015-01-06 2:43 ` Cyril Bur
-- strict thread matches above, loose matches on Subject: below --
2014-12-01 2:38 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=20150109145651.GE116159@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=benzh@chromium.org \
--cc=chaiw.fnst@cn.fujitsu.com \
--cc=cl@linu.com \
--cc=cyrilbur@gmail.com \
--cc=drjones@redhat.com \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=mtosatti@redhat.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;
as well as URLs for NNTP newsgroup(s).