From: Robin Holt <holt@sgi.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Robin Holt <holt@sgi.com>, Russ Anderson <rja@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Shawn Guo <shawn.guo@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH] Do not force shutdown/reboot to boot cpu.
Date: Thu, 11 Apr 2013 06:34:13 -0500 [thread overview]
Message-ID: <20130411113412.GP3658@sgi.com> (raw)
In-Reply-To: <20130411085751.GD11824@gmail.com>
> Ok, so it looks profilable.
>
> The result above is not surprising: most CPUs sit in idle and don't do anything,
> while the loop goes on, right?
>
> The interesting thing to profile would be the parallel bring-down, with the
> simplest global lock solution you mentioned. In that case most CPUs should be
> doing 'something' all the time - maybe spinning on the lock, maybe something else,
> right?
Again, mostly looks idle.
Events: 5M cycles
31.69% swapper [kernel.kallsyms] [k] update_cfs_rq_blocked_load
14.22% swapper [kernel.kallsyms] [k] load_balance
12.95% swapper [kernel.kallsyms] [k] ktime_get
4.64% swapper [kernel.kallsyms] [k] idle_cpu
3.46% swapper [kernel.kallsyms] [k] uv_read_rtc
2.26% swapper [kernel.kallsyms] [k] ktime_get_update_offsets
2.25% swapper [kernel.kallsyms] [k] rcu_check_callbacks
1.72% swapper [kernel.kallsyms] [k] _raw_spin_lock_irqsave
1.57% swapper [kernel.kallsyms] [k] native_write_msr_safe
1.53% swapper [kernel.kallsyms] [k] native_safe_halt
1.52% swapper [kernel.kallsyms] [k] apic_timer_interrupt
1.52% swapper [kernel.kallsyms] [k] update_blocked_averages
1.51% swapper [kernel.kallsyms] [k] __lock_text_start
1.48% swapper [kernel.kallsyms] [k] rcu_process_gp_end
1.40% swapper [kernel.kallsyms] [k] rcu_process_callbacks
1.19% reboot [kernel.kallsyms] [k] kmem_cache_alloc_node
0.63% swapper [kernel.kallsyms] [k] check_for_new_grace_period
0.58% swapper [kernel.kallsyms] [k] rebalance_domains
0.55% swapper [kernel.kallsyms] [k] cpumask_next_and
0.54% swapper [kernel.kallsyms] [k] __tick_nohz_idle_enter
0.53% swapper [kernel.kallsyms] [k] perf_adjust_freq_unthr_context
0.49% swapper [kernel.kallsyms] [k] _raw_spin_lock
Robin
next prev parent reply other threads:[~2013-04-11 11:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 19:37 [PATCH] Do not force shutdown/reboot to boot cpu Robin Holt
2013-04-08 15:57 ` Ingo Molnar
2013-04-08 16:11 ` H. Peter Anvin
2013-04-08 16:59 ` Robin Holt
2013-04-10 11:16 ` Ingo Molnar
2013-04-10 14:01 ` Robin Holt
2013-04-10 15:10 ` Linus Torvalds
2013-04-10 15:29 ` Russ Anderson
2013-04-10 16:59 ` Ingo Molnar
2013-04-10 17:14 ` Robin Holt
2013-04-10 17:22 ` Ingo Molnar
2013-04-10 17:55 ` Robin Holt
2013-04-10 19:00 ` Robin Holt
2013-04-11 8:57 ` Ingo Molnar
2013-04-11 11:34 ` Robin Holt [this message]
2013-04-11 12:00 ` Ingo Molnar
2013-04-11 12:03 ` Robin Holt
2013-04-11 12:08 ` Robin Holt
2013-04-11 12:14 ` Ingo Molnar
2013-04-10 17:58 ` H. Peter Anvin
2013-04-10 23:02 ` Russ Anderson
2013-04-10 22:29 ` Russ Anderson
2013-04-11 5:31 ` Paul Mackerras
2013-04-11 12:45 ` Bulk CPU Hotplug (Was Re: [PATCH] Do not force shutdown/reboot to boot cpu.) Srivatsa S. Bhat
2013-04-11 13:48 ` Robin Holt
2013-04-12 5:37 ` Ingo Molnar
2013-04-12 6:09 ` Srivatsa S. Bhat
2013-04-12 9:31 ` Robin Holt
2013-04-12 10:01 ` Robin Holt
2013-04-13 16:30 ` Oleg Nesterov
2013-04-15 16:04 ` Robin Holt
2013-04-15 16:09 ` Oleg Nesterov
2013-04-15 16:10 ` Robin Holt
2013-04-13 17:01 ` Srivatsa S. Bhat
2013-04-15 10:16 ` Ingo Molnar
2013-04-15 12:02 ` Robin Holt
2013-04-15 15:59 ` Robin Holt
2013-04-16 9:40 ` Ingo Molnar
2013-04-11 14:23 ` Russ Anderson
2013-04-11 14:45 ` Srivatsa S. Bhat
2013-04-11 20:08 ` Russ Anderson
2013-04-11 20:17 ` Srivatsa S. Bhat
2013-04-11 21:08 ` Robin Holt
2013-04-08 16:54 ` [PATCH] Do not force shutdown/reboot to boot cpu Robin Holt
2013-04-08 17:07 ` Russ Anderson
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=20130411113412.GP3658@sgi.com \
--to=holt@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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.