From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>,
Yi Min Zhao <zyimin@linux.vnet.ibm.com>,
Pierre Morel <pmorel@linux.vnet.ibm.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH/s390-next 3/3] s390x/flic: migrate ais states
Date: Thu, 13 Jul 2017 15:10:54 +0200 [thread overview]
Message-ID: <20170713151054.28eb7909@gondolin> (raw)
In-Reply-To: <606fdb06-cb0e-00b3-ffa3-18a024f14309@de.ibm.com>
On Thu, 13 Jul 2017 15:02:08 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 07/13/2017 02:27 PM, Cornelia Huck wrote:
> > On Thu, 13 Jul 2017 12:40:29 +0200
> > Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> >
> >> From: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
> >>
> >> During migration we should transfer ais states to the target guest.
> >> This patch introduces a subsection to kvm_s390_flic_vmstate and new
> >> vmsd for qemu_flic. The ais states need to be migrated only when
> >> ais is supported.
> >>
> >> Signed-off-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
> >> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> >> ---
> >> hw/intc/s390_flic.c | 20 ++++++++++++
> >> hw/intc/s390_flic_kvm.c | 75 ++++++++++++++++++++++++++++++++++++++++++++
> >> include/hw/s390x/s390_flic.h | 1 +
> >> 3 files changed, 96 insertions(+)
> >> +static int kvm_flic_ais_post_load(void *opaque, int version_id)
> >> +{
> >> + KVMS390FLICStateMigTmp *tmp = opaque;
> >> + KVMS390FLICState *flic = tmp->parent;
> >> + struct kvm_s390_ais_all ais = {
> >> + .simm = tmp->simm,
> >> + .nimm = tmp->nimm,
> >> + };
> >> + struct kvm_device_attr attr = {
> >> + .group = KVM_DEV_FLIC_AISM_ALL,
> >> + .addr = (uint64_t)&ais,
> >> + };
> >> +
> >> + if (!ais_needed(flic)) {
> >> + return -ENOSYS;
> >> + }
> >
> > I do not understand this... does that mean that
> > - we should never get here or
> > - we should not try to change the fields or
> > - I need coffee?
>
> My understanding is that this should not happen with a normal setup,
> but it can happen if the user does something "wrong". For example
> use qemu without libvirt and with -cpu host (which is not migration safe)
> and do a migration from a host that has AIS to a host that has no AIS.
> In that case the target system will reject the migration (late, but hopefully
> not too late).
A comment would be helpful here.
next prev parent reply other threads:[~2017-07-13 13:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 10:40 [Qemu-devel] [PATCH/s390-next 0/3] s390x: remaining pci related fixes Christian Borntraeger
2017-07-13 10:40 ` [Qemu-devel] [PATCH/s390-next 1/3] s390x: initialize cpu firstly Christian Borntraeger
2017-07-13 11:55 ` Cornelia Huck
2017-07-13 10:40 ` [Qemu-devel] [PATCH/s390-next 2/3] s390x/cpumodel: add zpci, aen and ais facilities Christian Borntraeger
2017-07-13 12:11 ` Cornelia Huck
2017-07-13 12:29 ` Christian Borntraeger
2017-07-13 13:06 ` Cornelia Huck
2017-07-13 13:11 ` Christian Borntraeger
2017-07-13 13:15 ` Cornelia Huck
2017-07-13 12:41 ` Christian Borntraeger
2017-07-13 12:57 ` Cornelia Huck
2017-07-13 13:07 ` Halil Pasic
2017-07-13 10:40 ` [Qemu-devel] [PATCH/s390-next 3/3] s390x/flic: migrate ais states Christian Borntraeger
2017-07-13 12:27 ` Cornelia Huck
2017-07-13 13:02 ` Christian Borntraeger
2017-07-13 13:10 ` Cornelia Huck [this message]
2017-07-13 13:41 ` Halil Pasic
2017-07-13 13:58 ` Christian Borntraeger
2017-07-13 14:01 ` Cornelia Huck
2017-07-13 13:18 ` Halil Pasic
2017-07-13 14:49 ` Dr. David Alan Gilbert
2017-07-13 15:05 ` Christian Borntraeger
2017-07-13 15:11 ` Dr. David Alan Gilbert
2017-07-13 15:45 ` Halil Pasic
2017-07-13 15:54 ` Dr. David Alan Gilbert
2017-07-18 10:31 ` Juan Quintela
2017-07-18 14:07 ` Dr. David Alan Gilbert
2017-07-18 18:24 ` Halil Pasic
2017-07-13 15:27 ` Cornelia Huck
2017-07-13 10:58 ` [Qemu-devel] [PATCH/s390-next 0/3] s390x: remaining pci related fixes Christian Borntraeger
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=20170713151054.28eb7909@gondolin \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=zyimin@linux.vnet.ibm.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.