public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH] s390x: Use loop to save and restore fprs
Date: Mon, 11 Nov 2019 14:34:08 +0100	[thread overview]
Message-ID: <49b6daa6-f5fd-9ca6-7ffb-ec7c23c5cf92@linux.ibm.com> (raw)
In-Reply-To: <5dfe4c62-5178-3e9c-b1bb-6814e020078e@redhat.com>


On 11/8/19 10:15 AM, Thomas Huth wrote:
> On 04/11/2019 09.55, Janosch Frank wrote:
>> Let's save some lines in the assembly by using a loop to save and
>> restore the fprs.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>>   s390x/cstart64.S | 38 ++++++--------------------------------
>>   1 file changed, 6 insertions(+), 32 deletions(-)
>>
>> diff --git a/s390x/cstart64.S b/s390x/cstart64.S
>> index 5dc1577..8e2b21e 100644
>> --- a/s390x/cstart64.S
>> +++ b/s390x/cstart64.S
>> @@ -99,44 +99,18 @@ memsetxc:
>>       lctlg    %c0, %c0, 0(%r1)
>>       /* save fprs 0-15 + fpc */
>>       la    %r1, GEN_LC_SW_INT_FPRS
>> -    std    %f0, 0(%r1)
>> -    std    %f1, 8(%r1)
>> -    std    %f2, 16(%r1)
>> -    std    %f3, 24(%r1)
>> -    std    %f4, 32(%r1)
>> -    std    %f5, 40(%r1)
>> -    std    %f6, 48(%r1)
>> -    std    %f7, 56(%r1)
>> -    std    %f8, 64(%r1)
>> -    std    %f9, 72(%r1)
>> -    std    %f10, 80(%r1)
>> -    std    %f11, 88(%r1)
>> -    std    %f12, 96(%r1)
>> -    std    %f13, 104(%r1)
>> -    std    %f14, 112(%r1)
>> -    std    %f15, 120(%r1)
>> +    .irp i, 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
>> +    std    \i, \i * 8(%r1)
>> +    .endr
>>       stfpc    GEN_LC_SW_INT_FPC
>>       .endm
>>         .macro RESTORE_REGS
>>       /* restore fprs 0-15 + fpc */
>>       la    %r1, GEN_LC_SW_INT_FPRS
>> -    ld    %f0, 0(%r1)
>> -    ld    %f1, 8(%r1)
>> -    ld    %f2, 16(%r1)
>> -    ld    %f3, 24(%r1)
>> -    ld    %f4, 32(%r1)
>> -    ld    %f5, 40(%r1)
>> -    ld    %f6, 48(%r1)
>> -    ld    %f7, 56(%r1)
>> -    ld    %f8, 64(%r1)
>> -    ld    %f9, 72(%r1)
>> -    ld    %f10, 80(%r1)
>> -    ld    %f11, 88(%r1)
>> -    ld    %f12, 96(%r1)
>> -    ld    %f13, 104(%r1)
>> -    ld    %f14, 112(%r1)
>> -    ld    %f15, 120(%r1)
>> +    .irp i, 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
>> +    ld    \i, \i * 8(%r1)
>> +    .endr
>>       lfpc    GEN_LC_SW_INT_FPC
>>       /* restore cr0 */
>>       lctlg    %c0, %c0, GEN_LC_SW_INT_CR0
>>
>
> Produces exactly the same code as before.
>
> Tested-by: Thomas Huth <thuth@redhat.com>
>
Good for me, makes the code smaller ... is better

Reviewed-by: Pierre Morel <pmorel@linux.ibm.com>



-- 
Pierre Morel
IBM Lab Boeblingen

      reply	other threads:[~2019-11-11 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04  8:55 [kvm-unit-tests PATCH] s390x: Use loop to save and restore fprs Janosch Frank
2019-11-04 10:00 ` David Hildenbrand
2019-11-08  9:15 ` Thomas Huth
2019-11-11 13:34   ` Pierre Morel [this message]

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=49b6daa6-f5fd-9ca6-7ffb-ec7c23c5cf92@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=thuth@redhat.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