From: patchwork-bot+linux-riscv@kernel.org
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: linux-riscv@lists.infradead.org, linux-arch@vger.kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com, zong.li@sifive.com,
guoren@kernel.org, aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com
Subject: Re: [PATCH 0/2] riscv: asid: switch to alternative way to fix stale TLB entries
Date: Fri, 10 Mar 2023 02:30:19 +0000 [thread overview]
Message-ID: <167841541911.17842.1187782812543670687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230226150137.1919750-1-geomatsi@gmail.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 26 Feb 2023 18:01:35 +0300 you wrote:
> Hi all,
>
> Some time ago two different patches have been posted to fix stale TLB
> entries that caused applications crashes.
>
> The patch [0] suggested 'aggregating' mm_cpumask, i.e. current cpu is not
> cleared for the switched-out task in switch_mm function. For additional
> explanations see the commit message by Guo Ren. The same approach is
> used by arc architecture, so another good comment is for switch_mm
> in arch/arc/include/asm/mmu_context.h.
>
> [...]
Here is the summary with links:
- [1/2] Revert "riscv: mm: notify remote harts about mmu cache updates"
https://git.kernel.org/riscv/c/e921050022f1
- [2/2] riscv: asid: Fixup stale TLB entry cause application crash
https://git.kernel.org/riscv/c/82dd33fde026
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
prev parent reply other threads:[~2023-03-10 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 15:01 [PATCH 0/2] riscv: asid: switch to alternative way to fix stale TLB entries Sergey Matyukevich
2023-02-26 15:01 ` [PATCH 1/2] Revert "riscv: mm: notify remote harts about mmu cache updates" Sergey Matyukevich
2023-02-28 3:15 ` Guo Ren
2023-02-26 15:01 ` [PATCH 2/2] riscv: asid: Fixup stale TLB entry cause application crash Sergey Matyukevich
2023-02-26 16:44 ` Andrew Jones
2023-03-10 2:30 ` patchwork-bot+linux-riscv [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=167841541911.17842.1187782812543670687.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=geomatsi@gmail.com \
--cc=guoren@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=zong.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox