From: Janosch Frank <frankja@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: thuth@redhat.com, kvm@vger.kernel.org, imbrenda@linux.ibm.com,
david@redhat.com, nrb@linux.ibm.com, nsg@linux.ibm.com,
cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 2/2] s390x: sclp: Implement SCLP_RC_INSUFFICIENT_SCCB_LENGTH
Date: Thu, 1 Jun 2023 10:03:06 +0200 [thread overview]
Message-ID: <3dc8e019-a3c1-8446-08ed-f76a9064f954@linux.ibm.com> (raw)
In-Reply-To: <20230530124056.18332-3-pmorel@linux.ibm.com>
On 5/30/23 14:40, Pierre Morel wrote:
> If SCLP_CMDW_READ_SCP_INFO fails due to a short buffer, retry
> with a greater buffer.
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
You've been testing using all possible cpus, haven't you?
> }
>
> -static void sclp_read_scp_info(ReadInfo *ri, int length)
> +static bool sclp_read_scp_info_extended(unsigned int command, ReadInfo *ri)
> +{
> + int cc;
> +
> + if (!test_facility(140)) {
> + report_abort("S390_FEAT_EXTENDED_LENGTH_SCCB missing");
That's the QEMU name for the facility, isn't it?
"extended-length-SCCB facility is missing" might be better since that's
the name that the architecture specifies for that feature.
> + return false;
> + }
> + if (ri->h.length > (2 * PAGE_SIZE)) {
sizeof() would reduce the locations that we have to touch if we ever
want to increase the buffer in the future.
> + report_abort("SCLP_READ_INFO expected size too big");
> + return false;
> + }
> +
> + sclp_mark_busy();
> + memset(&ri->h, 0, sizeof(ri->h));
> + ri->h.length = 2 * PAGE_SIZE;
Same here
> +
> + cc = sclp_service_call(command, ri);
> + if (cc) {
> + report_abort("SCLP_READ_INFO error");
> + return false;
> + }
> + if (ri->h.response_code != SCLP_RC_NORMAL_READ_COMPLETION) {
> + report_abort("SCLP_READ_INFO error %02x", ri->h.response_code);
> + return false;
> + }
> +
> + return true;
> +}
> +
> +static void sclp_read_scp_info(ReadInfo *ri)
> {
> unsigned int commands[] = { SCLP_CMDW_READ_SCP_INFO_FORCED,
> SCLP_CMDW_READ_SCP_INFO };
> + int length = PAGE_SIZE;
> int i, cc;
>
> for (i = 0; i < ARRAY_SIZE(commands); i++) {
> @@ -101,19 +133,29 @@ static void sclp_read_scp_info(ReadInfo *ri, int length)
> ri->h.length = length;
>
> cc = sclp_service_call(commands[i], ri);
> - if (cc)
> - break;
> - if (ri->h.response_code == SCLP_RC_NORMAL_READ_COMPLETION)
> + if (cc) {
> + report_abort("SCLP_READ_INFO error");
> return;
> - if (ri->h.response_code != SCLP_RC_INVALID_SCLP_COMMAND)
> + }
> +
> + switch (ri->h.response_code) {
> + case SCLP_RC_NORMAL_READ_COMPLETION:
> + return;
> + case SCLP_RC_INVALID_SCLP_COMMAND:
> break;
> + case SCLP_RC_INSUFFICIENT_SCCB_LENGTH:
> + sclp_read_scp_info_extended(commands[i], ri);
> + return;
> + default:
> + report_abort("READ_SCP_INFO failed");
> + return;
> + }
> }
> - report_abort("READ_SCP_INFO failed");
> }
>
> void sclp_read_info(void)
> {
> - sclp_read_scp_info((void *)_read_info, SCCB_SIZE);
Why did you remove that?
You could have re-tried with the extended-length in
sclp_read_scp_info(). Or you could return the rc and introduce a tiny
function that tries both lengths depending on the rc.
> + sclp_read_scp_info((void *)_read_info);
> read_info = (ReadInfo *)_read_info;
> }
>
next prev parent reply other threads:[~2023-06-01 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:40 [kvm-unit-tests PATCH v3 0/2] Fixing infinite loop on SCLP READ SCP INFO error Pierre Morel
2023-05-30 12:40 ` [kvm-unit-tests PATCH v3 1/2] s390x: sclp: consider monoprocessor on read_info error Pierre Morel
2023-06-01 11:52 ` Nico Boehr
2023-06-01 12:32 ` Pierre Morel
2023-05-30 12:40 ` [kvm-unit-tests PATCH v3 2/2] s390x: sclp: Implement SCLP_RC_INSUFFICIENT_SCCB_LENGTH Pierre Morel
2023-06-01 8:03 ` Janosch Frank [this message]
2023-06-01 10:15 ` Pierre Morel
2023-06-01 11:59 ` Nico Boehr
2023-06-01 12:55 ` Pierre Morel
2023-06-01 13:32 ` Janosch Frank
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=3dc8e019-a3c1-8446-08ed-f76a9064f954@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--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