From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>, Kees Cook <kees@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Juergen Christ <jchrist@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
Sven Schnelle <svens@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v2 0/4] s390: Fix and optimize __flogr() inline assembly
Date: Thu, 18 Sep 2025 16:19:22 +0200 [thread overview]
Message-ID: <c38409b1-fa4e-4fa6-94a8-51616bf1fd6a-agordeev@linux.ibm.com> (raw)
In-Reply-To: <20250916134803.874580-1-hca@linux.ibm.com>
On Tue, Sep 16, 2025 at 03:47:59PM +0200, Heiko Carstens wrote:
> A recent optimization of the s390 specific ffs() and ffs64()
> implementations leads to a new compiler warning. Instead of reverting the
> optimization address this with the rather new assume attribute, which
> generates even better code, if supported by compilers.
>
> Since the assume attribute may be useful for others as well, add the
> __assume macro to compiler attributes, so it is kernel wide available,
> instead of adding an s390 specific optimization.
>
> Heiko Carstens (4):
> s390/bitops: Limit return value range of __flogr()
> compiler_types: Add __assume macro
> s390/bitops: Use __assume() for __flogr() inline assembly return value
> s390/bitops: Cleanup __flogr()
>
> arch/s390/include/asm/bitops.h | 21 ++++++++++++++-------
> include/linux/compiler_types.h | 23 +++++++++++++++++++++++
> init/Kconfig | 10 ++++++++++
> 3 files changed, 47 insertions(+), 7 deletions(-)
Applied, thanks!
prev parent reply other threads:[~2025-09-18 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 13:47 Heiko Carstens
2025-09-16 13:48 ` [PATCH v2 1/4] s390/bitops: Limit return value range of __flogr() Heiko Carstens
2025-09-16 13:48 ` [PATCH v2 2/4] compiler_types: Add __assume macro Heiko Carstens
2025-09-17 2:30 ` Nathan Chancellor
2025-09-16 13:48 ` [PATCH v2 3/4] s390/bitops: Use __assume() for __flogr() inline assembly return value Heiko Carstens
2025-09-16 13:48 ` [PATCH v2 4/4] s390/bitops: Cleanup __flogr() Heiko Carstens
2025-09-18 14:19 ` Alexander Gordeev [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=c38409b1-fa4e-4fa6-94a8-51616bf1fd6a-agordeev@linux.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jchrist@linux.ibm.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=ojeda@kernel.org \
--cc=svens@linux.ibm.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
all inboxes | Powered by JetHome®