From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/irq: Modernise inline assembly in irq_soft_mask_{set,return}
Date: Fri, 23 Sep 2022 17:15:43 -0500 [thread overview]
Message-ID: <20220923221543.GN25951@gate.crashing.org> (raw)
In-Reply-To: <CN3X6YN1FRQ3.1Z9BVD6WYQY3M@bobo>
On Sat, Sep 24, 2022 at 02:26:52AM +1000, Nicholas Piggin wrote:
> I still don't see what clauses guarantees asm("%0" ::"r"(foo)) to give
> 13. It doesn't say access via inline assembly is special,
But it is. It is for all register variables, local and global. I agree
this isn't documented clearly. For local register variables this is the
*only* thing guaranteed; for global register vars there is more (it
changes the ABI, there are safe/restore effects, that kind of thing).
Never it is guaranteed that all accesses through this variable will use
the register directly: this fundamentally cannot work on all archs, and
also not at -O0. More in general it doesn't work if some basic
optimisations are not done, be it because of a compiler deficiency, or a
straight out bug, or maybe it is a conscious choice in some cases.
> I think if it was obviously guaranteed then this might be marginally
> better than explicit r13 in the asm
>
> asm volatile(
> "stb %0,%2(%1)"
> :
> : "r" (mask),
> "r" (local_paca),
> "i" (offsetof(struct paca_struct, irq_soft_mask))
> : "memory");
(Please use "n" instead of "i". Doesn't matter here, but it does in
many other places.)
Segher
next prev parent reply other threads:[~2022-09-23 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 6:41 [PATCH] powerpc/irq: Modernise inline assembly in irq_soft_mask_{set,return} Christophe Leroy
2022-09-23 7:08 ` Nicholas Piggin
2022-09-23 12:18 ` Segher Boessenkool
2022-09-23 16:26 ` Nicholas Piggin
2022-09-23 22:15 ` Segher Boessenkool [this message]
2022-09-24 4:00 ` Nicholas Piggin
2022-09-24 16:14 ` Segher Boessenkool
2022-09-24 18:30 ` 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=20220923221543.GN25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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