All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Andrew Bresticker <abrestic@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
	atishp@rivosinc.com, guoren@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RISC-V: Fix unannoted hardirqs-on in return to userspace slow-path
Date: Thu, 08 Dec 2022 23:50:15 +0000	[thread overview]
Message-ID: <167054341561.16966.16448595920168997874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221111223108.1976562-1-abrestic@rivosinc.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Fri, 11 Nov 2022 17:31:08 -0500 you wrote:
> The return to userspace path in entry.S may enable interrupts without the
> corresponding lockdep annotation, producing a splat[0] when DEBUG_LOCKDEP
> is enabled. Simply calling __trace_hardirqs_on() here gets a bit messy
> due to the use of RA to point back to ret_from_exception, so just move
> the whole slow-path loop into C. It's more readable and it lets us use
> local_irq_{enable,disable}(), avoiding the need for manual annotations
> altogether.
> 
> [...]

Here is the summary with links:
  - RISC-V: Fix unannoted hardirqs-on in return to userspace slow-path
    https://git.kernel.org/riscv/c/b0f4c74eadbf

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



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

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Andrew Bresticker <abrestic@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
	atishp@rivosinc.com, guoren@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RISC-V: Fix unannoted hardirqs-on in return to userspace slow-path
Date: Thu, 08 Dec 2022 23:50:15 +0000	[thread overview]
Message-ID: <167054341561.16966.16448595920168997874.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221111223108.1976562-1-abrestic@rivosinc.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Fri, 11 Nov 2022 17:31:08 -0500 you wrote:
> The return to userspace path in entry.S may enable interrupts without the
> corresponding lockdep annotation, producing a splat[0] when DEBUG_LOCKDEP
> is enabled. Simply calling __trace_hardirqs_on() here gets a bit messy
> due to the use of RA to point back to ret_from_exception, so just move
> the whole slow-path loop into C. It's more readable and it lets us use
> local_irq_{enable,disable}(), avoiding the need for manual annotations
> altogether.
> 
> [...]

Here is the summary with links:
  - RISC-V: Fix unannoted hardirqs-on in return to userspace slow-path
    https://git.kernel.org/riscv/c/b0f4c74eadbf

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2022-12-08 23:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 22:31 [PATCH] RISC-V: Fix unannoted hardirqs-on in return to userspace slow-path Andrew Bresticker
2022-11-11 22:31 ` Andrew Bresticker
2022-11-12 23:52 ` Conor Dooley
2022-11-12 23:52   ` Conor Dooley
2022-11-14 14:31   ` Andrew Bresticker
2022-11-14 14:31     ` Andrew Bresticker
2022-11-14 14:42 ` Guo Ren
2022-11-14 14:42   ` Guo Ren
2022-11-14 15:20   ` Andrew Bresticker
2022-11-14 15:20     ` Andrew Bresticker
2022-11-14 15:30     ` Conor Dooley
2022-11-14 15:30       ` Conor Dooley
2022-11-14 15:42       ` Andrew Bresticker
2022-11-14 15:42         ` Andrew Bresticker
2022-11-14 15:54         ` Guo Ren
2022-11-14 15:54           ` Guo Ren
2022-12-08 23:43           ` Palmer Dabbelt
2022-12-08 23:43             ` Palmer Dabbelt
2022-12-08 23:43 ` Palmer Dabbelt
2022-12-08 23:43   ` Palmer Dabbelt
2022-12-08 23:50 ` patchwork-bot+linux-riscv [this message]
2022-12-08 23:50   ` patchwork-bot+linux-riscv

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=167054341561.16966.16448595920168997874.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=abrestic@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@rivosinc.com \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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.