linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Itaru Kitayama <itaru.kitayama@linux.dev>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, broonie@kernel.org,
	catalin.marinas@arm.com, james.morse@arm.com, will@kernel.org
Subject: Re: [PATCH 0/3] arm64: cleanup DAIF handling for EL0 returns
Date: Thu, 8 Feb 2024 11:28:32 +0900	[thread overview]
Message-ID: <ZcQ8UKRNz0TLvJRB@vm3> (raw)
In-Reply-To: <20240206123848.1696480-1-mark.rutland@arm.com>

On Tue, Feb 06, 2024 at 12:38:45PM +0000, Mark Rutland wrote:
> Hi,
> 
> These patches rework DAIF handling when returning to EL0, simplifiying
> the logic in do_notify_resume() and allowing Debug + SError to be
> unmasked for a little longer during exception return.
> 
> My primary motivation for these changes is to centralize entry/exit DAIF
> management within entry-common.c, as this will allow entry/exit
> sequences to be specialised, and make it much easier to add support for
> FEAT_NMI. With specialized entry DAIF management, it will also be
> possible to simplify local_daif_{save,restore}() and
> local_irq_{save,restore}().
> 
> I'm sending this out on its own as (IMO) it's a nice cleanup on its own,
> and I don't believe that I'll have the remainder of the DAIF rework
> ready for this cycle.
> 
> The series is based on v6.8-rc3.
> 
> Mark.
> 
> Mark Rutland (3):
>   arm64: Simplify do_notify_resume() DAIF masking
>   arm64: Move do_notify_resume() to entry-common.c
>   arm64: Unmask Debug + SError in do_notify_resume()
> 
>  arch/arm64/include/asm/exception.h |  2 +-
>  arch/arm64/kernel/entry-common.c   | 36 ++++++++++++++++++++++++++-
>  arch/arm64/kernel/signal.c         | 39 ++----------------------------
>  3 files changed, 38 insertions(+), 39 deletions(-)

Boot tested on RevC FVP and kselftest arm64 subcategory runs without an error
on RevC FVP too.

Itaru.

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

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

  parent reply	other threads:[~2024-02-08  2:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 12:38 [PATCH 0/3] arm64: cleanup DAIF handling for EL0 returns Mark Rutland
2024-02-06 12:38 ` [PATCH 1/3] arm64: Simplify do_notify_resume() DAIF masking Mark Rutland
2024-02-08 14:04   ` Mark Brown
2024-02-06 12:38 ` [PATCH 2/3] arm64: Move do_notify_resume() to entry-common.c Mark Rutland
2024-02-06 12:52   ` Mark Brown
2024-02-27  3:25   ` Liao, Chang
2024-02-27 10:24     ` Mark Rutland
2024-02-06 12:38 ` [PATCH 3/3] arm64: Unmask Debug + SError in do_notify_resume() Mark Rutland
2024-02-08 14:08   ` Mark Brown
2024-02-08  2:28 ` Itaru Kitayama [this message]
2024-02-08 12:38   ` [PATCH 0/3] arm64: cleanup DAIF handling for EL0 returns Mark Rutland
2024-02-08 20:53     ` Itaru Kitayama
2024-02-20 18:19 ` Catalin Marinas

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=ZcQ8UKRNz0TLvJRB@vm3 \
    --to=itaru.kitayama@linux.dev \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).