linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH 0/5] context_tracking: prerequisites for ARM support
Date: Wed, 20 Feb 2013 11:41:37 -0800	[thread overview]
Message-ID: <1361389302-11968-1-git-send-email-khilman@linaro.org> (raw)

Frederic,

Here is a first pass at some changes needed in order to add ARM
support.

I have another series coming that instruments the syscalls, exceptions
etc. on ARM also, but this one is just to get some prerequisites out
for broader discussion.

This series applies on top of your 3.8-rc6-nohz4 branch, and is also available
here: 

git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux.git wip/arm-nohz/prereq

I'm aware of the >80 column warnings from checkpatch on the atomic64
conversion patch, but wanted to get some feedback on this approach
before fixing all those up.  Maybe some simpler wrappers in
kernel_stat.h would make this a bit cleaner?

Kevin


Kevin Hilman (5):
  context tracking: conditionalize guest support based on CONFIG_KVM
  kernel_cpustat: convert to atomic 64-bit accessors
  virt CPU accounting: Kconfig: drop 64-bit requirment
  cputime: use do_div() for nsec resolution conversion helpers
  ARM: Kconfig: allow virt CPU accounting

 arch/arm/Kconfig                    |  1 +
 fs/proc/stat.c                      | 36 +++++++++++++-------------
 fs/proc/uptime.c                    |  2 +-
 include/asm-generic/cputime_nsecs.h | 51 +++++++++++++++++++++++++++----------
 include/linux/kernel_stat.h         |  2 +-
 init/Kconfig                        |  2 +-
 kernel/context_tracking.c           |  4 +++
 kernel/sched/core.c                 | 10 ++++----
 kernel/sched/cputime.c              | 24 ++++++++---------
 9 files changed, 80 insertions(+), 52 deletions(-)

-- 
1.8.1.2

             reply	other threads:[~2013-02-20 19:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 19:41 Kevin Hilman [this message]
2013-02-20 19:41 ` [RFC/PATCH 1/5] context tracking: conditionalize guest support based on CONFIG_KVM Kevin Hilman
2013-02-22 13:27   ` Frederic Weisbecker
2013-02-26 19:29     ` Kevin Hilman
2013-02-26 22:13       ` Namhyung Kim
2013-02-27 14:24         ` Kevin Hilman
2013-02-27 15:21           ` Frederic Weisbecker
2013-02-20 19:41 ` [RFC/PATCH 2/5] kernel_cpustat: convert to atomic 64-bit accessors Kevin Hilman
2013-02-21 19:38   ` Kevin Hilman
2013-02-21 21:53     ` Frederic Weisbecker
2013-02-21 21:54       ` Frederic Weisbecker
2013-02-22  5:57         ` Kevin Hilman
2013-02-21 21:58       ` Russell King - ARM Linux
2013-02-21 22:15         ` Frederic Weisbecker
2013-02-20 19:41 ` [RFC/PATCH 3/5] virt CPU accounting: Kconfig: drop 64-bit requirment Kevin Hilman
2013-02-20 19:41 ` [RFC/PATCH 4/5] cputime: use do_div() for nsec resolution conversion helpers Kevin Hilman
2013-02-21 16:24   ` Frederic Weisbecker
2013-02-21 17:58   ` Namhyung Kim
2013-02-21 19:21     ` Kevin Hilman
2013-02-26 15:21       ` Frederic Weisbecker
2013-02-20 19:41 ` [RFC/PATCH 5/5] ARM: Kconfig: allow virt CPU accounting 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=1361389302-11968-1-git-send-email-khilman@linaro.org \
    --to=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).