qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, qemu-s390x@nongnu.org, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3] s390x: Add stsi 3.2.2 tests
Date: Tue, 31 Mar 2020 10:29:15 +0200	[thread overview]
Message-ID: <4d36c625-8c05-2027-24b9-e7b66839ca45@linux.ibm.com> (raw)
In-Reply-To: <37be8d87-d259-da6f-47c0-d5a314cfa2dc@redhat.com>


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

On 3/31/20 10:24 AM, David Hildenbrand wrote:
> On 31.03.20 09:14, Janosch Frank wrote:
>> Subcode 3.2.2 is handled by KVM/QEMU and should therefore be tested
>> a bit more thorough.
>>
>> In this test we set a custom name and uuid through the QEMU command
>> line. Both parameters will be passed to the guest on a stsi subcode
>> 3.2.2 call and will then be checked.
>>
>> We also compare the configured cpu numbers against the smp reported
>> numbers and if the reserved + configured add up to the total number
>> reported.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>>
>> * Tabify on struct
>> * Moved prefix_push up a bit
>> * Replaced returns with goto out to pop prefix
>>
>> ---
>>  s390x/stsi.c        | 73 +++++++++++++++++++++++++++++++++++++++++++++
>>  s390x/unittests.cfg |  1 +
>>  2 files changed, 74 insertions(+)
>>
>> diff --git a/s390x/stsi.c b/s390x/stsi.c
>> index e9206bca137d2edb..17ad33eefb9c948a 100644
>> --- a/s390x/stsi.c
>> +++ b/s390x/stsi.c
>> @@ -14,7 +14,28 @@
>>  #include <asm/page.h>
>>  #include <asm/asm-offsets.h>
>>  #include <asm/interrupt.h>
>> +#include <smp.h>
>>  
>> +struct stsi_322 {
>> +    uint8_t reserved[31];
>> +    uint8_t count;
>> +    struct {
>> +	uint8_t reserved2[4];
>> +	uint16_t total_cpus;
>> +	uint16_t conf_cpus;
>> +	uint16_t standby_cpus;
>> +	uint16_t reserved_cpus;
>> +	uint8_t name[8];
>> +	uint32_t caf;
>> +	uint8_t cpi[16];
>> +	uint8_t reserved5[3];
>> +	uint8_t ext_name_encoding;
>> +	uint32_t reserved3;
>> +	uint8_t uuid[16];
>> +    } vm[8];
>> +    uint8_t reserved4[1504];
>> +    uint8_t ext_names[8][256];
> 
> Sorry, still no proper use of tabs. (can fixup if you agree)
> 
Sure, go ahead



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

  reply	other threads:[~2020-03-31  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2ebc49ff-479a-351d-36f9-cb79fe4b9804@redhat.com>
2020-03-31  7:14 ` [kvm-unit-tests PATCH v3] s390x: Add stsi 3.2.2 tests Janosch Frank
2020-03-31  8:24   ` David Hildenbrand
2020-03-31  8:29     ` Janosch Frank [this message]
2020-03-31  8:38       ` David Hildenbrand
2020-03-31  9:35   ` Cornelia Huck
2020-03-31  9:46     ` Janosch Frank
2020-03-31 10:16       ` Cornelia Huck
2020-03-31 10:45         ` Janosch Frank
2020-03-31 17:24     ` David Hildenbrand
2020-04-01  7:20       ` Janosch Frank
2020-04-01  7:24         ` Cornelia Huck

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=4d36c625-8c05-2027-24b9-e7b66839ca45@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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;
as well as URLs for NNTP newsgroup(s).