From: Pierre Morel <pmorel@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>, qemu-s390x@nongnu.org
Cc: qemu-devel@nongnu.org, pasic@linux.ibm.com,
richard.henderson@linaro.org, david@redhat.com, thuth@redhat.com,
cohuck@redhat.com, mst@redhat.com, pbonzini@redhat.com,
kvm@vger.kernel.org, ehabkost@redhat.com,
marcel.apfelbaum@gmail.com, eblake@redhat.com, armbru@redhat.com,
seiden@linux.ibm.com, nrb@linux.ibm.com, scgl@linux.ibm.com,
frankja@linux.ibm.com, berrange@redhat.com, clg@kaod.org
Subject: Re: [PATCH v13 4/7] s390x/cpu_topology: CPU topology migration
Date: Tue, 13 Dec 2022 18:40:10 +0100 [thread overview]
Message-ID: <ca338024-4e00-6e45-2eea-ffb034c854a9@linux.ibm.com> (raw)
In-Reply-To: <65b704e7-ee3a-c9de-45fa-b59c9731cb54@de.ibm.com>
On 12/13/22 14:26, Christian Borntraeger wrote:
> Am 08.12.22 um 10:44 schrieb Pierre Morel:
>> The migration can only take place if both source and destination
>> of the migration both use or both do not use the CPU topology
>> facility.
>>
>> We indicate a change in topology during migration postload for the
>> case the topology changed between source and destination.
>
> I dont get why we need this? If the target QEMU has topology it should
> already create this according to the configuration. WHy do we need a
> trigger?
We do not.
The first idea was to migrate the topology with a dedicated object but
after today discussion, it will be recreated by the admin on the target
and the MTCR will not be migrated but simply set to 1 on target start.
So next spin will not get migration included.
Regards,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2022-12-13 17:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 9:44 [PATCH v13 0/7] s390x: CPU Topology Pierre Morel
2022-12-08 9:44 ` [PATCH v13 1/7] s390x/cpu topology: Creating CPU topology device Pierre Morel
2022-12-09 13:50 ` Thomas Huth
2022-12-12 8:52 ` Pierre Morel
2022-12-09 14:51 ` Cédric Le Goater
2022-12-08 9:44 ` [PATCH v13 2/7] s390x/cpu topology: reporting the CPU topology to the guest Pierre Morel
2022-12-09 15:43 ` Cédric Le Goater
2022-12-12 9:21 ` Pierre Morel
2022-12-08 9:44 ` [PATCH v13 3/7] s390x/cpu_topology: resetting the Topology-Change-Report Pierre Morel
2022-12-08 9:44 ` [PATCH v13 4/7] s390x/cpu_topology: CPU topology migration Pierre Morel
2022-12-09 14:56 ` Cédric Le Goater
2022-12-12 9:14 ` Pierre Morel
2022-12-11 14:55 ` Pierre Morel
2022-12-13 13:26 ` Christian Borntraeger
2022-12-13 17:40 ` Pierre Morel [this message]
2022-12-08 9:44 ` [PATCH v13 5/7] s390x/cpu_topology: interception of PTF instruction Pierre Morel
2022-12-08 9:44 ` [PATCH v13 6/7] s390x/cpu_topology: activating CPU topology Pierre Morel
2022-12-08 9:44 ` [PATCH v13 7/7] docs/s390x: document s390x cpu topology Pierre Morel
2022-12-09 13:32 ` [PATCH v13 0/7] s390x: CPU Topology Thomas Huth
2022-12-12 8:51 ` Pierre Morel
2022-12-12 9:07 ` Thomas Huth
2022-12-12 10:10 ` Pierre Morel
2022-12-12 10:17 ` Thomas Huth
2022-12-13 13:41 ` Christian Borntraeger
2022-12-13 13:57 ` Janis Schoetterl-Glausch
2022-12-13 14:00 ` Christian Borntraeger
2022-12-13 17:24 ` Pierre Morel
2022-12-14 10:39 ` Thomas Huth
2022-12-09 14:45 ` Cédric Le Goater
2022-12-12 10:01 ` Pierre Morel
2022-12-13 13:50 ` Christian Borntraeger
2022-12-13 15:12 ` Christian Borntraeger
2022-12-13 15:31 ` Janis Schoetterl-Glausch
2022-12-13 17:27 ` 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=ca338024-4e00-6e45-2eea-ffb034c854a9@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=clg@kaod.org \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=nrb@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=scgl@linux.ibm.com \
--cc=seiden@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.