linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
	Paul Mackerras <paulus@samba.org>,
	Nathan Chancellor <natechancellor@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc: slightly improve cache helpers
Date: Tue, 23 Jul 2019 09:21:53 +1000	[thread overview]
Message-ID: <875znt7izy.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190722151801.GC20882@gate.crashing.org>

Segher Boessenkool <segher@kernel.crashing.org> writes:
> On Mon, Jul 22, 2019 at 08:15:14PM +1000, Michael Ellerman wrote:
>> Segher Boessenkool <segher@kernel.crashing.org> writes:
>> > On Sun, Jul 21, 2019 at 12:58:46AM -0700, Nathan Chancellor wrote:
>> >> 0000017c clear_user_page:
>> >>      17c: 94 21 ff f0                  	stwu 1, -16(1)
>> >>      180: 38 80 00 80                  	li 4, 128
>> >>      184: 38 63 ff e0                  	addi 3, 3, -32
>> >>      188: 7c 89 03 a6                  	mtctr 4
>> >>      18c: 38 81 00 0f                  	addi 4, 1, 15
>> >>      190: 8c c3 00 20                  	lbzu 6, 32(3)
>> >>      194: 98 c1 00 0f                  	stb 6, 15(1)
>> >>      198: 7c 00 27 ec                  	dcbz 0, 4
>> >>      19c: 42 00 ff f4                  	bdnz .+65524
>> >
>> > Uh, yeah, well, I have no idea what clang tried here, but that won't
>> > work.  It's copying a byte from each target cache line to the stack,
>> > and then does clears the cache line containing that byte on the stack.
>> 
>> So it seems like this is a clang bug.
>> 
>> None of the distros we support use clang, but we would still like to
>> keep it working if we can.
>
> Which version?  Which versions *are* broken?

AFAIK clang 8 is the first version that we could build with, without
hacks.

>> Looking at the original patch, the only upside is that the compiler
>> can use both RA and RB to compute the address, rather than us forcing RA
>> to 0.
>> 
>> But at least with my compiler here (GCC 8 vintage) I don't actually see
>> GCC ever using both GPRs even with the patch. Or at least, there's no
>> difference before/after the patch as far as I can see.
>
> The benefit is small, certainly.

Zero is small, but I guess some things are smaller? :P

>> So my inclination is to revert the original patch. We can try again in a
>> few years :D
>> 
>> Thoughts?
>
> I think you should give the clang people time to figure out what is
> going on.

Yeah fair enough, will wait and see what their diagnosis is.

cheers

  reply	other threads:[~2019-07-22 23:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10  9:24 [PATCH v2] powerpc: slightly improve cache helpers Christophe Leroy
2019-07-08  1:19 ` Michael Ellerman
2019-07-08 19:14   ` Nathan Chancellor
2019-07-09  5:04     ` Christophe Leroy
2019-07-09  6:49       ` Nathan Chancellor
2019-07-19  3:24         ` Nathan Chancellor
2019-07-19 15:23           ` Segher Boessenkool
2019-07-19 16:04             ` Nathan Chancellor
2019-07-21  7:58               ` Nathan Chancellor
2019-07-21 18:01                 ` Segher Boessenkool
2019-07-22  2:41                   ` Nathan Chancellor
2019-07-22  6:19                     ` Segher Boessenkool
2019-07-22 17:21                       ` Nick Desaulniers
2019-07-22 17:58                         ` Segher Boessenkool
2019-07-25 21:30                           ` Nick Desaulniers
2019-07-29 20:28                             ` Nick Desaulniers
2019-07-22 10:15                   ` Michael Ellerman
2019-07-22 15:18                     ` Segher Boessenkool
2019-07-22 23:21                       ` Michael Ellerman [this message]
2019-07-25 13:22                         ` Segher Boessenkool
2019-07-22  0:53                 ` [PATCH] powerpc: Test broken dcbz kbuild test robot
2019-07-09 13:35       ` [PATCH v2] powerpc: slightly improve cache helpers Segher Boessenkool

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=875znt7izy.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=natechancellor@gmail.com \
    --cc=paulus@samba.org \
    --cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).