All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
	"Kumar Gala" <kumar.gala@linaro.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Nicolas Pitre" <nico@fluxnic.net>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Lukasz Stelmach" <l.stelmach@samsung.com>,
	"Bjorn Andersson" <bjorn.andersson@linaro.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"Chris Brandt" <chris.brandt@renesas.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Eric Miao" <eric.miao@nvidia.com>,
	"Dmitry Osipenko" <digetx@gmail.com>,
	"Laura Abbott" <labbott@redhat.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [PATCH/RFC v7] ARM: boot: Obtain start of physical memory from DTB
Date: Sat, 15 Aug 2020 10:16:21 +0100	[thread overview]
Message-ID: <20200815091620.GV1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CACRpkdaN22OjWsG+d-hp_NEw==3VVAsWHkFsiG642KmbjD_6Mg@mail.gmail.com>

On Fri, Aug 14, 2020 at 04:03:41PM +0200, Linus Walleij wrote:
> But TEXT_OFFSET is also used inside the kernel to offset the
> virtual memory. This means that when we set up the virtual
> memory split, the kernel virtual memory is also bumped by
> these 2 MB so the virtual memory starts at 0xC0208000
> instead of 0xC0008000 as is normal.

No.  Virtual memory starts without the 32KiB offset.  The L1 swapper
page table starts 16KiB below (or slightly more if LPAE) for example.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Kumar Gala" <kumar.gala@linaro.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Nicolas Pitre" <nico@fluxnic.net>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Lukasz Stelmach" <l.stelmach@samsung.com>,
	"Bjorn Andersson" <bjorn.andersson@linaro.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"Chris Brandt" <chris.brandt@renesas.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Eric Miao" <eric.miao@nvidia.com>,
	"Dmitry Osipenko" <digetx@gmail.com>,
	"Laura Abbott" <labbott@redhat.com>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [PATCH/RFC v7] ARM: boot: Obtain start of physical memory from DTB
Date: Sat, 15 Aug 2020 10:16:21 +0100	[thread overview]
Message-ID: <20200815091620.GV1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CACRpkdaN22OjWsG+d-hp_NEw==3VVAsWHkFsiG642KmbjD_6Mg@mail.gmail.com>

On Fri, Aug 14, 2020 at 04:03:41PM +0200, Linus Walleij wrote:
> But TEXT_OFFSET is also used inside the kernel to offset the
> virtual memory. This means that when we set up the virtual
> memory split, the kernel virtual memory is also bumped by
> these 2 MB so the virtual memory starts at 0xC0208000
> instead of 0xC0008000 as is normal.

No.  Virtual memory starts without the 32KiB offset.  The L1 swapper
page table starts 16KiB below (or slightly more if LPAE) for example.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-08-15 22:02 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 15:02 [PATCH/RFC v7] ARM: boot: Obtain start of physical memory from DTB Geert Uytterhoeven
2020-07-06 15:02 ` Geert Uytterhoeven
2020-07-07  6:50 ` Ard Biesheuvel
2020-07-07  6:50   ` Ard Biesheuvel
2020-07-07  7:39   ` Geert Uytterhoeven
2020-07-07  7:39     ` Geert Uytterhoeven
2020-07-07  7:45     ` Ard Biesheuvel
2020-07-07  7:45       ` Ard Biesheuvel
2020-07-07  7:58       ` Geert Uytterhoeven
2020-07-07  7:58         ` Geert Uytterhoeven
2020-07-07  8:35         ` Ard Biesheuvel
2020-07-07  8:35           ` Ard Biesheuvel
2020-07-07  8:40           ` Ard Biesheuvel
2020-07-07  8:40             ` Ard Biesheuvel
2020-07-07  9:09             ` Ard Biesheuvel
2020-07-07  9:09               ` Ard Biesheuvel
2020-07-20  9:45 ` Linus Walleij
2020-07-20  9:45   ` Linus Walleij
2020-07-20  9:53   ` Arnd Bergmann
2020-07-20  9:53     ` Arnd Bergmann
2020-07-21 12:58     ` Linus Walleij
2020-07-21 12:58       ` Linus Walleij
2020-07-23  1:19       ` Stephen Boyd
2020-07-23  1:19         ` Stephen Boyd
2020-08-03 10:18         ` Geert Uytterhoeven
2020-08-03 10:18           ` Geert Uytterhoeven
2020-08-03 19:46           ` Stephen Boyd
2020-08-03 19:46             ` Stephen Boyd
2020-08-14 14:03         ` Linus Walleij
2020-08-14 14:03           ` Linus Walleij
2020-08-14 14:06           ` Ard Biesheuvel
2020-08-14 14:06             ` Ard Biesheuvel
2020-08-15  9:18             ` Russell King - ARM Linux admin
2020-08-15  9:18               ` Russell King - ARM Linux admin
2020-08-15  8:28           ` Stephen Boyd
2020-08-15  8:28             ` Stephen Boyd
2020-08-15  9:16           ` Russell King - ARM Linux admin [this message]
2020-08-15  9:16             ` Russell King - ARM Linux admin
2020-08-15 10:28             ` Linus Walleij
2020-08-15 10:28               ` Linus Walleij

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=20200815091620.GV1551@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=chris.brandt@renesas.com \
    --cc=digetx@gmail.com \
    --cc=eric.miao@nvidia.com \
    --cc=geert+renesas@glider.be \
    --cc=kumar.gala@linaro.org \
    --cc=l.stelmach@samsung.com \
    --cc=labbott@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=masahiroy@kernel.org \
    --cc=nico@fluxnic.net \
    --cc=sboyd@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.