From: patchwork-bot+linux-riscv@kernel.org
To: Leonardo Bras <leobras@redhat.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, ebiederm@xmission.com,
keescook@chromium.org, oleg@redhat.com, guoren@kernel.org,
andy.chiu@sifive.com, conor.dooley@microchip.com,
xiao.w.wang@intel.com, vincent.chen@sifive.com,
charlie@rivosinc.com, gerg@kernel.org, akpm@linux-foundation.org,
shikemeng@huaweicloud.com, alexghiti@rivosinc.com,
david@redhat.com, willy@infradead.org,
panqinglin2020@iscas.ac.cn, greentime.hu@sifive.com,
bhe@redhat.com, cleger@rivosinc.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v1 0/5] riscv: Introduce compat-mode helpers & improve arch_get_mmap_end()
Date: Wed, 20 Mar 2024 20:50:39 +0000 [thread overview]
Message-ID: <171096783911.6804.6652711937507464203.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240103160024.70305-2-leobras@redhat.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 3 Jan 2024 13:00:18 -0300 you wrote:
> I just saw the opportunity of optimizing the helper is_compat_task() by
> introducing a compile-time test, and it made possible to remove some
> #ifdef's without any loss of performance.
>
> I also saw the possibility of removing the direct check of task flags from
> general code, and concentrated it in asm/compat.h by creating a few more
> helpers, which in the end helped optimize code.
>
> [...]
Here is the summary with links:
- [v1,1/5] riscv: Improve arch_get_mmap_end() macro
https://git.kernel.org/riscv/c/6be7ee4bebd1
- [v1,2/5] riscv: Replace direct thread flag check with is_compat_task()
https://git.kernel.org/riscv/c/9dc30419248f
- [v1,3/5] riscv: add compile-time test into is_compat_task()
https://git.kernel.org/riscv/c/4c0b5a451675
- [v1,4/5] riscv: Introduce is_compat_thread() into compat.h
https://git.kernel.org/riscv/c/5917ea17ad07
- [v1,5/5] riscv: Introduce set_compat_task() in asm/compat.h
https://git.kernel.org/riscv/c/2a8986fc5e1c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-20 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 16:00 [PATCH v1 0/5] riscv: Introduce compat-mode helpers & improve arch_get_mmap_end() Leonardo Bras
2024-01-03 16:00 ` [PATCH v1 1/5] riscv: Improve arch_get_mmap_end() macro Leonardo Bras
2024-01-03 16:00 ` [PATCH v1 2/5] riscv: Replace direct thread flag check with is_compat_task() Leonardo Bras
2024-01-03 16:00 ` [PATCH v1 3/5] riscv: add compile-time test into is_compat_task() Leonardo Bras
2024-01-03 16:00 ` [PATCH v1 4/5] riscv: Introduce is_compat_thread() into compat.h Leonardo Bras
2024-01-03 16:00 ` [PATCH v1 5/5] riscv: Introduce set_compat_task() in asm/compat.h Leonardo Bras
2024-03-20 20:50 ` 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=171096783911.6804.6652711937507464203.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bhe@redhat.com \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gerg@kernel.org \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=keescook@chromium.org \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=panqinglin2020@iscas.ac.cn \
--cc=paul.walmsley@sifive.com \
--cc=shikemeng@huaweicloud.com \
--cc=vincent.chen@sifive.com \
--cc=willy@infradead.org \
--cc=xiao.w.wang@intel.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