From: Paolo Bonzini <pbonzini@redhat.com>
To: Liran Alon <liran.alon@oracle.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, kvm@vger.kernel.org,
Joao Martins <joao.m.martins@oracle.com>
Subject: Re: [PATCH 4/4] target/i386: kvm: Demand nested migration kernel capabilities only when vCPU may have enabled VMX
Date: Mon, 15 Jul 2019 11:25:00 +0200 [thread overview]
Message-ID: <e1e48ece-b571-5229-589d-3525f505887f@redhat.com> (raw)
In-Reply-To: <8423C5FD-2F44-48B8-8E1F-A2E8D62E8F2B@oracle.com>
On 15/07/19 11:20, Liran Alon wrote:
> Gentle ping.
>
> Should this be considered to be merged into QEMU even though QEMU is now in hard freeze?
> As it touches a mechanism which is already merged but too restricted.
Yes, I have it queued and will send the pull request later today.
Paolo
> Anyway, I would like this to be reviewed even if it’s merged is delayed for early feedback.
>
> Thanks,
> -Liran
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Liran Alon <liran.alon@oracle.com>, qemu-devel@nongnu.org
Cc: Joao Martins <joao.m.martins@oracle.com>,
ehabkost@redhat.com, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 4/4] target/i386: kvm: Demand nested migration kernel capabilities only when vCPU may have enabled VMX
Date: Mon, 15 Jul 2019 11:25:00 +0200 [thread overview]
Message-ID: <e1e48ece-b571-5229-589d-3525f505887f@redhat.com> (raw)
In-Reply-To: <8423C5FD-2F44-48B8-8E1F-A2E8D62E8F2B@oracle.com>
On 15/07/19 11:20, Liran Alon wrote:
> Gentle ping.
>
> Should this be considered to be merged into QEMU even though QEMU is now in hard freeze?
> As it touches a mechanism which is already merged but too restricted.
Yes, I have it queued and will send the pull request later today.
Paolo
> Anyway, I would like this to be reviewed even if it’s merged is delayed for early feedback.
>
> Thanks,
> -Liran
next prev parent reply other threads:[~2019-07-15 9:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 21:06 [PATCH 0/4] target/i386: kvm: Various nested-state fixes Liran Alon
2019-07-05 21:06 ` [Qemu-devel] " Liran Alon
2019-07-05 21:06 ` [PATCH 1/4] target/i386: kvm: Init nested-state for VMX when vCPU expose VMX Liran Alon
2019-07-05 21:06 ` [Qemu-devel] " Liran Alon
2019-07-09 17:21 ` Maran Wilson
2019-07-11 13:45 ` Paolo Bonzini
2019-07-11 14:36 ` Liran Alon
2019-07-11 14:36 ` Liran Alon
2019-07-11 17:27 ` Paolo Bonzini
2019-07-11 17:27 ` Paolo Bonzini
2019-07-05 21:06 ` [PATCH 2/4] target/i386: kvm: Init nested-state for vCPU exposed with SVM Liran Alon
2019-07-05 21:06 ` [Qemu-devel] " Liran Alon
2019-07-09 17:21 ` Maran Wilson
2019-07-11 13:35 ` Paolo Bonzini
2019-07-05 21:06 ` [PATCH 3/4] target/i386: kvm: Save nested-state only in case vCPU have set VMXON region Liran Alon
2019-07-05 21:06 ` [Qemu-devel] " Liran Alon
2019-07-09 17:21 ` Maran Wilson
2019-07-05 21:06 ` [PATCH 4/4] target/i386: kvm: Demand nested migration kernel capabilities only when vCPU may have enabled VMX Liran Alon
2019-07-05 21:06 ` [Qemu-devel] " Liran Alon
2019-07-09 17:21 ` Maran Wilson
2019-07-15 9:20 ` Liran Alon
2019-07-15 9:20 ` [Qemu-devel] " Liran Alon
2019-07-15 9:25 ` Paolo Bonzini [this message]
2019-07-15 9:25 ` Paolo Bonzini
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=e1e48ece-b571-5229-589d-3525f505887f@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=qemu-devel@nongnu.org \
/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.