From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, frankja@linux.ibm.com,
thuth@redhat.com, kvm@vger.kernel.org, cohuck@redhat.com,
david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v1 1/4] s390x: lib: Add SCLP toplogy nested level
Date: Mon, 9 Aug 2021 11:53:45 +0200 [thread overview]
Message-ID: <20210809115345.3f0eb1c4@p-imbrenda> (raw)
In-Reply-To: <1628498934-20735-2-git-send-email-pmorel@linux.ibm.com>
On Mon, 9 Aug 2021 10:48:51 +0200
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;
> +}
> +
> CPUEntry *sclp_get_cpu_entries(void)
> {
> assert(read_info);
> diff --git a/lib/s390x/sclp.h b/lib/s390x/sclp.h
> index 28e526e2..1a365958 100644
> --- a/lib/s390x/sclp.h
> +++ b/lib/s390x/sclp.h
> @@ -146,7 +146,8 @@ typedef struct ReadInfo {
> SCCBHeader h;
> uint16_t rnmax;
> uint8_t rnsize;
> - uint8_t _reserved1[16 - 11]; /* 11-15 */
> + uint8_t _reserved1[15 - 11]; /* 11-14 */
> + uint8_t stsi_parm;
> uint16_t entries_cpu; /* 16-17 */
> uint16_t offset_cpu; /* 18-19 */
> uint8_t _reserved2[24 - 20]; /* 20-23 */
> @@ -322,6 +323,7 @@ void sclp_console_setup(void);
> void sclp_print(const char *str);
> void sclp_read_info(void);
> int sclp_get_cpu_num(void);
> +int sclp_get_stsi_parm(void);
> CPUEntry *sclp_get_cpu_entries(void);
> void sclp_facilities_setup(void);
> int sclp_service_call(unsigned int command, void *sccb);
next prev parent reply other threads:[~2021-08-09 10:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 8:48 [kvm-unit-tests PATCH v1 0/4] S390x: CPU Topology Information Pierre Morel
2021-08-09 8:48 ` [kvm-unit-tests PATCH v1 1/4] s390x: lib: Add SCLP toplogy nested level Pierre Morel
2021-08-09 9:53 ` Claudio Imbrenda [this message]
2021-08-09 14:23 ` Pierre Morel
2021-08-09 8:48 ` [kvm-unit-tests PATCH v1 2/4] s390x: lib: Move stsi_get_fc to library Pierre Morel
2021-08-09 9:53 ` Claudio Imbrenda
2021-08-09 10:16 ` Janosch Frank
2021-08-09 14:23 ` Pierre Morel
2021-08-09 8:48 ` [kvm-unit-tests PATCH v1 3/4] s390x: topology: check the Perform Topology Function Pierre Morel
2021-08-09 10:03 ` Claudio Imbrenda
2021-08-09 15:24 ` Pierre Morel
2021-08-09 10:12 ` Janosch Frank
2021-08-09 15:57 ` Pierre Morel
2021-08-09 8:48 ` [kvm-unit-tests PATCH v1 4/4] s390x: Topology: checking Configuration Topology Information Pierre Morel
2021-08-09 10:22 ` Claudio Imbrenda
2021-08-09 15:59 ` 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=20210809115345.3f0eb1c4@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@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