From: Michael Ellerman <mpe@ellerman.id.au>
To: Preeti U Murthy <preeti@linux.vnet.ibm.com>
Cc: aik@ozlabs.ru, shreyas@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, anton@samba.org,
tglx@linutronix.de, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V4] tick/hotplug: Handover time related duties before cpu offline
Date: Tue, 17 Feb 2015 15:55:16 +1100 [thread overview]
Message-ID: <1424148916.31713.1.camel@ellerman.id.au> (raw)
In-Reply-To: <54E2BECD.3050301@linux.vnet.ibm.com>
On Tue, 2015-02-17 at 09:38 +0530, Preeti U Murthy wrote:
> On 02/17/2015 07:28 AM, Michael Ellerman wrote:
> > On Sat, 2015-01-31 at 09:44 +0530, Preeti U Murthy wrote:
> >> These duties include do_timer to update jiffies and broadcast wakeups on those
> >> platforms which do not have an external device to handle wakeup of cpus from deep
> >> idle states. The handover of these duties is not robust against a cpu offline
> >> operation today.
> >
> > Hi Preeti,
> >
> > This bug is still causing breakage for people on Power8 machines.
> >
> > Are we just waiting for Thomas to take the patch?
>
> Hi mpe,
>
> Thomas has included the patch for fixing this issue in a recent patchset
> that he posted for cleaning up tick/clockevents related code.
> https://lkml.org/lkml/2015/2/16/213. I think it will go into this
> merge-window. There are a couple of issues there, once that is fixed I
> will remind him to mark it for stable.
Ah thanks. I missed it when searching LKML because it was posted by Peter.
cheers
prev parent reply other threads:[~2015-02-17 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 4:14 [PATCH V4] tick/hotplug: Handover time related duties before cpu offline Preeti U Murthy
2015-02-17 1:58 ` Michael Ellerman
2015-02-17 4:08 ` Preeti U Murthy
2015-02-17 4:55 ` Michael Ellerman [this message]
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=1424148916.31713.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=shreyas@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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).