From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH] KVM: s390: get rid of register asm usage
Date: Mon, 21 Jun 2021 16:39:35 +0200 [thread overview]
Message-ID: <20210621163935.143dd14a@ibm-vm> (raw)
In-Reply-To: <20210621140356.1210771-1-hca@linux.ibm.com>
On Mon, 21 Jun 2021 16:03:56 +0200
Heiko Carstens <hca@linux.ibm.com> wrote:
> Using register asm statements has been proven to be very error prone,
> especially when using code instrumentation where gcc may add function
> calls, which clobbers register contents in an unexpected way.
>
> Therefore get rid of register asm statements in kvm code, even though
> there is currently nothing wrong with them. This way we know for sure
> that this bug class won't be introduced here.
>
> Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> arch/s390/kvm/kvm-s390.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> index 1296fc10f80c..4b7b24f07790 100644
> --- a/arch/s390/kvm/kvm-s390.c
> +++ b/arch/s390/kvm/kvm-s390.c
> @@ -329,31 +329,31 @@ static void allow_cpu_feat(unsigned long nr)
>
> static inline int plo_test_bit(unsigned char nr)
> {
> - register unsigned long r0 asm("0") = (unsigned long) nr |
> 0x100;
> + unsigned long function = (unsigned long) nr | 0x100;
> int cc;
>
> asm volatile(
> + " lgr 0,%[function]\n"
> /* Parameter registers are ignored for "test bit" */
> " plo 0,0,0,0(0)\n"
> " ipm %0\n"
> " srl %0,28\n"
> : "=d" (cc)
> - : "d" (r0)
> - : "cc");
> + : [function] "d" (function)
> + : "cc", "0");
> return cc == 0;
> }
>
> static __always_inline void __insn32_query(unsigned int opcode, u8
> *query) {
> - register unsigned long r0 asm("0") = 0; /* query
> function */
> - register unsigned long r1 asm("1") = (unsigned long) query;
> -
> asm volatile(
> - /* Parameter regs are ignored */
> + " lghi 0,0\n"
> + " lgr 1,%[query]\n"
> + /* Parameter registers are ignored */
> " .insn rrf,%[opc] << 16,2,4,6,0\n"
> :
> - : "d" (r0), "a" (r1), [opc] "i" (opcode)
> - : "cc", "memory");
> + : [query] "d" ((unsigned long)query), [opc] "i"
> (opcode)
> + : "cc", "memory", "0", "1");
> }
>
> #define INSN_SORTL 0xb938
next prev parent reply other threads:[~2021-06-21 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 14:03 [PATCH] KVM: s390: get rid of register asm usage Heiko Carstens
2021-06-21 14:34 ` Cornelia Huck
2021-06-21 14:39 ` Claudio Imbrenda [this message]
2021-06-22 7:36 ` Thomas Huth
2021-06-22 7:43 ` Christian Borntraeger
2021-06-22 7:46 ` Thomas Huth
2021-06-22 7:50 ` Christian Borntraeger
2021-06-22 7:53 ` Thomas Huth
2021-06-22 7:57 ` Christian Borntraeger
2021-06-22 8:00 ` Christian Borntraeger
2021-06-22 8:04 ` Thomas Huth
2021-06-22 14:56 ` Christian Borntraeger
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=20210621163935.143dd14a@ibm-vm \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.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