From: Akira Tsukamoto <akira.tsukamoto@gmail.com> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Akira Tsukamoto <akira.tsukamoto@gmail.com>, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/1] __asm_copy_to-from_user: Reduce more byte_copy Date: Thu, 11 Nov 2021 17:11:03 +0900 [thread overview] Message-ID: <6ebbb5e0-c2bc-89ce-2cb8-4f537c5aea13@gmail.com> (raw) I tried building the kernel on both starlight and unmatched successfully with v2. --- v1 -> v2: Fixed the kernel panic when the page was not allocated for the address of REG_L and REG_S. The REG_L is loading the data from main memory to register and REG_S is storing the data in register to main memory. In these functions for copying between kernel and user space, the kernel will not automatically trap and recover the page faults. Adding macro for them. Akira Tsukamoto (1): riscv: __asm_copy_to-from_user: Improve using word copy if size is < 9*SZREG arch/riscv/lib/uaccess.S | 46 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 42 insertions(+), 4 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Akira Tsukamoto <akira.tsukamoto@gmail.com> To: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Akira Tsukamoto <akira.tsukamoto@gmail.com>, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/1] __asm_copy_to-from_user: Reduce more byte_copy Date: Thu, 11 Nov 2021 17:11:03 +0900 [thread overview] Message-ID: <6ebbb5e0-c2bc-89ce-2cb8-4f537c5aea13@gmail.com> (raw) I tried building the kernel on both starlight and unmatched successfully with v2. --- v1 -> v2: Fixed the kernel panic when the page was not allocated for the address of REG_L and REG_S. The REG_L is loading the data from main memory to register and REG_S is storing the data in register to main memory. In these functions for copying between kernel and user space, the kernel will not automatically trap and recover the page faults. Adding macro for them. Akira Tsukamoto (1): riscv: __asm_copy_to-from_user: Improve using word copy if size is < 9*SZREG arch/riscv/lib/uaccess.S | 46 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 42 insertions(+), 4 deletions(-) -- 2.17.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2021-11-11 8:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 8:11 Akira Tsukamoto [this message] 2021-11-11 8:11 ` [PATCH v2 0/1] __asm_copy_to-from_user: Reduce more byte_copy Akira Tsukamoto 2021-11-11 8:13 ` [PATCH v2 1/1] riscv: __asm_copy_to-from_user: Improve using word copy, if size is < 9*SZREG Akira Tsukamoto 2021-11-11 8:13 ` Akira Tsukamoto 2021-11-11 23:04 ` kernel test robot 2021-11-11 23:04 ` kernel test robot 2021-11-11 23:04 ` kernel test robot 2021-11-12 4:23 ` kernel test robot 2021-11-12 4:23 ` kernel test robot 2021-11-12 4:23 ` kernel test robot
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=6ebbb5e0-c2bc-89ce-2cb8-4f537c5aea13@gmail.com \ --to=akira.tsukamoto@gmail.com \ --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: linkBe 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.