From: Jim Mattson via Qemu-devel <qemu-devel@nongnu.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
kvm list <kvm@vger.kernel.org>,
mtosatti@redhat.com, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Liran Alon <liran.alon@oracle.com>,
Paolo Bonzini <pbonzini@redhat.com>,
rth@twiddle.net
Subject: Re: [QEMU PATCH v2 0/2]: KVM: i386: Add support for save and restore nested state
Date: Fri, 2 Nov 2018 10:01:19 -0700 [thread overview]
Message-ID: <CALMp9eRw-0JCpwfEGU6ximLMSNfgKsvBEfKpLOq_MGgTq+81Rw@mail.gmail.com> (raw)
In-Reply-To: <20181102165807.GG21191@redhat.com>
On Fri, Nov 2, 2018 at 9:58 AM, Daniel P. Berrangé <berrange@redhat.com> wrote:
> On Fri, Nov 02, 2018 at 09:44:54AM -0700, Jim Mattson via Qemu-devel wrote:
>> On Fri, Nov 2, 2018 at 5:59 AM, Liran Alon <liran.alon@oracle.com> wrote:
>> >
>>
>> >>> Therefore, I don't think that we want this versioning to be based on KVM_CAP at all.
>> >>> It seems that we would want the process to behave as follows:
>> >>> 1) Mgmt-layer at dest queries dest host max supported nested_state size.
>> >>> (Which should be returned from kvm_check_extension(KVM_CAP_NESTED_STATE))
>> >>> 2) Mgmt-layer at source initiate migration to dest with requesting QEMU to send nested_state
>> >>> matching dest max supported nested_state size.
>> >>> When saving nested state using KVM_GET_NESTED_STATE IOCTL, QEMU will specify in nested_state->size
>> >>> the *requested* size to be saved and KVM should be able to save only the information which matches
>> >>> the version that worked with that size.
>> >>> 3) After some sanity checks on received migration stream, dest host use KVM_SET_NESTED_STATE IOCTL.
>> >>> This IOCTL should deduce which information it should deploy based on given nested_state->size.
>>
>> I have to object to any proposal which requires the management later
>> to communicate with the source and the destination to determine what
>> should be done.
>
> Can you elaborate on why you object ?
We don't currently have this requirement, and I don't want to be
encumbered by it.
WARNING: multiple messages have this Message-ID (diff)
From: Jim Mattson <jmattson@google.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Liran Alon <liran.alon@oracle.com>,
Eduardo Habkost <ehabkost@redhat.com>,
kvm list <kvm@vger.kernel.org>,
mtosatti@redhat.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
rth@twiddle.net
Subject: Re: [Qemu-devel] [QEMU PATCH v2 0/2]: KVM: i386: Add support for save and restore nested state
Date: Fri, 2 Nov 2018 10:01:19 -0700 [thread overview]
Message-ID: <CALMp9eRw-0JCpwfEGU6ximLMSNfgKsvBEfKpLOq_MGgTq+81Rw@mail.gmail.com> (raw)
In-Reply-To: <20181102165807.GG21191@redhat.com>
On Fri, Nov 2, 2018 at 9:58 AM, Daniel P. Berrangé <berrange@redhat.com> wrote:
> On Fri, Nov 02, 2018 at 09:44:54AM -0700, Jim Mattson via Qemu-devel wrote:
>> On Fri, Nov 2, 2018 at 5:59 AM, Liran Alon <liran.alon@oracle.com> wrote:
>> >
>>
>> >>> Therefore, I don't think that we want this versioning to be based on KVM_CAP at all.
>> >>> It seems that we would want the process to behave as follows:
>> >>> 1) Mgmt-layer at dest queries dest host max supported nested_state size.
>> >>> (Which should be returned from kvm_check_extension(KVM_CAP_NESTED_STATE))
>> >>> 2) Mgmt-layer at source initiate migration to dest with requesting QEMU to send nested_state
>> >>> matching dest max supported nested_state size.
>> >>> When saving nested state using KVM_GET_NESTED_STATE IOCTL, QEMU will specify in nested_state->size
>> >>> the *requested* size to be saved and KVM should be able to save only the information which matches
>> >>> the version that worked with that size.
>> >>> 3) After some sanity checks on received migration stream, dest host use KVM_SET_NESTED_STATE IOCTL.
>> >>> This IOCTL should deduce which information it should deploy based on given nested_state->size.
>>
>> I have to object to any proposal which requires the management later
>> to communicate with the source and the destination to determine what
>> should be done.
>
> Can you elaborate on why you object ?
We don't currently have this requirement, and I don't want to be
encumbered by it.
next prev parent reply other threads:[~2018-11-02 17:01 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 12:46 [QEMU PATCH v2 0/2]: KVM: i386: Add support for save and restore nested state Liran Alon
2018-09-16 12:46 ` [Qemu-devel] " Liran Alon
2018-09-16 12:46 ` [QEMU PATCH v2 1/2] i386: Compile CPUX86State xsave_buf only when support KVM or HVF Liran Alon
2018-09-16 12:46 ` [Qemu-devel] " Liran Alon
2018-09-16 12:46 ` [QEMU PATCH v2 2/2] KVM: i386: Add support for save and restore nested state Liran Alon
2018-09-16 12:46 ` [Qemu-devel] " Liran Alon
2018-10-08 17:21 ` [QEMU PATCH v2 0/2]: " Liran Alon
2018-10-08 17:21 ` [Qemu-devel] " Liran Alon
2018-10-15 18:10 ` Liran Alon
2018-10-15 18:10 ` [Qemu-devel] " Liran Alon
2018-10-31 1:03 ` Liran Alon
2018-10-31 1:03 ` [Qemu-devel] " Liran Alon
2018-10-31 18:17 ` Eduardo Habkost
2018-10-31 18:17 ` [Qemu-devel] " Eduardo Habkost
2018-10-31 18:19 ` Paolo Bonzini
2018-10-31 18:19 ` [Qemu-devel] " Paolo Bonzini
2018-10-31 18:50 ` Liran Alon
2018-10-31 18:50 ` [Qemu-devel] " Liran Alon
2018-10-31 18:59 ` Dr. David Alan Gilbert
2018-10-31 18:59 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-10-31 23:17 ` Liran Alon
2018-10-31 23:17 ` [Qemu-devel] " Liran Alon
2018-11-01 13:10 ` Dr. David Alan Gilbert
2018-11-01 13:10 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-11-01 15:23 ` Liran Alon
2018-11-01 15:23 ` [Qemu-devel] " Liran Alon
2018-11-01 15:56 ` Dr. David Alan Gilbert
2018-11-01 15:56 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-11-01 16:45 ` Jim Mattson via Qemu-devel
2018-11-01 16:45 ` [Qemu-devel] " Jim Mattson
2018-11-02 3:46 ` Liran Alon
2018-11-02 3:46 ` [Qemu-devel] " Liran Alon
2018-11-02 9:40 ` Paolo Bonzini
2018-11-02 9:40 ` [Qemu-devel] " Paolo Bonzini
2018-11-02 12:35 ` Dr. David Alan Gilbert
2018-11-02 12:35 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-11-02 12:40 ` Daniel P. Berrangé
2018-11-02 12:40 ` [Qemu-devel] " Daniel P. Berrangé
2018-11-04 22:12 ` Paolo Bonzini
2018-11-04 22:12 ` [Qemu-devel] " Paolo Bonzini
2018-11-02 12:59 ` Liran Alon
2018-11-02 12:59 ` [Qemu-devel] " Liran Alon
2018-11-02 16:44 ` Jim Mattson via Qemu-devel
2018-11-02 16:44 ` [Qemu-devel] " Jim Mattson
2018-11-02 16:58 ` Daniel P. Berrangé
2018-11-02 16:58 ` [Qemu-devel] " Daniel P. Berrangé
2018-11-02 17:01 ` Jim Mattson via Qemu-devel [this message]
2018-11-02 17:01 ` Jim Mattson
2018-11-02 16:54 ` Daniel P. Berrangé
2018-11-02 16:54 ` [Qemu-devel] " Daniel P. Berrangé
2018-11-02 16:58 ` Dr. David Alan Gilbert
2018-11-02 16:58 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-11-04 22:19 ` Paolo Bonzini
2018-11-04 22:19 ` [Qemu-devel] " Paolo Bonzini
2018-11-12 16:18 ` Daniel P. Berrangé
2018-11-12 16:18 ` [Qemu-devel] " Daniel P. Berrangé
2018-11-12 16:50 ` Dr. David Alan Gilbert
2018-11-12 16:50 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-11-12 16:53 ` Paolo Bonzini
2018-11-12 16:53 ` [Qemu-devel] " Paolo Bonzini
2018-11-12 16:54 ` Daniel P. Berrangé
2018-11-12 16:54 ` [Qemu-devel] " Daniel P. Berrangé
2018-11-13 0:00 ` Liran Alon
2018-11-13 0:00 ` [Qemu-devel] " Liran Alon
2018-11-13 0:07 ` Jim Mattson via Qemu-devel
2018-11-13 0:07 ` [Qemu-devel] " Jim Mattson
2018-11-13 0:09 ` Liran Alon
2018-11-13 0:09 ` [Qemu-devel] " Liran Alon
2018-11-12 23:58 ` Liran Alon
2018-11-12 23:58 ` [Qemu-devel] " Liran Alon
2018-11-02 16:39 ` Jim Mattson via Qemu-devel
2018-11-02 16:39 ` [Qemu-devel] " Jim Mattson
2018-11-03 2:02 ` Liran Alon
2018-11-03 2:02 ` [Qemu-devel] " Liran Alon
2018-11-08 0:13 ` Liran Alon
2018-11-08 0:13 ` [Qemu-devel] " Liran Alon
2018-11-08 0:45 ` Jim Mattson via Qemu-devel
2018-11-08 0:45 ` [Qemu-devel] " Jim Mattson
2018-11-08 9:50 ` Paolo Bonzini
2018-11-08 9:50 ` [Qemu-devel] " Paolo Bonzini
2018-11-08 9:57 ` Liran Alon
2018-11-08 9:57 ` [Qemu-devel] " Liran Alon
2018-11-08 17:02 ` Paolo Bonzini
2018-11-08 17:02 ` [Qemu-devel] " Paolo Bonzini
2018-11-08 18:41 ` Liran Alon
2018-11-08 18:41 ` [Qemu-devel] " Liran Alon
2018-11-08 20:34 ` Paolo Bonzini
2018-11-08 20:34 ` [Qemu-devel] " Paolo Bonzini
2018-11-12 14:51 ` Dr. David Alan Gilbert
2018-11-12 14:51 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-11-01 19:03 ` Liran Alon
2018-11-01 19:03 ` [Qemu-devel] " Liran Alon
2018-11-01 19:07 ` Dr. David Alan Gilbert
2018-11-01 19:07 ` [Qemu-devel] " Dr. David Alan Gilbert
2018-11-01 19:41 ` Jim Mattson via Qemu-devel
2018-11-01 19:41 ` [Qemu-devel] " Jim Mattson
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=CALMp9eRw-0JCpwfEGU6ximLMSNfgKsvBEfKpLOq_MGgTq+81Rw@mail.gmail.com \
--to=qemu-devel@nongnu.org \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rth@twiddle.net \
/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.