public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: Neil Zhang <zhangwm@marvell.com>, Dan Streetman <ddstreet@ieee.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: base: update cpu offline info when do hotplug
Date: Tue, 21 Oct 2014 13:47:45 +0900	[thread overview]
Message-ID: <5445E571.30107@jp.fujitsu.com> (raw)
In-Reply-To: <9034CBD80F070943B59700D7F8149ED9024EB81D5A@SC-VEXCH4.marvell.com>

(2014/10/21 12:36), Neil Zhang wrote:
>
>
>> -----Original Message-----
>> From: Yasuaki Ishimatsu [mailto:isimatu.yasuaki@jp.fujitsu.com]
>> Sent: 2014年10月21日 11:27
>> To: Neil Zhang; Dan Streetman
>> Cc: Greg KH; linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH] drivers: base: update cpu offline info when do hotplug
>>
>> (2014/10/21 12:18), Neil Zhang wrote:
>>> Yasuaki,
>>>
>>>> -----Original Message-----
>>>> From: Yasuaki Ishimatsu [mailto:isimatu.yasuaki@jp.fujitsu.com]
>>>> Sent: 2014年10月21日 10:57
>>>> To: Dan Streetman; Neil Zhang
>>>> Cc: Greg KH; linux-kernel@vger.kernel.org
>>>> Subject: Re: [PATCH] drivers: base: update cpu offline info when do
>>>> hotplug
>>>>
>>>> Hi Neil and Dan,
>>>>
>>>> (2014/10/21 2:02), Dan Streetman wrote:
>>>>> On Mon, Oct 20, 2014 at 3:40 AM, Neil Zhang <zhangwm@marvell.com> wrote:
>>>>>> Greg,
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Greg KH [mailto:gregkh@linuxfoundation.org]
>>>>>> Sent: 2014年10月20日 14:48
>>>>>> To: Neil Zhang
>>>>>> Cc: linux-kernel@vger.kernel.org
>>>>>> Subject: Re: [PATCH] drivers: base: update cpu offline info when do
>>>>>> hotplug
>>>>>>
>>>>>> 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?
>>>>>>
>>>>>> I didn't have such kind of machine on hand.
>>>>>> Can anyone has such machine to verify it?
>>>>>> Thanks!
>>>>>
>>>>> I tested this on a ppc PowerVM system, using dlpar operations to
>>>>> remove/add cpus.
>>>>>
>>>>> Without this patch the cpu online nodes get out of sync with the
>>>>> main online node (and the actual state of the cpus), because they
>>>>> aren't updated as the cpus are brought up/down:
>>>>>
>>>>
>>>>> [root@br10p02 cpu]$ pwd
>>>>> /sys/devices/system/cpu
>>>>> [root@br10p02 cpu]$ cat online
>>>>> 0-39
>>>>> [root@br10p02 cpu]$ for n in {0..47} ; do test $( cat cpu$n/online )
>>>>> -eq 1 && echo -n "$n " ; done ; echo ""
>>>>> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
>>>>> 26
>>>>> 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
>>>>
>>>> How is the issue reproduced.
>>>>
>>>> Here is a result on my x86 box with linux-3.18-rc1.
>>>>
>>>> - before offline CPU
>>>> # cd /sys/devices/system/cpu/
>>>> # cat online
>>>> 0-59
>>>> # for n in {0..59} ; do test $( cat cpu$n/online ) -eq 1 && echo -n
>>>> "$n " ; done ; echo ""
>>>> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
>>>> 26 27 28
>>>> 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51
>>>> 52 53 54
>>>> 55
>>>> 56 57 58 59
>>>>
>>>> - after offline CPU{1..59}
>>>> # for n in {1..59} ; do echo 0 > cpu$n/online; done # cat online
>>>> 0
>>>> # for n in {0..59} ; do test $( cat cpu$n/online ) -eq 1 && echo -n
>>>> "$n " ; done ; echo ""
>>>> 0
>>>>
>>>> It seems that dev->offline is set to correct valute.
>>>>
>>>
>>
>>> Please use an in kernel governor to up / down a core instead of sysfs
>> interface.
>>
>> Thank you for the information. But I don't know the in kernel governor?
>> Could you point a documentation of it?
>>
>

> Simply means that you call cpu_down / cpu_up directly in kernel base on the profiler.

I understood it.
When using sysfs, device_online/offline() changes dev->offline.
Therefore, this problem did not occur in my previous test.

Thanks,
Yasuaki Ishimatsu


>
>> Thanks,
>> Yasuaki Ishimatsu
>>
>>>
>>>> Thanks,
>>>> Yasuaki Ishimatsu
>>>>
>>>>>
>>>>>
>>>>> While with the patch, the cpu online nodes are kept up to date as
>>>>> the cpus are brought up/down:
>>>>>
>>>>> [root@br10p02 cpu]$ pwd
>>>>> /sys/devices/system/cpu
>>>>> [root@br10p02 cpu]$ cat online
>>>>> 0-39
>>>>> [root@br10p02 cpu]$ for n in {0..47} ; do test $( cat cpu$n/online )
>>>>> -eq 1 && echo -n "$n " ; done ; echo ""
>>>>> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
>>>>> 26
>>>>> 27 28 29 30 31 32 33 34 35 36 37 38 39
>>>>>
>>>>>
>>>>> Feel free to add
>>>>>
>>>>> Tested-by: Dan Streetman <ddstreet@ieee.org>
>>>>>
>>>>>>
>>>>>>> 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?
>>>>>>
>>>>>> As I know it use cpu_suspend to switch out a processor in IKS and
>>>>>> there is
>>>> no cpu hotplug notifier in this procedure.
>>>>>>
>>>>>>
>>>>>> Why do you need/want this notification?  What are you going to do
>>>>>> with this
>>>> information that you don't already have?
>>>>>>
>>>>>> The offline won't be updated if an in kernel hotplug governor plug
>>>>>> in / out
>>>> a core which cause the sysfs interface report a wrong status.
>>>>>>
>>>>>>
>>>>>> thanks,
>>>>>>
>>>>>> greg k-h
>>>>>>
>>>>>>
>>>>>> Best Regards,
>>>>>> Neil Zhang
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>> linux-kernel" in the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>> Please read the FAQ at  http://www.tux.org/lkml/
>>>>>
>>>>
>>>
>>>
>>> Best Regards,
>>> Neil Zhang
>>> \x04 {.n +       +%  lzwm  b 맲  r  zX  \x19\x1e w  {ay \x1dʇڙ ,j
>>>    f   h   z \x1e w
>>
>>     j:+v   w j m         zZ+     ݢj"  ! iO  z  v ^\x14\x04\x1a ^[m
>> nƊ  Y&
>>>
>>
>
>
> Best Regards,
> Neil Zhang
> \x13��칻\x1c�&�~�&�\x18��+-��ݶ\x17��w��˛���m�b��dz�ޖ)���w*\x1fjg���\x1e�����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a��\x7f��\x1e�G���h�\x0f�j:+v���w�٥>W����i�axP\x10j�m����\f-�\x1a+��d�_
>



  reply	other threads:[~2014-10-21  4:48 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
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 [this message]
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=5445E571.30107@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.com \
    --cc=ddstreet@ieee.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox