All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Cyril Bur <cyrilbur@tenstorrent.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org, antonb@tenstorrent.com
Subject: Re: [PATCH v2] riscv: Improve exception and system call latency
Date: Thu, 25 Jul 2024 13:20:39 +0000	[thread overview]
Message-ID: <172191363945.6240.15239605352830042623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240607061335.2197383-1-cyrilbur@tenstorrent.com>

Hello:

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

On Thu,  6 Jun 2024 23:13:35 -0700 you wrote:
> From: Anton Blanchard <antonb@tenstorrent.com>
> 
> Many CPUs implement return address branch prediction as a stack. The
> RISCV architecture refers to this as a return address stack (RAS). If
> this gets corrupted then the CPU will mispredict at least one but
> potentally many function returns.
> 
> [...]

Here is the summary with links:
  - [v2] riscv: Improve exception and system call latency
    https://git.kernel.org/riscv/c/9eb7421003d3

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: Cyril Bur <cyrilbur@tenstorrent.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org, antonb@tenstorrent.com
Subject: Re: [PATCH v2] riscv: Improve exception and system call latency
Date: Thu, 25 Jul 2024 13:20:39 +0000	[thread overview]
Message-ID: <172191363945.6240.15239605352830042623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240607061335.2197383-1-cyrilbur@tenstorrent.com>

Hello:

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

On Thu,  6 Jun 2024 23:13:35 -0700 you wrote:
> From: Anton Blanchard <antonb@tenstorrent.com>
> 
> Many CPUs implement return address branch prediction as a stack. The
> RISCV architecture refers to this as a return address stack (RAS). If
> this gets corrupted then the CPU will mispredict at least one but
> potentally many function returns.
> 
> [...]

Here is the summary with links:
  - [v2] riscv: Improve exception and system call latency
    https://git.kernel.org/riscv/c/9eb7421003d3

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



  parent reply	other threads:[~2024-07-25 13:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25  4:00 [PATCH] riscv: Improve exception and system call latency Anton Blanchard
2023-12-25  4:00 ` Anton Blanchard
2023-12-25 10:09 ` Jisheng Zhang
2023-12-25 10:09   ` Jisheng Zhang
2023-12-26  3:56 ` Guo Ren
2023-12-26  3:56   ` Guo Ren
2024-06-03  4:38   ` Cyril Bur
2024-06-03  4:38     ` Cyril Bur
2024-06-03  6:39     ` Guo Ren
2024-06-03  6:39       ` Guo Ren
2024-06-04  8:15       ` [CAUTION - External Sender] " Cyril Bur
2024-06-04  8:15         ` Cyril Bur
2024-06-05  5:52         ` Guo Ren
2024-06-05  5:52           ` Guo Ren
2024-06-05  5:53           ` Guo Ren
2024-06-05  5:53             ` Guo Ren
2024-06-07  6:13 ` [PATCH v2] " Cyril Bur
2024-06-07  6:13   ` Cyril Bur
2024-07-11 14:40   ` Jisheng Zhang
2024-07-11 14:40     ` Jisheng Zhang
2024-07-25 13:20   ` patchwork-bot+linux-riscv [this message]
2024-07-25 13:20     ` 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=172191363945.6240.15239605352830042623.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=antonb@tenstorrent.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=cyrilbur@tenstorrent.com \
    --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.