public inbox for linux-riscv@lists.infradead.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, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, paul.walmsley@sifive.com,
	charlie@rivosinc.com, jrtc27@jrtc27.com,
	ben.dooks@codethink.co.uk, alex@ghiti.fr,
	linux-kernel@vger.kernel.org, jszhang@kernel.org
Subject: Re: [PATCH v6 0/5] riscv: uaccess: optimisations
Date: Fri, 09 May 2025 17:30:35 +0000	[thread overview]
Message-ID: <174681183574.3697320.3349869843167722914.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250410070526.3160847-1-cyrilbur@tenstorrent.com>

Hello:

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

On Thu, 10 Apr 2025 07:05:21 +0000 you wrote:
> This series tries to optimize riscv uaccess by allowing the use of
> user_access_begin() and user_access_end() which permits grouping user accesses
> and avoiding the CSR write penalty for each access.
> 
> The error path can also be optimised using asm goto which patches 3 and 4
> achieve. This will speed up jumping to labels by avoiding the need of an
> intermediary error type variable within the uaccess macros
> 
> [...]

Here is the summary with links:
  - [v6,1/5] riscv: save the SR_SUM status over switches
    https://git.kernel.org/riscv/c/788aa64c01f1
  - [v6,2/5] riscv: implement user_access_begin() and families
    https://git.kernel.org/riscv/c/19500c6dbc5c
  - [v6,3/5] riscv: uaccess: use input constraints for ptr of __put_user()
    https://git.kernel.org/riscv/c/62135bf660b2
  - [v6,4/5] riscv: uaccess: use 'asm goto' for put_user()
    https://git.kernel.org/riscv/c/cdf647e81714
  - [v6,5/5] riscv: uaccess: use 'asm_goto_output' for get_user()
    https://git.kernel.org/riscv/c/f6bff7827a48

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

      parent reply	other threads:[~2025-05-09 20:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10  7:05 [PATCH v6 0/5] riscv: uaccess: optimisations Cyril Bur
2025-04-10  7:05 ` [PATCH v6 1/5] riscv: save the SR_SUM status over switches Cyril Bur
2025-04-22 10:22   ` Alexandre Ghiti
2025-05-21  8:26     ` Ben Dooks
2025-05-21 13:38       ` Samuel Holland
2025-05-21 14:30         ` Alexandre Ghiti
2025-05-21 14:45           ` Cyril Bur
2025-05-22 16:15           ` [EXT] " Cyril Bur
2025-05-22 17:40           ` Andy Chiu
2025-05-22 20:03             ` Ben Dooks
2025-04-22 23:01   ` Deepak Gupta
2025-04-23  6:44     ` Alexandre Ghiti
2025-05-20 16:49     ` Deepak Gupta
2025-05-22  6:23       ` Ben Dooks
2025-05-22 14:49         ` Deepak Gupta
2025-05-22 17:42           ` Andy Chiu
2025-05-22 22:43             ` Deepak Gupta
2025-05-23 12:22               ` Alexandre Ghiti
2025-05-23 17:14                 ` Deepak Gupta
2025-05-23 20:00                   ` Alexandre Ghiti
2025-05-27 19:34                     ` Deepak Gupta
2025-05-24 10:00                   ` Andy Chiu
2025-05-27 20:58                     ` Deepak Gupta
2025-04-10  7:05 ` [PATCH v6 2/5] riscv: implement user_access_begin() and families Cyril Bur
2025-04-22 10:26   ` Alexandre Ghiti
2025-04-10  7:05 ` [PATCH v6 3/5] riscv: uaccess: use input constraints for ptr of __put_user() Cyril Bur
2025-04-22 12:10   ` Alexandre Ghiti
2025-04-10  7:05 ` [PATCH v6 4/5] riscv: uaccess: use 'asm goto' for put_user() Cyril Bur
2025-04-22 10:36   ` Alexandre Ghiti
2025-04-10  7:05 ` [PATCH v6 5/5] riscv: uaccess: use 'asm_goto_output' for get_user() Cyril Bur
2025-04-22 12:19   ` Alexandre Ghiti
2025-05-09 17: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=174681183574.3697320.3349869843167722914.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=ben.dooks@codethink.co.uk \
    --cc=charlie@rivosinc.com \
    --cc=cyrilbur@tenstorrent.com \
    --cc=jrtc27@jrtc27.com \
    --cc=jszhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox