public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: xip: disable PATCH_PHYS_VIRT for ARCH_MULTIPLATFORM when XIP
Date: Wed, 8 Feb 2017 18:55:04 +0000	[thread overview]
Message-ID: <20170208185504.GZ27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAMuHMdX=EZdPk+b3Vs21bSPq-wP10W=1WOag5FgBjVfvRzrDhQ@mail.gmail.com>

On Wed, Feb 08, 2017 at 07:46:55PM +0100, Geert Uytterhoeven wrote:
> Hi Russell,
> 
> On Wed, Feb 8, 2017 at 7:39 PM, Russell King - ARM Linux
> <linux@armlinux.org.uk> wrote:
> > On Wed, Feb 08, 2017 at 06:53:14PM +0100, Geert Uytterhoeven wrote:
> >> The problem is that "multiplatform" may mean one of two things:
> >>   1. Build a single kernel that can run on multiple platforms.
> >>      This is tricky when enabling XIP and/or NOMMU, as the physical parameters
> >>      must be compatible with all platforms. But building a kernel with the
> >>      right parameters is the responsibility of the user.
> >>      I.e. don't shoot yourself in the foot.
> >>   2. Your platform uses the arch/arm multiplatform framework.
> >>
> >> As everything is being migrated to 2, not allowing XIP and/or NOMMU on
> >> "multiplatform" is IMHO an insane limitation.
> >
> > There _isn't_ a framework.  What there is are a collection of Kconfig
> > options that multiplatform provides you that can also be selected by
> > any other configuration route.
> >
> > (2) really doesn't apply.
> >
> > The real issue is that board stuff ends up with a "depends on MULTI_xxx"
> > which needs to be bypassed.  That's pretty easy to do - I've done it as
> > a proof of concept a few years ago when this exact same thing came up
> > for !MMU, and since then I've been NAKing and refusing to apply patches
> > that try to re-use multiplat for !MMU.
> 
> So you mean this:
> 
> --- a/arch/arm/mach-shmobile/Kconfig
> +++ b/arch/arm/mach-shmobile/Kconfig
> @@ -31,7 +31,7 @@ config ARCH_RMOBILE
> 
>  menuconfig ARCH_RENESAS
>         bool "Renesas ARM SoCs"
> -       depends on ARCH_MULTI_V7 && MMU
> +       depends on MMU
>         select ARCH_DMA_ADDR_T_64BIT if ARM_LPAE
>         select ARCH_SHMOBILE
>         select ARCH_SHMOBILE_MULTI

I don't see the connection, sorry.  That looks totally broken to me,
because you now end up being able to select it when you have (eg)
something like ARCH_RPC enabled, and that's totally insane.

If you think the above patch in some way represents what I was saying,
that's wrong as well.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-02-08 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 17:22 [PATCH] ARM: xip: disable PATCH_PHYS_VIRT for ARCH_MULTIPLATFORM when XIP Chris Brandt
2017-02-08 17:44 ` Russell King - ARM Linux
2017-02-08 17:53   ` Geert Uytterhoeven
2017-02-08 18:39     ` Russell King - ARM Linux
2017-02-08 18:46       ` Geert Uytterhoeven
2017-02-08 18:55         ` Russell King - ARM Linux [this message]
2017-02-08 18:00   ` Chris Brandt
2017-02-08 18:52     ` Russell King - ARM Linux
2017-02-08 19:08       ` Chris Brandt

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=20170208185504.GZ27312@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --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