From: jonathan.austin@arm.com (Jonathan Austin)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] Interested in R/M-class (!MMU), automated testing
Date: Fri, 02 Aug 2013 19:23:57 +0100 [thread overview]
Message-ID: <51FBF93D.8040707@arm.com> (raw)
Hello,
I'm keen to attend the ARM Kernel summit this year. I haven't got a
specific proposal, but I'd really like to talk to people about !MMU,
R/M-class (which is where I've done most of my work so far) and
automation of testing on ARM hardware.
I'm pretty new to the kernel and based on the accounts of other hackers,
getting to the ARM (mini) summits and meeting people in person is a
great way to get more involved, so if there are places I'd love to come.
Specifically, after the merging of my MPU support for R-class and
Uwe/Catalin's M-class patches, I'd like to talk about:
- Whether we can make better use of the MPU/actually have real
kernel/userspace protection even without an MMU, and how not to kill
performance doing this
- Whether we want to do MPU support for M-class
- How we can get more eyes on the !MMU code in the kernel - is it
because nobody's got R/M hardware? R/M isn?t interesting to people so
far? etc
- Ways to do more automated testing of ARM kernels, including hearing
from other people what they use to build/boot/test/benchmark their
code (perhaps even get a discussion going about using the diverse
range of hardware people have around put to use as test-machines).
Thanks,
Jonny
next reply other threads:[~2013-08-02 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 18:23 Jonathan Austin [this message]
2013-08-04 12:25 ` [ARM ATTEND] Interested in R/M-class (!MMU), automated testing Robert Schwebel
2013-08-05 6:49 ` Olof Johansson
2013-08-05 6:49 ` Olof Johansson
2013-08-05 10:08 ` Jonathan Austin
2013-08-05 17:58 ` [Ksummit-2013-discuss] " Steven Rostedt
2013-08-08 10:22 ` Jonathan Austin
2013-08-06 23:44 ` Aaro Koskinen
2013-08-07 0:06 ` [Ksummit-2013-discuss] " Guenter Roeck
2013-08-07 0:28 ` Olof Johansson
2013-08-07 1:10 ` Fabio Estevam
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=51FBF93D.8040707@arm.com \
--to=jonathan.austin@arm.com \
--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).