All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: NOMMU: Fix exc_ret for stack frame type
Date: Tue, 15 Oct 2024 08:02:19 +0800	[thread overview]
Message-ID: <Zw2xC39-YkNlL6qT@xhacker> (raw)
In-Reply-To: <87ba9595-6229-4a79-aa65-d76567ef708e@arm.com>

On Mon, Oct 14, 2024 at 10:54:00AM +0100, Vladimir Murzin wrote:
> On 10/13/24 14:25, Jisheng Zhang wrote:
> > commit 72cd4064fcca ("ARM: 8830/1: NOMMU: Toggle only bits in
> > EXC_RETURN we are really care of") only sets BIT[3] for Thread mode
> > and BIT[2] for PSP, it leaves BIT[4] untouched. But there's such a
> > case: the pre-linux env makes use of FPU then the BIT[4] in 'lr' is
> > cleared, this brings an umatch issue since the NOMMU kernel doesn't
> 
> Can pre-linux env disable FPU before passing control to kernel (which
> is, as correctly pointed, doesn't know how to use FPU)?

IIRC, I did a experiment like this by clearing the SCB CPACR related
bits, but the stack frame type is still not correct. I searched in the
armv8m arm or cortex-mN's TRM I didn't find the relation between the
returned "lr" and the pre FPU usage.

What's more, IMHO, kernel needs to use the correct exc_ret no matter
the pre-linux env does, I.E if kernel/userspace supports FPU, then
clear BIT[4]; if no, set BIT[4].

PS: this is a regression: before the commit, the have-used-fpu pre-linux
env + linux nommu combination works; after the commit, it fails to
execute the init due to wrong stack frame type.

Thanks


  reply	other threads:[~2024-10-15  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 13:25 [PATCH] ARM: NOMMU: Fix exc_ret for stack frame type Jisheng Zhang
2024-10-14  9:54 ` Vladimir Murzin
2024-10-15  0:02   ` Jisheng Zhang [this message]
2024-10-22 10:37     ` Vladimir Murzin

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=Zw2xC39-YkNlL6qT@xhacker \
    --to=jszhang@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=vladimir.murzin@arm.com \
    /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.