public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] riscv: uaccess: optimizations
Date: Tue, 25 Jun 2024 12:04:56 +0800	[thread overview]
Message-ID: <20240625040500.1788-1-jszhang@kernel.org> (raw)

This series tries to optimize riscv uaccess in the following way:

patch1 implement the user_access_begin and families, I.E the unsafe
accessors. when a function like strncpy_from_user() is called,
the userspace access protection is disabled and enabled for every
word read. After patch1, the protection is disabled at the beginning
of the copy and enabled at the end.

patch2 is a simple clean up

patch3 uses 'asm goto' for put_user()
patch4 uses 'asm goto output' for get_user()

Both patch3 and patch4 are based on the fact -- 'asm goto' and
'asm goto output'generates noticeably better code since we don't need
to test the error etc, the exception just jumps to the error handling
directly.


Jisheng Zhang (4):
  riscv: implement user_access_begin and families
  riscv: uaccess: use input constraints for ptr of __put_user
  riscv: uaccess: use 'asm goto' for put_user()
  riscv: uaccess: use 'asm goto output' for get_user

 arch/riscv/include/asm/uaccess.h | 201 +++++++++++++++++++++++--------
 1 file changed, 149 insertions(+), 52 deletions(-)

-- 
2.43.0


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

             reply	other threads:[~2024-06-25  4:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25  4:04 Jisheng Zhang [this message]
2024-06-25  4:04 ` [PATCH 1/4] riscv: implement user_access_begin and families Jisheng Zhang
2024-06-26 23:38   ` Cyril Bur
2024-06-25  4:04 ` [PATCH 2/4] riscv: uaccess: use input constraints for ptr of __put_user Jisheng Zhang
2024-06-25  5:54   ` Arnd Bergmann
2024-06-26 12:32     ` Jisheng Zhang
2024-06-26 12:49       ` Jisheng Zhang
2024-06-26 13:18         ` Jisheng Zhang
2024-06-26 13:35         ` Andreas Schwab
2024-06-26 13:54           ` Jisheng Zhang
2024-06-26 13:12   ` Andreas Schwab
2024-06-26 13:12     ` Jisheng Zhang
2024-06-26 14:25       ` Arnd Bergmann
2024-06-26 16:02         ` Jisheng Zhang
2024-06-27  6:46           ` Arnd Bergmann
2024-06-28 15:36         ` David Laight
2024-06-25  4:04 ` [PATCH 3/4] riscv: uaccess: use 'asm goto' for put_user() Jisheng Zhang
2024-07-05  2:22   ` kernel test robot
2024-07-06  0:02   ` kernel test robot
2024-06-25  4:05 ` [PATCH 4/4] riscv: uaccess: use 'asm goto output' for get_user Jisheng Zhang
2024-07-05  4:13   ` kernel test robot
2024-06-25  7:21 ` [PATCH 0/4] riscv: uaccess: optimizations Arnd Bergmann
2024-06-25 18:12   ` Linus Torvalds
2024-06-26 13:04     ` Jisheng Zhang
2024-06-30 16:59     ` Linus Torvalds
2024-07-05 11:25       ` Will Deacon
2024-07-05 17:58         ` Linus Torvalds
2024-07-08 13:52           ` Will Deacon
2024-07-08 15:30             ` Mark Rutland
2024-07-23 14:16               ` Will Deacon
2024-07-08 15:21           ` Mark Rutland
2024-07-24 22:57 ` Palmer Dabbelt

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=20240625040500.1788-1-jszhang@kernel.org \
    --to=jszhang@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --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