All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Alison Wang <alison.wang@nxp.com>, Nishanth Menon <nm@ti.com>,
	Priyanka Singh <priyanka.singh@nxp.com>,
	Peter Hoyes <Peter.Hoyes@arm.com>,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH 0/6] armv8: fixes and cleanups
Date: Sun, 09 Jan 2022 20:14:57 +0100	[thread overview]
Message-ID: <58184c1f6930de2149c15f716f4745c1@walle.cc> (raw)
In-Reply-To: <20220109173009.25522-1-andre.przywara@arm.com>

Am 2022-01-09 18:30, schrieb Andre Przywara:
> Hi,
> 
> I was looking into the arm64 boot code lately and stumbled upon some
> issues. Also Nishanth brought back memories of a lengthy debug session,
> which was caused due to U-Boot keeping SErrors masked. As the resulting
> patches are all somewhat related, I gathered this series here to 
> address
> those problems.
> 
> Patches 1 to 3 address exception handling issues, with the SError
> enablement being the most prominent fix here.
> Patch 4 cleans up asm/io.h. This was on the list before[1], but was
> somehow lost when it was intercepted by a shorter version of itself.
> Patches 5 and 6 clean up some unnecessarily complicated AArch64 
> assembly
> code.
> 
> I did only some light testing, as some code paths do not apply to 
> boards
> I have (ARMV8_MULTIENTRY).
> 
> Please have a look and test!

FWIW, tested on kontron sl28 board with and without TF-A. U-Boot is 
either
running in EL3 or EL2.

Tested-by: Michael Walle <michael@walle.cc>

-michael

      parent reply	other threads:[~2022-01-09 19:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 17:30 [PATCH 0/6] armv8: fixes and cleanups Andre Przywara
2022-01-09 17:30 ` [PATCH 1/6] cmd: exception: arm64: fix undefined, add faults Andre Przywara
2022-01-09 18:43   ` Heinrich Schuchardt
2022-01-09 19:08   ` Heinrich Schuchardt
2022-01-09 21:31     ` Andre Przywara
2022-01-09 22:19       ` Heinrich Schuchardt
2022-01-09 22:35         ` Andre Przywara
2022-01-09 22:47           ` Mark Kettenis
2022-01-09 23:19             ` Andre Przywara
2022-01-09 23:23               ` Heinrich Schuchardt
2022-01-09 23:49                 ` Andre Przywara
2022-01-10 22:37               ` Mark Kettenis
2022-01-11 10:28                 ` Andre Przywara
2022-01-09 17:30 ` [PATCH 2/6] armv8: Always unmask SErrors Andre Przywara
2022-01-09 17:30 ` [PATCH 3/6] armv8: Force SP_ELx stack pointer usage Andre Przywara
2022-01-09 17:30 ` [PATCH 4/6] arm: Clean up asm/io.h Andre Przywara
2022-01-09 21:39   ` Andre Przywara
2022-01-13  6:44     ` Leo Liang
2022-01-09 17:30 ` [PATCH 5/6] armv8: Simplify switch_el macro Andre Przywara
2022-01-09 17:30 ` [PATCH 6/6] armv8: Fix and simplify branch_if_master/branch_if_slave Andre Przywara
2022-01-09 19:14 ` Michael Walle [this message]

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=58184c1f6930de2149c15f716f4745c1@walle.cc \
    --to=michael@walle.cc \
    --cc=Peter.Hoyes@arm.com \
    --cc=alison.wang@nxp.com \
    --cc=andre.przywara@arm.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=nm@ti.com \
    --cc=priyanka.singh@nxp.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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.