mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: rcz@pengutronix.de
Subject: [PATCH 0/4] of: request reserved memory regions so other code can't
Date: Thu,  9 Jun 2022 07:43:38 +0200	[thread overview]
Message-ID: <20220609054342.661505-1-a.fatoum@pengutronix.de> (raw)

This series pulls out some parts from Rouven's eXecute Never series[1]
to improve reserved memory support.

Changes are described beneath each patch. This series was prompted by
Raspberry Pi 64-bit rework: barebox placed the kernel at address 0,
which is reserved for the spin table thereby breaking multicore boot.

Now that reserved memory regions are requested, they are skipped over
when determining a load address.

This may induce breakage if reserved memory regions are being used
by existing code that expects exclusive access. nvmem-rmem is one
such user that's fixed here. If you know of more, please tell.

[1]: https://lore.barebox.org/barebox/20210803094418.475609-1-r.czerwinski@pengutronix.de/

Ahmad Fatoum (1):
  nvmem: rmem: get, don't request, memory region

Rouven Czerwinski (3):
  of: reserve: mark runtime firmware code regions specially
  of: add of_get_reserve_map stub for !CONFIG_OFTREE
  of: request reserved memory regions so other code can't

 arch/arm/cpu/sm.c              |  3 ++-
 arch/arm/cpu/start.c           |  3 ++-
 arch/arm/mach-layerscape/ppa.c |  2 +-
 common/bootm.c                 |  3 ++-
 common/memory.c                | 21 +++++++++++++++++++--
 drivers/nvmem/rmem.c           |  2 +-
 drivers/of/Makefile            |  1 +
 drivers/of/fdt.c               | 18 +++++++++++++-----
 drivers/video/fb.c             |  3 ++-
 drivers/video/simplefb-fixup.c |  2 +-
 fs/pstore/ram.c                |  3 ++-
 include/of.h                   | 15 +++++++++++++--
 12 files changed, 59 insertions(+), 17 deletions(-)

-- 
2.30.2


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


             reply	other threads:[~2022-06-09  5:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  5:43 Ahmad Fatoum [this message]
2022-06-09  5:43 ` [PATCH 1/4] nvmem: rmem: get, don't request, memory region Ahmad Fatoum
2022-06-09  5:43 ` [PATCH 2/4] of: reserve: mark runtime firmware code regions specially Ahmad Fatoum
2022-06-09  8:05   ` Sascha Hauer
2022-06-09  8:17     ` Ahmad Fatoum
2022-06-09  5:43 ` [PATCH 3/4] of: add of_get_reserve_map stub for !CONFIG_OFTREE Ahmad Fatoum
2022-06-09  9:14   ` Sascha Hauer
2022-06-09  5:43 ` [PATCH 4/4] of: request reserved memory regions so other code can't Ahmad Fatoum
2022-06-09  8:31   ` [PATCH] fixup! " Ahmad Fatoum
2022-06-09  8:31   ` [PATCH 4/4] " Sascha Hauer
2022-06-09  8:36     ` Ahmad Fatoum

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=20220609054342.661505-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=rcz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox