From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: elver@google.com, paulmck@kernel.org, peterz@infradead.org,
catalin.marinas@arm.com, Will Deacon <will@kernel.org>,
james.morse@arm.com, kernel-team@android.com, dvyukov@google.com
Subject: Re: [PATCHv2 00/11] arm64: entry lockdep/rcu/tracing fixes
Date: Mon, 30 Nov 2020 13:52:11 +0000 [thread overview]
Message-ID: <160673829883.2674613.7469554321959251331.b4-ty@kernel.org> (raw)
In-Reply-To: <20201130115950.22492-1-mark.rutland@arm.com>
On Mon, 30 Nov 2020 11:59:39 +0000, Mark Rutland wrote:
> [series changelog at the end]
>
> Dmitry and Marco both reported some weirdness with lockdep on arm64 erroneously
> reporting the hardware IRQ state, and inexplicable RCU stalls:
>
> https://lore.kernel.org/r/CACT4Y+aAzoJ48Mh1wNYD17pJqyEcDnrxGfApir=-j171TnQXhw@mail.gmail.com
> https://lore.kernel.org/r/20201119193819.GA2601289@elver.google.com
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[01/11] arm64: syscall: exit userspace before unmasking exceptions
https://git.kernel.org/arm64/c/ca1314d73eed
[02/11] arm64: mark idle code as noinstr
https://git.kernel.org/arm64/c/114e0a684753
[03/11] arm64: entry: mark entry code as noinstr
https://git.kernel.org/arm64/c/da1926764832
[04/11] arm64: entry: move enter_from_user_mode to entry-common.c
https://git.kernel.org/arm64/c/2f911d494f3f
[05/11] arm64: entry: prepare ret_to_user for function call
https://git.kernel.org/arm64/c/3cb5ed4d76c1
[06/11] arm64: entry: move el1 irq/nmi logic to C
https://git.kernel.org/arm64/c/105fc3352077
[07/11] arm64: entry: fix non-NMI user<->kernel transitions
https://git.kernel.org/arm64/c/23529049c684
[08/11] arm64: ptrace: prepare for EL1 irq/rcu tracking
https://git.kernel.org/arm64/c/1ec2f2c05b2a
[09/11] arm64: entry: fix non-NMI kernel<->kernel transitions
https://git.kernel.org/arm64/c/7cd1ea1010ac
[10/11] arm64: entry: fix NMI {user, kernel}->kernel transitions
https://git.kernel.org/arm64/c/f0cd5ac1e4c5
[11/11] arm64: entry: fix EL1 debug transitions
https://git.kernel.org/arm64/c/2a9b3e6ac69a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-30 13:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 11:59 [PATCHv2 00/11] arm64: entry lockdep/rcu/tracing fixes Mark Rutland
2020-11-30 11:59 ` [PATCHv2 01/11] arm64: syscall: exit userspace before unmasking exceptions Mark Rutland
2020-11-30 11:59 ` [PATCHv2 02/11] arm64: mark idle code as noinstr Mark Rutland
2020-11-30 11:59 ` [PATCHv2 03/11] arm64: entry: mark entry " Mark Rutland
2020-11-30 11:59 ` [PATCHv2 04/11] arm64: entry: move enter_from_user_mode to entry-common.c Mark Rutland
2020-11-30 11:59 ` [PATCHv2 05/11] arm64: entry: prepare ret_to_user for function call Mark Rutland
2020-12-17 17:57 ` Guenter Roeck
2020-12-17 18:38 ` Catalin Marinas
2020-11-30 11:59 ` [PATCHv2 06/11] arm64: entry: move el1 irq/nmi logic to C Mark Rutland
2021-05-06 8:28 ` He Ying
2021-05-06 9:16 ` Mark Rutland
[not found] ` <e3843e03-173e-10a6-5b14-0d8c14219e09@huawei.com>
2021-05-06 10:58 ` Mark Rutland
2021-05-07 3:25 ` He Ying
2021-05-07 9:41 ` Mark Rutland
2021-05-07 10:02 ` He Ying
2020-11-30 11:59 ` [PATCHv2 07/11] arm64: entry: fix non-NMI user<->kernel transitions Mark Rutland
2020-11-30 11:59 ` [PATCHv2 08/11] arm64: ptrace: prepare for EL1 irq/rcu tracking Mark Rutland
2020-11-30 11:59 ` [PATCHv2 09/11] arm64: entry: fix non-NMI kernel<->kernel transitions Mark Rutland
2021-04-25 5:29 ` Zenghui Yu
2021-04-26 9:21 ` Mark Rutland
2021-04-26 13:39 ` Zenghui Yu
2021-04-27 7:15 ` Zenghui Yu
2021-04-27 14:43 ` Mark Rutland
2020-11-30 11:59 ` [PATCHv2 10/11] arm64: entry: fix NMI {user, kernel}->kernel transitions Mark Rutland
2020-11-30 11:59 ` [PATCHv2 11/11] arm64: entry: fix EL1 debug transitions Mark Rutland
2020-11-30 13:52 ` Will Deacon [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=160673829883.2674613.7469554321959251331.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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 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.