public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, thuth@redhat.com, kvm@vger.kernel.org,
	imbrenda@linux.ibm.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 1/4] s390x: lib: Add SCLP toplogy nested level
Date: Thu, 12 Aug 2021 14:56:49 +0200	[thread overview]
Message-ID: <87czqivn1q.fsf@redhat.com> (raw)
In-Reply-To: <1628612544-25130-2-git-send-email-pmorel@linux.ibm.com>

On Tue, Aug 10 2021, Pierre Morel <pmorel@linux.ibm.com> wrote:

> The maximum CPU Topology nested level is available with the SCLP
> READ_INFO command inside the byte at offset 15 of the ReadInfo
> structure.
>
> Let's return this information to check the number of topology nested
> information available with the STSI 15.1.x instruction.
>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
>  lib/s390x/sclp.c | 6 ++++++
>  lib/s390x/sclp.h | 4 +++-
>  2 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/lib/s390x/sclp.c b/lib/s390x/sclp.c
> index 9502d161..ee379ddf 100644
> --- a/lib/s390x/sclp.c
> +++ b/lib/s390x/sclp.c
> @@ -123,6 +123,12 @@ int sclp_get_cpu_num(void)
>  	return read_info->entries_cpu;
>  }
>  
> +int sclp_get_stsi_parm(void)
> +{
> +	assert(read_info);
> +	return read_info->stsi_parm;

Is this a generic "stsi parm", or always the concrete topology nested
level? IOW, is that name good, or too generic?

> +}
> +
>  CPUEntry *sclp_get_cpu_entries(void)
>  {
>  	assert(read_info);


  parent reply	other threads:[~2021-08-12 12:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 16:22 [kvm-unit-tests PATCH v2 0/4] S390x: CPU Topology Information Pierre Morel
2021-08-10 16:22 ` [kvm-unit-tests PATCH v2 1/4] s390x: lib: Add SCLP toplogy nested level Pierre Morel
2021-08-11 14:59   ` Janosch Frank
2021-08-12  8:36     ` Pierre Morel
2021-08-12 12:56   ` Cornelia Huck [this message]
2021-08-12 15:05     ` Pierre Morel
2021-08-12 15:12       ` Cornelia Huck
2021-08-10 16:22 ` [kvm-unit-tests PATCH v2 2/4] s390x: lib: Simplify stsi_get_fc and move it to library Pierre Morel
2021-08-11 15:01   ` Janosch Frank
2021-08-12  8:38     ` Pierre Morel
2021-08-18  7:45   ` Thomas Huth
2021-08-23  9:17     ` Pierre Morel
2021-08-10 16:22 ` [kvm-unit-tests PATCH v2 3/4] s390x: topology: Check the Perform Topology Function Pierre Morel
2021-08-12  9:38   ` Janosch Frank
2021-08-12 11:40     ` Pierre Morel
2021-08-10 16:22 ` [kvm-unit-tests PATCH v2 4/4] s390x: topology: Checking Configuration Topology Information 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=87czqivn1q.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --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