From: Pierre Morel <pmorel@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, frankja@linux.ibm.com,
david@redhat.com, cohuck@redhat.com, drjones@redhat.com
Subject: Re: [kvm-unit-tests PATCH v12 9/9] s390x: css: ssch/tsch with sense and interrupt
Date: Tue, 14 Jul 2020 13:51:36 +0200 [thread overview]
Message-ID: <b197e520-7fb4-bb14-2641-aa4de472fe12@linux.ibm.com> (raw)
In-Reply-To: <865cb20f-ac2d-f54a-6613-5d580675eb97@redhat.com>
On 2020-07-14 13:38, Thomas Huth wrote:
> On 14/07/2020 13.15, Pierre Morel wrote:
>> After a channel is enabled we start a SENSE_ID command using
>> the SSCH instruction to recognize the control unit and device.
>>
>> This tests the success of SSCH, the I/O interruption and the TSCH
>> instructions.
>>
>> The SENSE_ID command response is tested to report 0xff inside
>> its reserved field and to report the same control unit type
>> as the cu_type kernel argument.
>>
>> Without the cu_type kernel argument, the test expects a device
>> with a default control unit type of 0x3832, a.k.a virtio-net-ccw.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
> [...]
>> @@ -102,6 +113,19 @@ struct irb {
>> uint32_t emw[8];
>> } __attribute__ ((aligned(4)));
>>
>> +#define CCW_CMD_SENSE_ID 0xe4
>> +#define CSS_SENSEID_COMMON_LEN 8
>> +struct senseid {
>> + /* common part */
>> + uint8_t reserved; /* always 0x'FF' */
>> + uint16_t cu_type; /* control unit type */
>> + uint8_t cu_model; /* control unit model */
>> + uint16_t dev_type; /* device type */
>> + uint8_t dev_model; /* device model */
>> + uint8_t unused; /* padding byte */
>> + uint8_t padding[256 - 10]; /* Extra padding for CCW */
>> +} __attribute__ ((aligned(4))) __attribute__ ((packed));
>
> Is that padding[256 - 10] right? If I count right, there are only 8
> bytes before the padding field, so "10" sounds wrong here?
>
No it is not, should be 248 or 256 - 8.
> [...]
>> diff --git a/lib/s390x/css_lib.c b/lib/s390x/css_lib.c
>> index e47a945..274c293 100644
>> --- a/lib/s390x/css_lib.c
>> +++ b/lib/s390x/css_lib.c
> [...]
>> +/*
>> + * css_residual_count
>> + * Return the residual count, if it is valid.
>> + *
>> + * Return value:
>> + * Success: the residual count
>> + * Not meaningful: -1 (-1 can not be a valid count)
>> + */
>> +int css_residual_count(unsigned int schid)
>> +{
>> +
>> + if (!(irb.scsw.ctrl & (SCSW_SC_PENDING | SCSW_SC_PRIMARY)))
>> + goto invalid;
>> +
>> + if (irb.scsw.dev_stat)
>> + if (irb.scsw.sch_stat & ~(SCSW_SCHS_PCI | SCSW_SCHS_IL))
>> + goto invalid;
>> +
>> + return irb.scsw.count;
>> +
>> +invalid:
>> + return -1;
>> +}
>
> Cosmetical nit: Unless you want to add something between "invalid:" and
> "return -1" later, I'd rather replace "goto invalid" with "return -1"
> and get rid of the "invalid" label here.
>
> Thomas
>
OK, since I need to respin for the padding above.
Thanks,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2020-07-14 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 11:15 [kvm-unit-tests PATCH v12 0/9] s390x: Testing the Channel Subsystem I/O Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 1/9] s390x: saving regs for interrupts Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 2/9] s390x: I/O interrupt registration Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 3/9] s390x: export the clock get_clock_ms() utility Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 4/9] s390x: clock and delays calculations Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 5/9] s390x: define function to wait for interrupt Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 6/9] s390x: Library resources for CSS tests Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 7/9] s390x: css: stsch, enumeration test Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 8/9] s390x: css: msch, enable test Pierre Morel
2020-07-14 11:15 ` [kvm-unit-tests PATCH v12 9/9] s390x: css: ssch/tsch with sense and interrupt Pierre Morel
2020-07-14 11:38 ` Thomas Huth
2020-07-14 11:51 ` Pierre Morel [this message]
2020-07-15 10:15 ` Cornelia Huck
2020-07-15 10:49 ` Pierre Morel
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=b197e520-7fb4-bb14-2641-aa4de472fe12@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=drjones@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