From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: nommu: re-enable use of vexpress without ARCH_MULTIPLATFORM
Date: Thu, 10 Jan 2013 13:45:03 +0000 [thread overview]
Message-ID: <50EEC5DF.1010607@arm.com> (raw)
In-Reply-To: <50EEC039.3010905@codeaurora.org>
On 10/01/13 13:20, Christopher Covington wrote:
> 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.
mach-virt requires GIC, Architected Timers and PSCI. I'm not prepared to
impose these requirements on all future v7 platforms yet.
When we reach a point where we have a completely DT driven setup,
without any explicit hook, I'll be happy to add new compatibility strings.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2013-01-10 13:45 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
2013-01-10 13:45 ` Marc Zyngier [this message]
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=50EEC5DF.1010607@arm.com \
--to=marc.zyngier@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).