All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc: slightly improve cache helpers
Date: Mon, 22 Jul 2019 01:19:40 -0500	[thread overview]
Message-ID: <20190722061940.GZ20882@gate.crashing.org> (raw)
In-Reply-To: <20190722024140.GA55142@archlinux-threadripper>

On Sun, Jul 21, 2019 at 07:41:40PM -0700, Nathan Chancellor wrote:
> Hi Segher,
> 
> On Sun, Jul 21, 2019 at 01:01:50PM -0500, Segher Boessenkool wrote:
> > 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.
> > 
> > I *guess* this is about "Z" and not about "%y", but you'll have to ask
> > the clang people.
> > 
> > Or it may be that they do not treat inline asm operands as lvalues
> > properly?  That rings some bells.  Yeah that looks like it.

The code is
  __asm__ __volatile__ ("dcbz %y0" : : "Z"(*(u8 *)addr) : "memory");

so yeah it looks like clang took that  *(u8 *)addr  as rvalue, and
stored that in stack, and then used *that* as memory.

Maybe clang simply does not not to treat "Z" the same as "m"?  (And "Y"
and "Q" and "es" and a whole bunch of "w*", what about those?)


Segher

WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Christophe Leroy <christophe.leroy@c-s.fr>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	clang-built-linux@googlegroups.com
Subject: Re: [PATCH v2] powerpc: slightly improve cache helpers
Date: Mon, 22 Jul 2019 01:19:40 -0500	[thread overview]
Message-ID: <20190722061940.GZ20882@gate.crashing.org> (raw)
In-Reply-To: <20190722024140.GA55142@archlinux-threadripper>

On Sun, Jul 21, 2019 at 07:41:40PM -0700, Nathan Chancellor wrote:
> Hi Segher,
> 
> On Sun, Jul 21, 2019 at 01:01:50PM -0500, Segher Boessenkool wrote:
> > 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.
> > 
> > I *guess* this is about "Z" and not about "%y", but you'll have to ask
> > the clang people.
> > 
> > Or it may be that they do not treat inline asm operands as lvalues
> > properly?  That rings some bells.  Yeah that looks like it.

The code is
  __asm__ __volatile__ ("dcbz %y0" : : "Z"(*(u8 *)addr) : "memory");

so yeah it looks like clang took that  *(u8 *)addr  as rvalue, and
stored that in stack, and then used *that* as memory.

Maybe clang simply does not not to treat "Z" the same as "m"?  (And "Y"
and "Q" and "es" and a whole bunch of "w*", what about those?)


Segher

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

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