From: Heiko Carstens <hca@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Pierre Morel <pmorel@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, borntraeger@de.ibm.com,
frankja@linux.ibm.com, cohuck@redhat.com, david@redhat.com,
thuth@redhat.com, gor@linux.ibm.com
Subject: Re: [PATCH v5 1/1] s390x: KVM: accept STSI for CPU topology information
Date: Thu, 9 Dec 2021 16:54:17 +0100 [thread overview]
Message-ID: <YbImqX/NEus71tZ1@osiris> (raw)
In-Reply-To: <20211209133616.650491fd@p-imbrenda>
On Thu, Dec 09, 2021 at 01:36:16PM +0100, Claudio Imbrenda wrote:
> On Mon, 22 Nov 2021 14:14:43 +0100
> Pierre Morel <pmorel@linux.ibm.com> wrote:
>
> > We let the userland hypervisor know if the machine support the CPU
> > topology facility using a new KVM capability: KVM_CAP_S390_CPU_TOPOLOGY.
> >
> > The PTF instruction will report a topology change if there is any change
> > with a previous STSI_15_1_2 SYSIB.
> > Changes inside a STSI_15_1_2 SYSIB occur if CPU bits are set or clear
> > inside the CPU Topology List Entry CPU mask field, which happens with
> > changes in CPU polarization, dedication, CPU types and adding or
> > removing CPUs in a socket.
> >
> > The reporting to the guest is done using the Multiprocessor
> > Topology-Change-Report (MTCR) bit of the utility entry of the guest's
> > SCA which will be cleared during the interpretation of PTF.
> >
> > To check if the topology has been modified we use a new field of the
> > arch vCPU to save the previous real CPU ID at the end of a schedule
> > and verify on next schedule that the CPU used is in the same socket.
> >
> > We assume in this patch:
> > - no polarization change: only horizontal polarization is currently
> > used in linux.
Why is this assumption necessary? The statement that Linux runs only
with horizontal polarization is not true.
next prev parent reply other threads:[~2021-12-09 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 13:14 [PATCH v5 0/1] s390x: KVM: CPU Topology Pierre Morel
2021-11-22 13:14 ` [PATCH v5 1/1] s390x: KVM: accept STSI for CPU topology information Pierre Morel
2021-12-07 9:43 ` Pierre Morel
2021-12-09 12:36 ` Claudio Imbrenda
2021-12-09 13:31 ` Pierre Morel
2021-12-09 15:54 ` Heiko Carstens [this message]
2021-12-13 10:05 ` Pierre Morel
2021-12-13 14:26 ` Pierre Morel
2021-12-13 15:21 ` Heiko Carstens
2021-12-13 15:46 ` Pierre Morel
2021-12-09 16:08 ` Janosch Frank
2021-12-13 10:16 ` Pierre Morel
2021-12-14 9:01 ` [PATCH v5 0/1] s390x: KVM: CPU Topology Alexandra Winter
2021-12-16 15:16 ` 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=YbImqX/NEus71tZ1@osiris \
--to=hca@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).