From: Shreyas B Prabhu <shreyas@linux•vnet.ibm.com>
To: Anton Blanchard <anton@samba•org>,
ego@linux•vnet.ibm.com, mpe@ellerman•id.au, mikey@neuling•org,
Paul Mackerras <paulus@samba•org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re: cpuidle broken on mainline
Date: Thu, 23 Jun 2016 01:09:11 +0530 [thread overview]
Message-ID: <576AE95F.6050109@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160623011655.62c610bd@kryten>
Hi,
On 06/22/2016 08:46 PM, Anton Blanchard wrote:
> Hi,
>
> I was noticing some pretty big run to run variations on single threaded
> benchmarks, and I've isolated it cpuidle issues. If I look at
> the cpuidle tracepoint, I notice we only go into the snooze state.
>
> Do we have any known bugs in cpuidle at the moment?
>
I've posted a fix here-
https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-June/144726.html
Thanks,
Shreyas
prev parent reply other threads:[~2016-06-22 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:16 cpuidle broken on mainline Anton Blanchard
2016-06-22 19:39 ` Shreyas B Prabhu [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=576AE95F.6050109@linux.vnet.ibm.com \
--to=shreyas@linux$(echo .)vnet.ibm.com \
--cc=anton@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=ego@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mikey@neuling$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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