From: Andrew Morton <akpm@linux-foundation.org>
To: Don Zickus <dzickus@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
uobergfe@redhat.com
Subject: Re: [PATCH 0/9] watchdog: internally split softlockup and hardlockup
Date: Wed, 21 Jan 2015 14:23:08 -0800 [thread overview]
Message-ID: <20150121142308.5c88fc5a6ea51a70e64d3c9c@linux-foundation.org> (raw)
In-Reply-To: <20150121141552.GB116159@redhat.com>
On Wed, 21 Jan 2015 09:15:52 -0500 Don Zickus <dzickus@redhat.com> wrote:
> On Tue, Nov 04, 2014 at 11:20:15AM -0500, Don Zickus wrote:
> > The hardlockup and softockup had always been tied together. Due to the request
> > of KVM folks, they had a need to have one enabled but not the other.
> > Internally rework the code to split things apart more cleanly.
> >
> > There is a bunch of churn here, but the end result should be code that should
> > be easier to maintain and fix without knowing the internals of what is going
> > on.
> >
> > Tested by Uli and myself.
>
> Hi Andrew,
>
> Poking again. What can I do to move this along? Should I repost?
I don't actually remember seeing this, but November was soooo long ago ;)
Yes please - refresh, retest, resend. Don't forget to gather up any
new acked/reviewed/tested-by's.
next prev parent reply other threads:[~2015-01-21 22:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 16:20 Don Zickus
2014-11-04 16:20 ` [PATCH 1/9] watchdog: new definitions and variables, initialization Don Zickus
2014-11-04 16:20 ` [PATCH 2/9] watchdog: introduce the proc_watchdog_update() function Don Zickus
2014-11-04 16:20 ` [PATCH 3/9] watchdog: move definition of 'watchdog_proc_mutex' outside of proc_dowatchdog() Don Zickus
2014-11-04 16:20 ` [PATCH 4/9] watchdog: introduce the proc_watchdog_common() function Don Zickus
2014-11-04 16:20 ` [PATCH 5/9] watchdog: introduce separate handlers for parameters in /proc/sys/kernel Don Zickus
2014-11-04 16:20 ` [PATCH 6/9] watchdog: implement error handling for failure to set up hardware perf events Don Zickus
2014-11-04 16:20 ` [PATCH 7/9] watchdog: enable the new user interface of the watchdog mechanism Don Zickus
2014-11-04 16:20 ` [PATCH 8/9] watchdog: clean up some function names and arguments Don Zickus
2014-11-04 16:20 ` [PATCH 9/9] watchdog: introduce the hardlockup_detector_disable() function Don Zickus
2014-12-17 21:25 ` [PATCH 0/9] watchdog: internally split softlockup and hardlockup Don Zickus
2015-01-21 14:15 ` Don Zickus
2015-01-21 22:23 ` Andrew Morton [this message]
2015-02-05 20:40 Don Zickus
2015-02-05 23:22 ` Andrew Morton
2015-02-06 14:12 ` 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=20150121142308.5c88fc5a6ea51a70e64d3c9c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®