From: Steven Price <steven.price@arm.com>
To: Andrew Jones <drjones@redhat.com>,
kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Cc: maz@kernel.org, pbonzini@redhat.com
Subject: Re: [PATCH v2 0/6] KVM: arm64: pvtime: Fixes and a new cap
Date: Wed, 5 Aug 2020 16:37:20 +0100 [thread overview]
Message-ID: <c5dbe385-d0d5-94f5-5e8a-620e439e482b@arm.com> (raw)
In-Reply-To: <20200804170604.42662-1-drjones@redhat.com>
On 04/08/2020 18:05, Andrew Jones wrote:
> v2:
> - ARM_SMCCC_HV_PV_TIME_FEATURES now also returns SMCCC_RET_NOT_SUPPORTED
> when steal time is not supported
> - Added READ_ONCE() for the run_delay read
> - Reworked kvm_put/get_guest to not require type as a parameter
> - Added some more text to the documentation for KVM_CAP_STEAL_TIME
> - Enough changed that I didn't pick up Steven's r-b's
Feel free to add my r-b's - the changes all look fine to me.
Thanks,
Steve
>
> The first four patches in the series are fixes that come from testing
> and reviewing pvtime code while writing the QEMU support[*]. The last
> patch is only a convenience for userspace, and I wouldn't be heartbroken
> if it wasn't deemed worth it. The QEMU patches are currently written
> without the cap. However, if the cap is accepted, then I'll change the
> QEMU code to use it.
>
> Thanks,
> drew
>
> [*] https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg03856.html
> (a v2 of this series will also be posted shortly)
>
> Andrew Jones (6):
> KVM: arm64: pvtime: steal-time is only supported when configured
> KVM: arm64: pvtime: Fix potential loss of stolen time
> KVM: arm64: Drop type input from kvm_put_guest
> KVM: arm64: pvtime: Fix stolen time accounting across migration
> KVM: Documentation: Minor fixups
> arm64/x86: KVM: Introduce steal-time cap
>
> Documentation/virt/kvm/api.rst | 22 ++++++++++++++++++----
> arch/arm64/include/asm/kvm_host.h | 2 +-
> arch/arm64/kvm/arm.c | 3 +++
> arch/arm64/kvm/pvtime.c | 29 +++++++++++++----------------
> arch/x86/kvm/x86.c | 3 +++
> include/linux/kvm_host.h | 31 ++++++++++++++++++++++++++-----
> include/uapi/linux/kvm.h | 1 +
> 7 files changed, 65 insertions(+), 26 deletions(-)
>
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2020-08-05 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 17:05 [PATCH v2 0/6] KVM: arm64: pvtime: Fixes and a new cap Andrew Jones
2020-08-04 17:05 ` [PATCH v2 1/6] KVM: arm64: pvtime: steal-time is only supported when configured Andrew Jones
2020-08-04 17:06 ` [PATCH v2 2/6] KVM: arm64: pvtime: Fix potential loss of stolen time Andrew Jones
2020-08-04 17:06 ` [PATCH v2 3/6] KVM: arm64: Drop type input from kvm_put_guest Andrew Jones
2020-08-04 17:06 ` [PATCH v2 4/6] KVM: arm64: pvtime: Fix stolen time accounting across migration Andrew Jones
2020-08-04 17:06 ` [PATCH v2 5/6] KVM: Documentation: Minor fixups Andrew Jones
2020-08-04 17:06 ` [PATCH v2 6/6] arm64/x86: KVM: Introduce steal-time cap Andrew Jones
2020-08-05 15:37 ` Steven Price [this message]
2020-08-19 12:50 ` [PATCH v2 0/6] KVM: arm64: pvtime: Fixes and a new cap Andrew Jones
2020-08-21 13:04 ` Marc Zyngier
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=c5dbe385-d0d5-94f5-5e8a-620e439e482b@arm.com \
--to=steven.price@arm.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=pbonzini@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