From: Pierre Morel <pmorel@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@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 16:23:28 +0200 [thread overview]
Message-ID: <31fe25db-6df8-90dc-81f4-d37ad17add5e@linux.ibm.com> (raw)
In-Reply-To: <20210809115345.3f0eb1c4@p-imbrenda>
On 8/9/21 11:53 AM, Claudio Imbrenda wrote:
> 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>
Thanks,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2021-08-09 14:23 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
2021-08-09 14:23 ` Pierre Morel [this message]
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=31fe25db-6df8-90dc-81f4-d37ad17add5e@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=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=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