From: Greg KH <gregkh@linuxfoundation.org>
To: Neil Zhang <zhangwm@marvell.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: base: update cpu offline info when do hotplug
Date: Mon, 20 Oct 2014 14:48:26 +0800 [thread overview]
Message-ID: <20141020064826.GA4064@kroah.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED9024EB81CAF@SC-VEXCH4.marvell.com>
On Sun, Oct 19, 2014 at 11:39:23PM -0700, Neil Zhang wrote:
>> How much noise is this going to cause on a big/little system that
>> constantly hot unplug/plugs processors all of the time?
>
> Can you explain more what kind of noise will be introduced on a big/little system?
Have you tested this on such a machine?
> As I know IKS on arm will use cpu_suspend way to power down a core.
Are you sure that it also doesn't use that same functionality to drop a
processor to save power?
Why do you need/want this notification? What are you going to do with
this information that you don't already have?
thanks,
greg k-h
next prev parent reply other threads:[~2014-10-20 6:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 3:29 [PATCH] drivers: base: update cpu offline info when do hotplug Neil Zhang
2014-10-20 4:43 ` Greg KH
2014-10-20 6:39 ` Neil Zhang
2014-10-20 6:48 ` Greg KH [this message]
2014-10-20 7:40 ` Neil Zhang
2014-10-20 17:02 ` Dan Streetman
2014-10-21 0:47 ` Neil Zhang
2014-10-21 2:57 ` Yasuaki Ishimatsu
2014-10-21 3:18 ` Neil Zhang
2014-10-21 3:26 ` Yasuaki Ishimatsu
2014-10-21 3:36 ` Neil Zhang
2014-10-21 4:47 ` Yasuaki Ishimatsu
2014-10-21 12:58 ` Dan Streetman
2014-10-27 1:43 ` Neil Zhang
2014-10-27 1:58 ` Greg KH
2014-10-27 2:17 ` Neil Zhang
2014-10-27 2:26 ` Greg KH
2014-10-27 2:30 ` Neil Zhang
2014-10-27 16:28 ` Dan Streetman
2014-10-21 13:02 ` Dan Streetman
2014-10-22 1:32 ` Neil Zhang
2014-10-23 14:05 ` Dan Streetman
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=20141020064826.GA4064@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangwm@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.