From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nathan Zimmer <nzimmer@sgi.com>,
linux-kernel@vger.kernel.org, John Stultz <johnstul@us.ibm.com>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH 2/2] timer_list: convert timer list to be a proper seq_file
Date: Wed, 27 Mar 2013 21:05:38 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1303272104150.22263@ionos> (raw)
In-Reply-To: <20130327121412.f589d0cc105843284e1d8eb5@linux-foundation.org>
On Wed, 27 Mar 2013, Andrew Morton wrote:
> On Tue, 26 Mar 2013 19:56:30 -0500 Nathan Zimmer <nzimmer@sgi.com> wrote:
> > +void sysrq_timer_list_show(void)
> > +{
> > + u64 now = ktime_to_ns(ktime_get());
> > + int cpu;
> > +
> > + timer_list_header(NULL, now);
> >
> > for_each_online_cpu(cpu)
>
> hm, it seems this code is taking the optimistic approach to CPU hotplug.
Right. It's not really relevant. The data structures are not going
away and this can cope with the fact that the cpu went away under us.
Thanks,
tglx
next prev parent reply other threads:[~2013-03-27 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.02.1303251651200.22263@ionos>
2013-03-27 0:56 ` [PATCH v5 0/2] timer_list: Fix /proc/timer_list failure on 4096 cpus Nathan Zimmer
2013-03-27 0:56 ` [PATCH 1/2] timer_list: split timer_list_show_tickdevices Nathan Zimmer
2013-04-17 19:57 ` [tip:timers/core] timer_list: Split timer_list_show_tickdevices tip-bot for Nathan Zimmer
2013-03-27 0:56 ` [PATCH 2/2] timer_list: convert timer list to be a proper seq_file Nathan Zimmer
2013-03-27 19:14 ` Andrew Morton
2013-03-27 20:05 ` Thomas Gleixner [this message]
2013-04-17 19:58 ` [tip:timers/core] timer_list: Convert " tip-bot for Nathan Zimmer
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=alpine.LFD.2.02.1303272104150.22263@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nzimmer@sgi.com \
--cc=sboyd@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome