From: Vasily Gorbik <gor@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH 2/3] s390/xor: Improve inline assembly constraints
Date: Mon, 2 Mar 2026 17:02:53 +0100 [thread overview]
Message-ID: <your-ad-here.call-01772467373-ext-6845@work.hours> (raw)
In-Reply-To: <20260302133500.1560531-3-hca@linux.ibm.com>
On Mon, Mar 02, 2026 at 02:34:59PM +0100, Heiko Carstens wrote:
> The inline assembly constraint for the "bytes" operand is "d" for all xor()
> inline assemblies. "d" means that any register from 0 to 15 can be used. If
> the compiler would use register 0 then the exrl instruction would not or
> the value of "bytes" into the executed instruction - resulting in an
> incorrect result.
>
> However all the xor() inline assemblies make hard-coded use of register 0,
> and it is correctly listed in the clobber list, so that this cannot happen.
>
> Given that this is quite subtle use the better "a" constraint, which
> excludes register 0 from register allocation in any case.
>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> ---
> arch/s390/lib/xor.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Reviewed-by: Vasily Gorbik <gor@linux.ibm.com>
next prev parent reply other threads:[~2026-03-02 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 13:34 [PATCH 0/3] s390: Fix and improve inline assembly constraints Heiko Carstens
2026-03-02 13:34 ` [PATCH 1/3] s390/xor: Fix xor_xc_2() " Heiko Carstens
2026-03-02 15:41 ` Vasily Gorbik
2026-03-02 13:34 ` [PATCH 2/3] s390/xor: Improve " Heiko Carstens
2026-03-02 16:02 ` Vasily Gorbik [this message]
2026-03-02 13:35 ` [PATCH 3/3] s390/stackleak: Fix __stackleak_poison() inline assembly constraint Heiko Carstens
2026-03-02 15:40 ` Vasily Gorbik
2026-03-02 13:47 ` [PATCH 0/3] s390: Fix and improve inline assembly constraints Christoph Hellwig
2026-03-02 14:40 ` Heiko Carstens
2026-03-02 16:13 ` Vasily Gorbik
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=your-ad-here.call-01772467373-ext-6845@work.hours \
--to=gor@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.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 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.