public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Mark Rutland" <mark.rutland@arm.com>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will@kernel.org>, "Jason Gunthorpe" <jgg@ziepe.ca>,
	"Valentin Schneider" <vschneid@redhat.com>,
	"Baoquan He" <bhe@redhat.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/io: add constant-argument check
Date: Wed, 29 May 2024 14:29:37 +0200	[thread overview]
Message-ID: <8ff9bc52-bf2f-4856-9335-14bf659e7e4c@app.fastmail.com> (raw)
In-Reply-To: <ZlcODqVXTDh6n0h-@J2N7QTR9R3>

On Wed, May 29, 2024, at 13:14, Mark Rutland wrote:
>>  {
>> -	if (count == 8 || count == 4 || count == 2 || count == 1) {
>> +	if (__builtin_constant_p(count) &&
>> +	    (count == 8 || count == 4 || count == 2 || count == 1)) {
>>  		__const_memcpy_toio_aligned32(to, from, count);
>>  		dgh();
>>  	} else {
>
> I don't think this is the right fix.
>
> The idea was that this was checked in __iowrite32_copy(), which does:
>
> 	#define __iowrite32_copy(to, from, count)                  \
> 	        (__builtin_constant_p(count) ?                     \
> 	                 __const_iowrite32_copy(to, from, count) : \
> 	                 __iowrite32_copy_full(to, from, count))
>
> ... and so __const_iowrite32_copy() should really be marked as __always_inline,
> and the same for __const_memcpy_toio_aligned32(), to guarantee that both get
> inlined and such that __const_memcpy_toio_aligned32() sees a constant.
>
> The same reasoning applies to __const_iowrite64_copy() and
> __const_memcpy_toio_aligned64().
>
> Checking for a constant in __const_iowrite32_copy() doesn't guarantee
> that __const_memcpy_toio_aligned32() is inlined and will actually see a
> constant.
>
> Does diff the below you for you?

Yes, your version addresses both failures I ran into, and
I think all other theoretical cases.

I would prefer to combine both though, using __always_inline
to force the compiler to pick the inline version over
__iowrite32_copy_full() even when it is optimizing for size
and it decides the inline version is larger, but removing
the extra complexity from the macro.

According to Jason, he used a macro here to be sure
that the compiler can detect an inline function argument
as constant when the value is known but it is not
a constant value according to the C standard.

This was indeed a problem in older versions of clang
that missed a lot of optimizations in the kernel, but
clang-8 and higher were changed to have the same behavior
as gcc here, so it is no longer necessary now that the
older versions are unable to build kernels.

     Arnd

  reply	other threads:[~2024-05-29 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 12:08 [PATCH] arm64/io: add constant-argument check Arnd Bergmann
2024-05-28 15:30 ` Arnd Bergmann
2024-05-29 11:14 ` Mark Rutland
2024-05-29 12:29   ` Arnd Bergmann [this message]
2024-05-29 15:08     ` Mark Rutland
2024-05-29 16:15       ` Arnd Bergmann
2024-05-29 16:36         ` Mark Rutland

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=8ff9bc52-bf2f-4856-9335-14bf659e7e4c@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=bhe@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    --cc=vschneid@redhat.com \
    --cc=will@kernel.org \
    /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