All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@linaro.org>
To: Mats Liljegren <mats.liljegren@enea.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	Namhyung Kim <namhyung.kim@lge.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Gleb Natapov <gleb@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [GIT PULL] cputime: Full dynticks task/cputime accounting v7
Date: Fri, 15 Feb 2013 07:06:39 -0800	[thread overview]
Message-ID: <878v6p7h1c.fsf@linaro.org> (raw)
In-Reply-To: <20130215140429.GA4322@enea.se> (Mats Liljegren's message of "Fri, 15 Feb 2013 15:04:29 +0100")

Mats Liljegren <mats.liljegren@enea.com> writes:

[...]

>> To give it a try, below is a quick patch to convert kernel_cpustat to
>> atomic64.  I only got as far as compile testing and basic boot testing
>> on a 32-bit ARM platform, but let me know if this is the right
>> direction.

[...]

> I had to do some changes to get it to compile. You can check my patch below
> and see whether I got it all wrong...

Your changes are fine, and there are sure to be a few more that I missed
for various config options (your are because of CGROUP_CPUACCT which I
didn't have enabled here.)  I'll do a more thorough patch when I hear
from Frederic if this is a direction he's OK with.

Thanks for the changes,

Kevin

  reply	other threads:[~2013-02-15 15:06 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 19:03 [GIT PULL] cputime: Full dynticks task/cputime accounting v7 Frederic Weisbecker
2013-01-28 19:03 ` [PATCH 1/8] context_tracking: Export context state for generic vtime Frederic Weisbecker
2013-01-28 19:03 ` [PATCH 2/8] cputime: Librarize per nsecs resolution cputime definitions Frederic Weisbecker
2013-02-14 19:49   ` Kevin Hilman
2013-02-20 16:07     ` Frederic Weisbecker
2013-01-28 19:04 ` [PATCH 3/8] cputime: Move default nsecs_to_cputime() to jiffies based cputime file Frederic Weisbecker
2013-01-28 19:04 ` [PATCH 4/8] cputime: Generic on-demand virtual cputime accounting Frederic Weisbecker
2013-02-08  3:07   ` Stephen Rothwell
2013-02-08  3:07     ` Stephen Rothwell
2013-02-08  3:14     ` Stephen Rothwell
2013-02-08  3:14       ` Stephen Rothwell
2013-02-08  3:19       ` [PATCH] cputime: restore CPU_ACCOUNTING config defaults for PPC64 Stephen Rothwell
2013-02-08  3:19         ` Stephen Rothwell
2013-02-08 15:18         ` [tip:sched/core] cputime: Restore " tip-bot for Stephen Rothwell
2013-02-08 15:18           ` tip-bot for Stephen Rothwell
2013-02-08 14:31       ` [PATCH 4/8] cputime: Generic on-demand virtual cputime accounting Frederic Weisbecker
2013-02-08 14:31         ` Frederic Weisbecker
2013-01-28 19:04 ` [PATCH 5/8] cputime: Allow dynamic switch between tick/virtual based " Frederic Weisbecker
2013-01-28 19:04 ` [PATCH 6/8] cputime: Use accessors to read task cputime stats Frederic Weisbecker
2013-01-28 19:04 ` [PATCH 7/8] kvm: Prepare to add generic guest entry/exit callbacks Frederic Weisbecker
2013-01-28 19:04 ` [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs Frederic Weisbecker
2013-01-28 21:51   ` Sedat Dilek
2013-01-30 21:57     ` Sedat Dilek
2013-01-31  0:38     ` Frederic Weisbecker
2013-01-31  7:24       ` Sedat Dilek
2013-01-31 10:12         ` Frederic Weisbecker
2013-01-31 10:30           ` Sedat Dilek
2013-01-31 16:29             ` Frederic Weisbecker
2013-01-28 19:18 ` [GIT PULL] cputime: Full dynticks task/cputime accounting v7 Christoph Lameter
2013-01-28 19:21   ` Frederic Weisbecker
2013-01-28 20:14     ` Christoph Lameter
2013-01-29  1:42       ` Frederic Weisbecker
2013-01-29  0:02 ` Steven Rostedt
2013-01-29  1:36   ` Frederic Weisbecker
2013-01-29  2:36   ` Steven Rostedt
2013-01-29  2:39     ` Frederic Weisbecker
2013-01-29  2:44       ` Steven Rostedt
2013-01-29  3:29         ` Frederic Weisbecker
2013-01-29  4:38           ` Steven Rostedt
2013-01-29 15:12             ` Frederic Weisbecker
2013-01-29 16:46               ` Steven Rostedt
2013-01-29 16:55                 ` Frederic Weisbecker
2013-01-29 17:08                   ` Steven Rostedt
2013-01-29 21:26     ` Steven Rostedt
2013-01-29 21:37       ` Frederic Weisbecker
2013-02-15  1:55 ` Kevin Hilman
2013-02-15 14:04   ` Mats Liljegren
2013-02-15 15:06     ` Kevin Hilman [this message]
2013-02-20 15:53     ` Frederic Weisbecker
2013-02-20 17:53       ` Kevin Hilman
2013-02-20 15:44   ` Frederic Weisbecker
2013-02-20 18:48     ` Kevin Hilman

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=878v6p7h1c.fsf@linaro.org \
    --to=khilman@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=fenghua.yu@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=gleb@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mats.liljegren@enea.com \
    --cc=mingo@kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=namhyung.kim@lge.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sedat.dilek@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=zhong@linux.vnet.ibm.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.