From: Pierre Morel <pmorel@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, qemu-s390x@nongnu.org
Cc: david@redhat.com, cohuck@redhat.com,
richard.henderson@linaro.org, qemu-devel@nongnu.org,
pasic@linux.ibm.com, borntraeger@de.ibm.com
Subject: Re: [PATCH v3 2/4] s390x: kvm: topology: interception of PTF instruction
Date: Wed, 17 Nov 2021 14:06:28 +0100 [thread overview]
Message-ID: <c5ecaf42-3eac-85a3-b6c1-66bfab9f6f3e@linux.ibm.com> (raw)
In-Reply-To: <ae0cf5c1-b0b8-0758-7c38-35c1845201ba@redhat.com>
On 10/13/21 09:25, Thomas Huth wrote:
> On 16/09/2021 15.50, Pierre Morel wrote:
>> When the host supports the CPU topology facility, the PTF
>> instruction with function code 2 is interpreted by the SIE,
>> provided that the userland hypervizor activates the interpretation
>> by using the KVM_CAP_S390_CPU_TOPOLOGY KVM extension.
>>
>> The PTF instructions with function code 0 and 1 are intercepted
>> and must be emulated by the userland hypervizor.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> ---
>> hw/s390x/s390-virtio-ccw.c | 36 ++++++++++++++++++++++++++++++
>> include/hw/s390x/s390-virtio-ccw.h | 6 +++++
>> target/s390x/kvm/kvm.c | 15 +++++++++++++
>> 3 files changed, 57 insertions(+)
>>
>> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
>> index 61aeccb163..894f013139 100644
>> --- a/hw/s390x/s390-virtio-ccw.c
>> +++ b/hw/s390x/s390-virtio-ccw.c
>> @@ -404,6 +404,42 @@ static void
>> s390_pv_prepare_reset(S390CcwMachineState *ms)
>> s390_pv_prep_reset();
>> }
>
> Could you please add a comment in front of this function, with some
> explanations? If I've got that right, it's currently rather only a
> "dummy" function, rejecting FC 0 and 1, and FC 2 is always handled by
> the SIE, right?
I just saw I did not answer this question.
Yes function code 2 is handled by the SIE but it is not really a dummy
function as without it PTF 0 or 1 would trigger a program check.
I will add a comment basically:
"We assume horizontal topology, the only one supported currently by
Linux consequently we answer to function code 0 requesting horizontal
polarization that it is already the current polarization and reject
vertical polarization request without further explanation."
regards,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2021-11-17 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 13:50 [PATCH v3 0/4] s390x: CPU Topology Pierre Morel
2021-09-16 13:50 ` [PATCH v3 1/4] linux-headers update Pierre Morel
2021-09-16 13:50 ` [PATCH v3 2/4] s390x: kvm: topology: interception of PTF instruction Pierre Morel
2021-10-13 7:25 ` Thomas Huth
2021-10-13 7:55 ` Pierre Morel
2021-10-13 9:11 ` Thomas Huth
2021-10-14 8:09 ` Pierre Morel
2021-10-21 8:44 ` Pierre Morel
2021-11-17 13:06 ` Pierre Morel [this message]
2021-09-16 13:50 ` [PATCH v3 3/4] s390x: topology: CPU topology objects and structures Pierre Morel
2021-10-14 7:16 ` Thomas Huth
2021-10-14 12:04 ` Pierre Morel
2021-09-16 13:50 ` [PATCH v3 4/4] s390x: topology: implementating Store Topology System Information Pierre Morel
2021-10-13 8:20 ` Thomas Huth
2021-10-13 8:40 ` 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=c5ecaf42-3eac-85a3-b6c1-66bfab9f6f3e@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).