From: mats.liljegren@enea•com (Mats Liljegren)
To: linux-arm-kernel@lists•infradead.org
Subject: Porting 3.8-rc4-nohz3 to ARM (PandaBoard)
Date: Mon, 4 Feb 2013 21:02:39 +0100 [thread overview]
Message-ID: <20130204200238.GA16718@enea.se> (raw)
Hi Frederic,
(Sorry for the re-post, I spelled the mailing list wrong...)
I want to port dynticks patches 3.8-rc4-nohz3 to ARM architecture, and try it out on the PandaBoard. Initially this is for evaluating it, but if it looks promising I'd like to upstream this.
As far as I can see the first thing to do is to implement virtual time accounting. After an initial look at the patches done for ia64, it doesn't look too difficult.
Are there any caveats I should be aware of?
Has anyone else started any work in this area that I could co-operate with?
Regards
Mats Liljegren
next reply other threads:[~2013-02-04 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 20:02 Mats Liljegren [this message]
2013-02-08 16:31 ` Porting 3.8-rc4-nohz3 to ARM (PandaBoard) Frederic Weisbecker
2013-02-08 17:04 ` Geoff Levand
2013-02-08 19:10 ` Mats Liljegren
2013-02-11 19:03 ` Mats Liljegren
2013-02-14 23:08 ` Kevin Hilman
2013-02-20 16:12 ` Frederic Weisbecker
2013-02-20 18:28 ` Mats Liljegren
2013-02-21 16:19 ` Frederic Weisbecker
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=20130204200238.GA16718@enea.se \
--to=mats.liljegren@enea$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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