From: Pierre Morel <pmorel@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, thuth@redhat.com, kvm@vger.kernel.org,
cohuck@redhat.com, imbrenda@linux.ibm.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v4 3/4] s390x: topology: Check the Perform Topology Function
Date: Tue, 15 Feb 2022 09:29:10 +0100 [thread overview]
Message-ID: <920663f6-637d-e442-62a9-4a3ac9ab12d6@linux.ibm.com> (raw)
In-Reply-To: <8dd704d23f8a14907ed2a7f28ec3ac52685ab96c.camel@linux.ibm.com>
On 2/9/22 12:37, Nico Boehr wrote:
> On Tue, 2022-02-08 at 14:27 +0100, Pierre Morel wrote:
>> We check the PTF instruction.
>
> You could test some very basic things as well:
>
> - you get a privileged pgm int in problem state,
> - reserved bits in first operand cause specification pgm int,
> - reserved FC values result in a specification pgm int,
> - second operand is ignored.
>
>>
>> - We do not expect to support vertical polarization.
>>
>> - We do not expect the Modified Topology Change Report to be
> [...]
>
> Forgive me if I'm missing something, but why _Modified_ Topology Change
> Report?
This does only exist in my mind the real name is indeed only Topology
change report.
>
>> diff --git a/s390x/topology.c b/s390x/topology.c
>> new file mode 100644
>> index 00000000..a1f9ce51
>> --- /dev/null
>> +++ b/s390x/topology.c
>
> [...]
>
>> +static int ptf(unsigned long fc, unsigned long *rc)
>> +{
>> + int cc;
>> +
>> + asm volatile(
>> + " .insn rre,0xb9a20000,%1,0\n"
>> + " ipm %0\n"
>> + " srl %0,28\n"
>> + : "=d" (cc), "+d" (fc)
>> + : "d" (fc)
>
> Why list fc here again?
>
>
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2022-02-15 8:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 13:27 [kvm-unit-tests PATCH v4 0/4] S390x: CPU Topology Information Pierre Morel
2022-02-08 13:27 ` [kvm-unit-tests PATCH v4 1/4] s390x: lib: Add SCLP toplogy nested level Pierre Morel
2022-02-08 13:27 ` [kvm-unit-tests PATCH v4 2/4] s390x: stsi: Define vm_is_kvm to be used in different tests Pierre Morel
2022-02-08 15:31 ` Janosch Frank
2022-02-08 15:43 ` Nico Boehr
2022-02-14 8:01 ` Pierre Morel
2022-02-14 9:18 ` Pierre Morel
2022-02-08 15:35 ` Nico Boehr
2022-02-14 7:55 ` Pierre Morel
2022-02-15 11:18 ` Claudio Imbrenda
2022-02-08 13:27 ` [kvm-unit-tests PATCH v4 3/4] s390x: topology: Check the Perform Topology Function Pierre Morel
2022-02-09 11:37 ` Nico Boehr
2022-02-14 9:21 ` Pierre Morel
2022-02-15 8:29 ` Pierre Morel [this message]
2022-02-15 8:50 ` Pierre Morel
2022-02-15 9:21 ` Pierre Morel
2022-02-15 9:44 ` Pierre Morel
2022-02-15 10:28 ` Nico Boehr
2022-02-08 13:27 ` [kvm-unit-tests PATCH v4 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=920663f6-637d-e442-62a9-4a3ac9ab12d6@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=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