From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v4 1/3] s390x: smp: move sigp calls with invalid cpu address to array
Date: Tue, 16 Aug 2022 14:12:45 +0200 [thread overview]
Message-ID: <20220816141245.7983eebf@p-imbrenda> (raw)
In-Reply-To: <20220810074616.1223561-2-nrb@linux.ibm.com>
On Wed, 10 Aug 2022 09:46:14 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:
> We have the nice array to test SIGP calls with invalid CPU addresses.
> Move the SIGP cases there to eliminate some of the duplicated code in
> test_emcall and test_cond_emcall.
>
> Since adding coverage for invalid CPU addresses in the ecall case is now
> trivial, do that as well.
>
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> s390x/smp.c | 18 +++---------------
> 1 file changed, 3 insertions(+), 15 deletions(-)
>
> diff --git a/s390x/smp.c b/s390x/smp.c
> index 0df4751f9cee..34ae91c3fe12 100644
> --- a/s390x/smp.c
> +++ b/s390x/smp.c
> @@ -30,6 +30,9 @@ static const struct sigp_invalid_cases cases_invalid_cpu_addr[] = {
> { SIGP_STOP, "stop with invalid CPU address" },
> { SIGP_START, "start with invalid CPU address" },
> { SIGP_CPU_RESET, "reset with invalid CPU address" },
> + { SIGP_COND_EMERGENCY_SIGNAL, "conditional emcall with invalid CPU address" },
> + { SIGP_EMERGENCY_SIGNAL, "emcall with invalid CPU address" },
> + { SIGP_EXTERNAL_CALL, "ecall with invalid CPU address" },
> { INVALID_ORDER_CODE, "invalid order code and CPU address" },
> { SIGP_SENSE, "sense with invalid CPU address" },
> { SIGP_STOP_AND_STORE_STATUS, "stop and store status with invalid CPU address" },
> @@ -329,7 +332,6 @@ static void emcall(void)
> static void test_emcall(void)
> {
> struct psw psw;
> - int cc;
> psw.mask = extract_psw_mask();
> psw.addr = (unsigned long)emcall;
>
> @@ -343,13 +345,6 @@ static void test_emcall(void)
> wait_for_flag();
> smp_cpu_stop(1);
>
> - report_prefix_push("invalid CPU address");
> -
> - cc = sigp(INVALID_CPU_ADDRESS, SIGP_EMERGENCY_SIGNAL, 0, NULL);
> - report(cc == 3, "CC = 3");
> -
> - report_prefix_pop();
> -
> report_prefix_pop();
> }
>
> @@ -368,13 +363,6 @@ static void test_cond_emcall(void)
> goto out;
> }
>
> - report_prefix_push("invalid CPU address");
> -
> - cc = sigp(INVALID_CPU_ADDRESS, SIGP_COND_EMERGENCY_SIGNAL, 0, NULL);
> - report(cc == 3, "CC = 3");
> -
> - report_prefix_pop();
> -
> report_prefix_push("success");
> set_flag(0);
>
next prev parent reply other threads:[~2022-08-16 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 7:46 [kvm-unit-tests PATCH v4 0/3] s390x: add tests for SIGP call orders in enabled wait Nico Boehr
2022-08-10 7:46 ` [kvm-unit-tests PATCH v4 1/3] s390x: smp: move sigp calls with invalid cpu address to array Nico Boehr
2022-08-16 12:12 ` Claudio Imbrenda [this message]
2022-08-10 7:46 ` [kvm-unit-tests PATCH v4 2/3] s390x: smp: use an array for sigp calls Nico Boehr
2022-08-16 15:09 ` Claudio Imbrenda
2022-08-10 7:46 ` [kvm-unit-tests PATCH v4 3/3] s390x: smp: add tests for calls in wait state Nico Boehr
2022-08-16 15:37 ` Claudio Imbrenda
2022-08-17 7:34 ` Janosch Frank
2022-08-17 14:50 ` Nico Boehr
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=20220816141245.7983eebf@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@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