public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH] s390x: Add diag308 subcode 0 testing
Date: Fri, 23 Aug 2019 16:41:29 +0200	[thread overview]
Message-ID: <137ffa8a-2a93-b31b-df47-6b27d566deef@linux.ibm.com> (raw)
In-Reply-To: <ffc7de14-7960-5423-d984-c18ab1dfa4b2@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1425 bytes --]

On 8/23/19 4:12 PM, Thomas Huth wrote:
> On 8/22/19 1:11 PM, Janosch Frank wrote:
>> By adding a load reset routine to cstart.S we can also test the clear
>> reset done by subcode 0, as we now can restore our registers again.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>> I managed to extract this from another bigger test, so let's add it to the bunch.
>> I'd be very happy about assembly review :-)
> 
> FWIW, the assembly code looks fine to me.
> 
>> ---
>>  s390x/cstart64.S | 27 +++++++++++++++++++++++++++
>>  s390x/diag308.c  | 31 ++++++++++---------------------
>>  2 files changed, 37 insertions(+), 21 deletions(-)
>>
>> diff --git a/s390x/cstart64.S b/s390x/cstart64.S
>> index dedfe80..47045e1 100644
>> --- a/s390x/cstart64.S
>> +++ b/s390x/cstart64.S
>> @@ -145,6 +145,33 @@ memsetxc:
>>  	.endm
>>  
>>  .section .text
>> +/*
>> + * load_reset calling convention:
>> + * %r2 subcode (0 or 1)
>> + */
>> +.globl load_reset
>> +load_reset:
> 
> Maybe rather name the function diag308_load_reset so that it is clear
> that it belongs to the diag308 test?

Sure

> Or are you going to re-use this function in other tests later?

I currently have no such plans
But I'm thinking about a way to check the CPU registers in combination
with smp. So it might be extended.

> 
> Anyway,
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> 

Thanks!



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-08-23 14:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 10:47 [kvm-unit-tests PATCH v2 0/4] s390x: More emulation tests Janosch Frank
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 1/4] s390x: Support PSW restart boot Janosch Frank
2019-08-21 13:23   ` David Hildenbrand
2019-08-23 10:31   ` David Hildenbrand
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 2/4] s390x: Diag288 test Janosch Frank
2019-08-23 10:30   ` Thomas Huth
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 3/4] s390x: Move stsi to library Janosch Frank
2019-08-21 13:27   ` David Hildenbrand
2019-08-23 10:34   ` Thomas Huth
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 4/4] s390x: STSI tests Janosch Frank
2019-08-23 10:57   ` Thomas Huth
2019-08-23 11:16     ` Janosch Frank
2019-08-22 11:11 ` [kvm-unit-tests PATCH] s390x: Add diag308 subcode 0 testing Janosch Frank
2019-08-23 11:00   ` David Hildenbrand
2019-08-23 11:33     ` Janosch Frank
2019-08-23 11:36       ` David Hildenbrand
2019-08-23 14:12   ` Thomas Huth
2019-08-23 14:41     ` Janosch Frank [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=137ffa8a-2a93-b31b-df47-6b27d566deef@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=david@redhat.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