From: Pierre Morel <pmorel@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: thuth@redhat.com, kvm@vger.kernel.org, cohuck@redhat.com,
imbrenda@linux.ibm.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v1 3/4] s390x: topology: check the Perform Topology Function
Date: Mon, 9 Aug 2021 17:57:25 +0200 [thread overview]
Message-ID: <78450ffb-eff7-7525-41db-2f4e58b5411f@linux.ibm.com> (raw)
In-Reply-To: <9590216d-9cfd-0725-e77a-9bd13f8a2d60@linux.ibm.com>
On 8/9/21 12:12 PM, Janosch Frank wrote:
> On 8/9/21 10:48 AM, Pierre Morel wrote:
>> We check the PTF instruction.
>>
>> - We do not expect to support vertical polarization.
>>
>> - We do not expect the Modified Topology Change Report to be
>> pending or not at the moment the first PTF instruction with
>> PTF_CHECK function code is done as some code already did run
>> a polarization change may have occur.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
>> s390x/Makefile | 1 +
>> s390x/topology.c | 87 +++++++++++++++++++++++++++++++++++++++++++++
>> s390x/unittests.cfg | 3 ++
>> 3 files changed, 91 insertions(+)
>> create mode 100644 s390x/topology.c
>>
>> diff --git a/s390x/Makefile b/s390x/Makefile
>> index 6565561b..c82b7dbf 100644
>> --- a/s390x/Makefile
>> +++ b/s390x/Makefile
>> @@ -24,6 +24,7 @@ tests += $(TEST_DIR)/mvpg.elf
>> tests += $(TEST_DIR)/uv-host.elf
>> tests += $(TEST_DIR)/edat.elf
>> tests += $(TEST_DIR)/mvpg-sie.elf
>> +tests += $(TEST_DIR)/topology.elf
>>
>> tests_binary = $(patsubst %.elf,%.bin,$(tests))
>> ifneq ($(HOST_KEY_DOCUMENT),)
>> diff --git a/s390x/topology.c b/s390x/topology.c
>> new file mode 100644
>> index 00000000..4146189a
>> --- /dev/null
>> +++ b/s390x/topology.c
>> @@ -0,0 +1,87 @@
>> +/* SPDX-License-Identifier: GPL-2.0-only */
>> +/*
>> + * CPU Topology
>> + *
>> + * Copyright (c) 2021 IBM Corp
>> + *
>> + * Authors:
>> + * Pierre Morel <pmorel@linux.ibm.com>
>> + */
>> +
>> +#include <libcflat.h>
>> +#include <asm/page.h>
>> +#include <asm/asm-offsets.h>
>> +#include <asm/interrupt.h>
>> +#include <asm/facility.h>
>> +#include <smp.h>
>> +#include <sclp.h>
>> +
>> +static uint8_t pagebuf[PAGE_SIZE * 2] __attribute__((aligned(PAGE_SIZE * 2)));
>
> We don't actually need that I made a mistake in stsi_get_fc().
> I'll comment in the other patch.
OK I saw.
thx
>
>> +int machine_level;
>> +int mnest;
>> +
>> +#define PTF_HORIZONTAL 0
>> +#define PTF_VERTICAL 1
>
> PTF_REQ_*
OK
>
>> +#define PTF_CHECK 2> +
>> +#define PTF_ERR_NO_REASON 0
>> +#define PTF_ERR_ALRDY_POLARIZED 1
>> +#define PTF_ERR_IN_PROGRESS 2
>> +
>> +static int ptf(unsigned long fc, unsigned long *rc)
>> +{
>> + int cc;
>> +
>> + asm volatile(
>> + " .insn rre,0xb9a20000,%1,%1\n"
>> + " ipm %0\n"
>> + " srl %0,28\n"
>> + : "=d" (cc), "+d" (fc)
>> + : "d" (fc)
>> + : "cc");
>> +
>> + *rc = fc >> 8;
>> + return cc;
>> +}
>> +
>> +static void test_ptf(void)
>> +{
>> + unsigned long rc;
>> + int cc;
>> +
>> + report_prefix_push("Topology Report pending");
>> + /*
>> + * At this moment the topology may already have changed
>> + * since the VM has been started.
>> + * However, we can test if a second PTF instruction
>> + * reports that the topology did not change since the
>> + * preceding PFT instruction.
>> + */
>> + ptf(PTF_CHECK, &rc);
>> + cc = ptf(PTF_CHECK, &rc)> + report(cc == 0, "PTF check clear");
>
> Please leave a \n after a report for readability.
OK
>
>> + cc = ptf(PTF_HORIZONTAL, &rc);
>> + report(cc == 2 && rc == PTF_ERR_ALRDY_POLARIZED,
>> + "PTF horizontal already configured");
>> + cc = ptf(PTF_VERTICAL, &rc);
>> + report(cc == 2 && rc == PTF_ERR_NO_REASON,
>> + "PTF vertical non possible");
>
> I've yet to look into your KVM/qemu code so I don't really understand
> what you're testing here and why we can expect to get those results.
In KVM please ignore the stupid patch 3 commented by Heiko and that will
disappear.
It changes nothing to the first two patches.
OK, I will add some comments to explain what we await and why.
>
> Maybe add a comment?
> Also what will happen if we start this test under LPAR or z/VM, will it
> fail?
The last one may fail, PTF would succeed AFAIU under LPAR.
For z/VM, no idea.
>
>> +
>> + report_prefix_pop();
>> +}
>> +
>> +int main(int argc, char *argv[])
>> +{
>> + report_prefix_push("stsi");
>
> Where did you copy that test from? :-)
:) yes cut and paste, I will change trhe prefix to "CPU Topology"
>
>> +
>> + if (!test_facility(11)) {
>> + report_skip("Topology facility not present");
>> + goto end;
>> + }
>> +
>> + report_info("Machine level %ld", stsi_get_fc(pagebuf));
>> +
>> + test_ptf();
>> +end:
>
> report_prefix_pop is missing here
Right.
will add.
>
>> + return report_summary();
>> +}
>> diff --git a/s390x/unittests.cfg b/s390x/unittests.cfg
>> index 9e1802fd..0f84d279 100644
>> --- a/s390x/unittests.cfg
>> +++ b/s390x/unittests.cfg
>> @@ -109,3 +109,6 @@ file = edat.elf
>>
>> [mvpg-sie]
>> file = mvpg-sie.elf
>> +
>> +[topology]
>> +file = topology.elf
>>
>
Thanks,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2021-08-09 15:57 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
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 [this message]
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=78450ffb-eff7-7525-41db-2f4e58b5411f@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