From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: nommu: re-enable use of vexpress without ARCH_MULTIPLATFORM
Date: Thu, 10 Jan 2013 08:20:57 -0500 [thread overview]
Message-ID: <50EEC039.3010905@codeaurora.org> (raw)
In-Reply-To: <201301101016.44708.arnd@arndb.de>
On 01/10/2013 05:16 AM, Arnd Bergmann wrote:
[...]
> I'd certainly be happy with
>
> * removing the intentional build error for ARCH_MULTIPLATFORM, but leaving
> it in for !ARCH_MULTIPLATFORM
> * having mach-virt enabled by default on ARCH_MULTIPLATFORM, and only
> visible for EXPERT.
> * making mach-virt compatible with all CPUs starting with ARM7.
>
> That would make allnoconfig, allyesconfig and allmodconfig work (besides
> all the other bugs) on qemu at least, avoid build errors with randconfig
> and make it hard enough to build a kernel that doesn't run on anything.
If this is going to be the approach, I would like to once again suggest that
paths, configuration options, and compatibility strings along the lines of
"mach-genericarmv7", "Generic ARMv7 Machine", and "linux,genericarmv7" be
considered in place of "mach-virt", "Dummy Virtual Machine" and
"linux,dummy-virt", respectively.
Virtualization may have been the initial motivation for creating mach-virt,
but the code is clearly also immediately applicable to other environments such
as simulation/emulation, and sticking to a name like "Dummy Virtual Machine"
makes it sound like such usage is erroneous.
Regards,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by
the Linux Foundation
next prev parent reply other threads:[~2013-01-10 13:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 18:15 [PATCH] ARM: nommu: re-enable use of vexpress without ARCH_MULTIPLATFORM Jonathan Austin
2013-01-09 18:30 ` Nicolas Pitre
2013-01-09 18:41 ` Will Deacon
2013-01-09 19:17 ` [PATCH v2] " Jonathan Austin
2013-01-09 18:43 ` [PATCH] " Arnd Bergmann
2013-01-09 18:54 ` Nicolas Pitre
2013-01-09 20:22 ` Arnd Bergmann
2013-01-09 20:39 ` Rob Herring
2013-01-09 20:48 ` Russell King - ARM Linux
2013-01-10 3:51 ` Rob Herring
2013-01-10 10:16 ` Arnd Bergmann
2013-01-10 13:20 ` Christopher Covington [this message]
2013-01-10 13:45 ` Marc Zyngier
2013-01-09 21:09 ` Nicolas Pitre
2013-01-09 21:00 ` Nicolas Pitre
2013-01-09 21:15 ` Arnd Bergmann
2013-01-09 21:37 ` Nicolas Pitre
2013-01-09 22:14 ` Arnd Bergmann
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=50EEC039.3010905@codeaurora.org \
--to=cov@codeaurora.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).