public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: "Nina Schoetterl-Glausch" <nsg@linux.ibm.com>,
	"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
	"Nico Böhr" <nrb@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org,
	Andrew Jones <andrew.jones@linux.dev>,
	Colton Lewis <coltonlewis@google.com>,
	Nikos Nikoleris <nikos.nikoleris@arm.com>,
	Ricardo Koller <ricarkol@google.com>,
	Sean Christopherson <seanjc@google.com>
Subject: Re: [kvm-unit-tests PATCH 5/9] s390x: topology: Refine stsi header test
Date: Wed, 11 Oct 2023 13:16:43 +0200	[thread overview]
Message-ID: <fc59fb56-4848-4282-bec5-bdef40c817ff@linux.ibm.com> (raw)
In-Reply-To: <20231011085635.1996346-6-nsg@linux.ibm.com>

On 10/11/23 10:56, Nina Schoetterl-Glausch wrote:
> Add checks for length field.
> Also minor refactor.
> 
> Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> ---
>   s390x/topology.c | 15 +++++++++------
>   1 file changed, 9 insertions(+), 6 deletions(-)
> 
> diff --git a/s390x/topology.c b/s390x/topology.c
> index 5374582f..0ba57986 100644
> --- a/s390x/topology.c
> +++ b/s390x/topology.c
> @@ -187,18 +187,22 @@ static void stsi_check_maxcpus(struct sysinfo_15_1_x *info)
>   }
>   
>   /*
> - * stsi_check_mag
> + * stsi_check_header
>    * @info: Pointer to the stsi information
> + * @sel2: stsi selector 2 value
>    *
>    * MAG field should match the architecture defined containers
>    * when MNEST as returned by SCLP matches MNEST of the SYSIB.
>    */
> -static void stsi_check_mag(struct sysinfo_15_1_x *info)
> +static void stsi_check_header(struct sysinfo_15_1_x *info, int sel2)
>   {
>   	int i;
>   
> -	report_prefix_push("MAG");
> +	report_prefix_push("Header");
>   
> +	report(IS_ALIGNED(info->length, 8), "Length %d multiple of 8", info->length);

STSI 15 works on Words, not DWords, no?
So we need to check length against 4, not 8.

> +	report(info->length < PAGE_SIZE, "Length %d in bounds", info->length);
> +	report(sel2 == info->mnest, "Valid mnest");
>   	stsi_check_maxcpus(info);
>   
>   	/*
> @@ -326,7 +330,6 @@ static int stsi_get_sysib(struct sysinfo_15_1_x *info, int sel2)
>   
>   	if (max_nested_lvl >= sel2) {
>   		report(!ret, "Valid instruction");
> -		report(sel2 == info->mnest, "Valid mnest");
>   	} else {
>   		report(ret, "Invalid instruction");
>   	}
> @@ -365,7 +368,7 @@ static void check_sysinfo_15_1_x(struct sysinfo_15_1_x *info, int sel2)
>   		goto vertical;
>   	}
>   
> -	stsi_check_mag(info);
> +	stsi_check_header(info, sel2);
>   	stsi_check_tle_coherency(info);
>   
>   vertical:
> @@ -378,7 +381,7 @@ vertical:
>   		goto end;
>   	}
>   
> -	stsi_check_mag(info);
> +	stsi_check_header(info, sel2);
>   	stsi_check_tle_coherency(info);
>   	report_prefix_pop();
>   


  reply	other threads:[~2023-10-11 11:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  8:56 [kvm-unit-tests PATCH 0/9] s390x: topology: Fixes and extension Nina Schoetterl-Glausch
2023-10-11  8:56 ` [kvm-unit-tests PATCH 1/9] s390x: topology: Fix report message Nina Schoetterl-Glausch
2023-10-11 10:56   ` Janosch Frank
2023-10-11 11:10     ` Nina Schoetterl-Glausch
2023-10-11 11:30       ` Janosch Frank
2023-10-11 11:41         ` Nina Schoetterl-Glausch
2023-10-11 13:36   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 2/9] s390x: topology: Use parameter in stsi_get_sysib Nina Schoetterl-Glausch
2023-10-11 11:05   ` Janosch Frank
2023-10-12 14:44   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 3/9] s390x: topology: Fix parsing loop Nina Schoetterl-Glausch
2023-10-11 11:07   ` Janosch Frank
2023-10-11 11:16     ` Nina Schoetterl-Glausch
2023-10-12 14:46   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 4/9] s390x: topology: Don't use non unique message Nina Schoetterl-Glausch
2023-10-11 11:11   ` Janosch Frank
2023-10-13  8:16   ` Nico Boehr
2023-10-13  9:18     ` Nina Schoetterl-Glausch
2023-10-11  8:56 ` [kvm-unit-tests PATCH 5/9] s390x: topology: Refine stsi header test Nina Schoetterl-Glausch
2023-10-11 11:16   ` Janosch Frank [this message]
2023-10-11 11:19     ` Nina Schoetterl-Glausch
2023-10-11 11:22       ` Janosch Frank
2023-10-17 12:31         ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 6/9] s390x: topology: Rename topology_core to topology_cpu Nina Schoetterl-Glausch
2023-10-11 11:31   ` Janosch Frank
2023-10-17 12:32   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 7/9] s390x: topology: Rewrite topology list test Nina Schoetterl-Glausch
2023-10-17 13:29   ` Nico Boehr
2023-10-11  8:56 ` [kvm-unit-tests PATCH 8/9] scripts: Implement multiline strings for extra_params Nina Schoetterl-Glausch
2023-10-19 10:50   ` Nico Boehr
2023-10-19 15:42     ` Nina Schoetterl-Glausch
2023-10-11  8:56 ` [kvm-unit-tests PATCH 9/9] s390x: topology: Add complex topology test Nina Schoetterl-Glausch
2023-10-19 10:58   ` 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=fc59fb56-4848-4282-bec5-bdef40c817ff@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=andrew.jones@linux.dev \
    --cc=coltonlewis@google.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nikos.nikoleris@arm.com \
    --cc=nrb@linux.ibm.com \
    --cc=nsg@linux.ibm.com \
    --cc=ricarkol@google.com \
    --cc=seanjc@google.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